An MDA‐based framework for collaborative business process modelling

Abstract

PurposeThis paper aims to present a new approach for developing a framework based on a model driven architecture (MDA) for the modelling of technology‐independent collaborative processes.Design/methodology/approachThe paper suggests a new collaborative process modelling approach based on an MDA and a metamodelling technique. The research method, based on the design science approach, was started by identifying the characteristics of the collaborative processes, which distinguish them from the classical intraorganizational ones. Then, the generic collaborative business process (CBP) modelling framework is developed based on MDA approach and definition of a set of transformation rules through three layers: business, process, and technical. After that, the core component of the framework was the proposition of a generic CBP metamodel at PIM/MDA level. The specific collaboration participant's business processes (expressed as BPMN model) are generated from the generic CBP model represented as an UML2 Profile activity diagram, which is compliant to CBP metamodel. Finally, as proof‐of‐concept, the architecture of an Eclipse‐based open development platform is developed implementing an e‐Procurement collaborative process.FindingsThe proposed framework for CBP modelling and the generic CBP metamodel contribute towards a more efficient methodology and have consequences for BPM‐related collaboration, facilitating the B2B processes modelling and implementation. In order to demonstrate and evaluate the practical applicability of the framework, the architecture of an Eclipse‐based open development platform is developed implementing a collaborative business application on the basis of an e‐Procurement use case.Research limitations/implicationsThere is a need to focus future research efforts on the improvement of the semi‐automatic transformation phase from public to private processes which needs human intervention by adding a suitable interfaces at both sides of the B2B interaction. In addition, the problem of semantic heterogeneities regarding the partner's business process elements (business documents, activity/task names) should be tackled by developing an approach that uses ontology.Practical implicationsBusiness processes developers find a B2B technology‐independent solution for implementing and using interorganizational information systems.Originality/valueThe paper provides a framework that enables the CBP modelling and integrates a generic CBP metamodel. Currently, to the best of the authors' knowledge, such a generic metamodel and his instantiation have not so far been developed.

Structured literature review on business process performance analysis and evaluation

“…Justification for regulative processes, also value creation activities of the process and activities associated to abuse prevention are provided by Regev et al (2005). Characteristics of collaborative processes and generic collaborative business process modeling framework is investigated by Bouchbout et al (2012). Process of reviewing performance is developed by Najmi (2005).…”

A Model-driven Architecture for Collaborative Business Processes

“…The author's approach respects the separation of the business and technology layer of the MDA, however, the use of the language (UP-ColBPIP) which is an extension of the UML2 does not seem very interesting given that the latter is quite complex for people in the trade or non-IT specialists to understand. Other works like [5], proposes a Framework for the modeling of collaborative business processes, its methodology is based on the MDA approach. It offers a generic metamodel in order to instantiate it as a collaborative business process from which the respective internal business processes of the partners can be derived.…”

A New Framework for Classifying Information Systems Modelling Languages

“…This infrastructure offers two UML-based extension mechanisms: the lightweight extension mechanism, via UML profiles, and the heavyweight extension mechanism, via extension or modification of the core UML metamodel (Fig. 12) [49], [50]. The UML profile consists of a set of stereotypes that specify UML elements in that profile for the domain of interest.…”

“…The stereotyped elements have the same structure of traditional UML element plus extra constraints and tagged values that are added, by the stereotype, to that metamodel element [48] [49]. Without any conflict in semantics, the profile only customises the metamodel without adding new metaclass in the UML metaclass hierarchy [50].…”