Message exchange on base of a blockchain-based layered architecture

2018 ◽  
Vol 60 (5-6) ◽  
pp. 253-261
Author(s):  
Uwe Roth ◽  
Theophane Ngne Djoua
Keyword(s):  
Business Process ◽  
Proof Of Concept ◽  
Layered Architecture ◽  
Knowing That ◽  
Data Throughput ◽  
Fast Development ◽  
Message Structure ◽  
Message Exchange ◽  
Point To Point ◽  
Main Message

Abstract In this article, we propose an architecture that allows to exchange messages or data via a blockchain solution, while keeping the business process independent from the concrete blockchain. The project is the consequence of a need to have fast development of a blockchain based proof of concept that shows the feasibility of a business process, while knowing that in a future step the underlying blockchain solution has to be replaced for reasons of licensing or maximal data throughput. This is done by providing an architecture on base of layers, similar to the OSI-model, and encapsulates the used blockchain within a wrapper layer that covers all blockchain specific properties and only provides a transparent view on the reading or writing from and to the blockchain. The higher layers re-implement point-to-point communication and introduce confidentiality by the use of encryption techniques. The architecture has been tested and proven by implementing two different blockchain solutions that are shielded by specific wrapper layer implementations. This wrapper layer is responsible for the fragmentation of the sent data and their encapsulation into the concrete blockchain solution. The reconstruction of the data takes care of the data fragments being sent potentially out of order or being incomplete. A payload layer is introduced to provide point-to-point communication and to embed the main message inside a message structure. In collaboration with underlying layer it identifies for which message one is not the addressee and allow the underling layer to stop collecting unnecessary data. A crypto-layer finally provides ways of encrypting messages for one or many recipients. Having fixed layers not only allows to replace the underlying blockchain solution but also to extend or replace the other layers in case new security features or optimized protocols need to embedded. The proposed solution does not allow to use specific features like smart contracts and only provides undeniable tamper-proofed existence of a sent message.

Business Agility and Process Agility

2013 ◽  
pp. 1580-1598
Author(s):  
Giorgio Bruno
Keyword(s):  
Business Process ◽  
Business Processes ◽  
Essential Feature ◽  
Great Influence ◽  
Proof Of Concept ◽  
Business Agility ◽  
Different Levels

Agility is an essential feature for SMEs and this chapter intends to examine if and how business processes, as currently understood, are able to promote it. Over the last years a number of viewpoints have emerged which exerted great influence on the design of notations and languages for business processes: the majority of them can be referred to as the centralized viewpoint, the role viewpoint, the conversational viewpoint, the case viewpoint and the cooperative one. These viewpoints provide different levels of agility and then beneficial results can be expected from their integration, which is the purpose of the proof-of-concept notation, AgileBPN, presented in this chapter. In AgileBPN, business processes are organized around conversations and role processes (encompassing the tasks pertaining to a given role); shared artifacts are represented as cooperative objects. The notation is illustrated with the help of an example referring to a business process meant to handle applications in a certain organization.

Grid Business Process

2008 ◽  
pp. 257-297 ◽  
Author(s):  
Asif Akram ◽  
Rob Allen ◽  
Sanjay Chaudhary ◽  
Prateek Jain ◽  
Zakir Laliwala
Keyword(s):  
Web Services ◽  
Web Service ◽  
Business Process ◽  
Use Cases ◽  
Proof Of Concept ◽  
Service Standards

This chapter presents a ‘Case Study’ based on the distributed market. The requirements of this Grid Business Process are more demanding than any typical business process deployed within a single organization or enterprise. Recently different specifications built on top of Web service standards have originated from the Grid paradigm to address limitations of stateless Web services. These emerging specifications are evaluated in the first part of the chapter to capture requirements of a dynamic business process i.e. Business Process Grid. In second part of the chapter, a case study with different use cases is presented to simulate various scenarios. The abstract discussion and requirements of the case study is followed by the actual implementation. The implementation is meant for the proof-of-concept rather than fully functional application.

scholarly journals Synchronous gesture manipulation for collaboration and coordination of co-located Business Process Modelling

2015 ◽  
Author(s):  
Brenda Scholtz ◽  
Andre Calitz ◽  
Irene Snyman
Keyword(s):  
Business Process ◽  
Design Science ◽  
Science Research ◽  
Process Modelling ◽  
Process Models ◽  
Proof Of Concept ◽  
Business Process Modelling ◽  
Individual Contributions ◽  
Coordination And Collaboration

The purpose of this study was to investigate approaches (techniques and technologies) for the coordination of collaborative tasks using synchronous gesture manipulation. Business Process Modelling (BPM) tasks are often performed in teams of modellers who need to collaborate with each other in order to coordinate and integrate their individual contributions into the various process models in a co-located environment. These collaborative BPM tasks were used as a case study in order to develop the artifact (the BPM-Touch approach) as a proof of concept. The BPM-Touch approach allows for the coordination and collaboration of BPM tasks in co-located modelling teams using synchronous gesture manipulation approaches. The Design Science Research (DSR) methodology was used and several cycles of developing and evaluating the artifact took place. This paper reports on the last cycle and set of evaluations. The proposed approach was implemented in a BPM software package in order to provide empirical validation. Usability evaluations of the software were undertaken with both students and BPM professionals as participants. The empirical results of the evaluations revealed that the participants found the approach to be effective and rated the usability and satisfaction of the collaboration and gesture manipulation aspects of the software positively.

Towards a Reusable Fault Handling in WS-BPEL

2014 ◽  
Vol 24 (02) ◽  
pp. 243-267
Author(s):  
Andrej Kocbek ◽  
Matjaz B. Juric
Keyword(s):  
Business Process ◽  
Real World ◽  
Service Oriented Architecture ◽  
Proof Of Concept ◽  
Fault Handling ◽  
Process Implementation ◽  
Service Oriented ◽  
Definition Of ◽  
Process Complexity ◽  
Bpel Processes

Service Oriented Architecture (SOA) is an evolution of distributed computing and it is based on the concepts of interoperable services. To enable reliable and robust service oriented information systems, it is important to establish an effective fault handling. WS-BPEL 2.0 specification does not provide sophisticated and reusable support for handling faults and challenges process designers with many obstacles in the process implementation. We introduce a novel policy driven fault handling framework for BPEL by extending the WS-BPEL 2.0 specification. We propose to separate business process and fault handling logic with the aim to decrease code duplication, process complexity and overall process size. The proposed framework consists of a fault policy which includes the definition of BPEL fault handling logic. The fault policy defines fault handlers and fault handling recovery actions that can be used to design handling BPEL process faults. As a proof-of-concept, we have developed a prototype implementation of the proposed policy driven fault handling framework for BPEL and tested it on 117 real world BPEL scenarios. We have confirmed that the proposed solution decreases the code duplication, the process complexity and overall the process size. Even more, we successfully improved the reliability and readability of BPEL processes.

scholarly journals A database for efficient storage and management of multi panel SNP data

2013 ◽  
Vol 56 (1) ◽  
pp. 1023-1027
Author(s):  
E. Groeneveld ◽  
C. V. C. Truong
Keyword(s):  
Data Storage ◽  
Proof Of Concept ◽  
Snp Data ◽  
New Strategy ◽  
Fast Development ◽  
Efficient Data ◽  
Compressed Storage ◽  
Space Requirements ◽  
Number Of Individuals ◽  
Derived Data

Abstract. The fast development of high throughput genotyping has opened up new possibilities in genetics while at the same time producing immense data handling issues. A system design and proof of concept implementation are presented which provides efficient data storage and manipulation of single nucleotide polymorphism (SNP) genotypes in a relational database. A new strategy using SNP and individual selection vectors allows us to view SNP data as matrices or sets. These genotype sets provide an easy way to handle original and derived data, the latter at basically no storage costs. Due to its vector based database storage, data imports and exports are much faster than those of other SNP databases. In the proof of concept implementation, the compressed storage scheme reduces disk space requirements by a factor of around 300. Furthermore, this design scales linearly with number of individuals and SNPs involved. The procedure supports panels of different sizes. This allows a straight forward management of different panel sizes in the same population as it occurs in animal breeding programs when higher density panels replace previous lower density versions.

Business Agility and Process Agility

2011 ◽  
pp. 71-89 ◽  
Author(s):  
Giorgio Bruno
Keyword(s):  
Business Process ◽  
Business Processes ◽  
Essential Feature ◽  
Great Influence ◽  
Proof Of Concept ◽  
Business Agility ◽  
Different Levels

Agility is an essential feature for SMEs and this chapter intends to examine if and how business processes, as currently understood, are able to promote it. Over the last years a number of viewpoints have emerged which exerted great influence on the design of notations and languages for business processes: the majority of them can be referred to as the centralized viewpoint, the role viewpoint, the conversational viewpoint, the case viewpoint and the cooperative one. These viewpoints provide different levels of agility and then beneficial results can be expected from their integration, which is the purpose of the proof-of-concept notation, AgileBPN, presented in this chapter. In AgileBPN, business processes are organized around conversations and role processes (encompassing the tasks pertaining to a given role); shared artifacts are represented as cooperative objects. The notation is illustrated with the help of an example referring to a business process meant to handle applications in a certain organization.

INTEROPERABLE SUPPLY-CHAIN APPLICATIONS: MESSAGE METAMODEL-BASED SEMANTIC RECONCILIATION OF B2B MESSAGES

2010 ◽  
Vol 19 (01n02) ◽  
pp. 31-69 ◽  
Author(s):  
MARKO VUJASINOVIC ◽  
EDWARD BARKMEYER ◽  
NENAD IVEZIC ◽  
ZORAN MARJANOVIC
Keyword(s):  
Supply Chain ◽  
Electronic Data Interchange ◽  
Electronic Business ◽  
Markup Language ◽  
Common Representation ◽  
Data Interchange ◽  
Extensible Markup ◽  
Message Structure ◽  
Message Exchange ◽  
Business To Business

Supply-chain applications exchange numerous electronic business-to-business (B2B) messages of varied types. Traditionally, prior to a message exchange, partners adopt one particular message specification that constrains message structure and syntax to implement compatible application message interfaces. However, in open, dynamic supply-chains, the applications need to interact even though their message interfaces are based on different, yet incompatible message specifications. To achieve such interactions, we propose the Message Metamodel-based semantic reconciliation of B2B messages. The Message Metamodel is a novel, ontological form that provides for common representation of B2B message specifications and messages of various syntaxes, such as Extensible Markup Language (XML) or Electronic Data Interchange (EDI). The experimental investigation showed that proposed semantic reconciliation architecture built atop the Message Metamodel (1) insulates the reconciliation activities from the specific message syntaxes, (2) supports the reconciliation of messages irrespective of message standards used, and (3) enables seamless interoperable message exchange between heterogeneous supply-chain applications.

A value-oriented approach to business process specialization: Principles, proof-of-concept, and validation

2017 ◽  
Vol 127 ◽  
pp. 120-149 ◽  
Author(s):  
Abderrahmane Leshob ◽  
Hafedh Mili ◽  
Javier Gonzalez-Huerta ◽  
Anis Boubaker
Keyword(s):  
Business Process ◽  
Proof Of Concept ◽  
A Value ◽  
Oriented Approach

scholarly journals Using QR Code for Uniform Representation of Content in Cross-Border Exchange of ePrescriptions in the EU

2021 ◽  
Author(s):  
Evgeniy Krastev ◽  
Petko Kovachev ◽  
Dimitar Tcharaktchiev ◽  
Simeon Abanos
Keyword(s):  
Business Process ◽  
Process Model ◽  
Qr Code ◽  
The European Union ◽  
Digital Service ◽  
Cross Border ◽  
Contact Points ◽  
Message Exchange ◽  
Clinical Models ◽  
Initial Results

This paper proposes an approach and demonstrates its application for cross-border exchange of ePrescriptions in the European Union. A business process model of the main use case for exchange of prescription content in the eHealth Digital Service Infrastructure is created and analyzed. The novelty in this approach is the proposed encoding of the basic dataset in a Quick Response (QR) code in terms of an XML scheme that is independent of clinical models or proprietary database structures. It allows to inverse the dataflow control in the chain of message exchanges between Dispenser and National Contact Points. The proposed inversion of control positions the citizen with the QR code of the prescription in the center of that chain of message exchanges between the main actors of the business process. The independent format of content representation in the QR code allows the actors in the message exchange to auto-populate data in their registers when the medicine is dispensed. Initial results are reported and reveal the advantages of embedding prescription details in QR code employing a common independent XML scheme.

scholarly journals Working of SOA with BPM

2011 ◽  
pp. 80-85
Author(s):  
Mrs. Aarti M. Karande ◽  
Mr. B.B. Meshram
Keyword(s):  
Web Services ◽  
Business Process ◽  
Business Processes ◽  
Enterprise Application Integration ◽  
Service Orchestration ◽  
Workflow Technology ◽  
Enterprise Application ◽  
Business Analysis ◽  
Standard Interface ◽  
Message Structure

Business processes which are the set of logical tasks related to fulfil some greater purpose. These tasks must be performed in sequence according to the business rules. SOA reuses services to automate a business process using a standard interface and message structure. BPM, based on workflow technology, enterprise application integration and XML technologies, manages the enterprise from the perspective of business processes. In software development there is a gap between the implementers andthe users/customers in their understanding of the system. SOA is the driver for minimizing the gap between business analysis and IT development. The idea of Business Processes based on web services stem from the thought that a Business Process can be composed from one or more web services. Service orchestration should be flexible and adaptable to meet changing Business Process requirements. Separating the business process logic from the service components promotes flexibility. Choreography languages are WS-CDL, Let’s Dance, and BPEL4Chor.The purpose of using several choreographies simultaneously is to establish a cross-enterprise organized way of collaborating with services.

Sign in / Sign up

Export Citation Format

Share Document