Improving Process Robustness through Domain-Specific Model Transformations

Mos, Adrian; Jacquin, Thierry

doi:10.1109/edocw.2013.28

Cited by 5 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…More details about a particular language are out of the scope of this paper. However, rich language definitions are possible for various domains, as we show also in [14].…”

Section: Overview Of the Approachmentioning

confidence: 98%

“…Indeed, we did not force a perfect vertical alignment that could be very costly and unrealistic as described in [25]. The double synchronization mechanism explained in previous work [14] permits to make (and propagate) changes in the domain model as well as in the generated BPMN model. The tracking of generated elements can be based on several identity-preserving mechanisms, of which a simple example is the usage of unique IDs injected in hidden properties of BPMN elements.…”

Section: Process Enrichmentmentioning

confidence: 99%

“…We do not go into the details about the transformation process as the paper focuses on this general methodology. More details about the two-way synchronization between domain specific models and BPMN are presented in [14]. Figure 3 depicts how the BPMN generation is performed through model transformations.…”

Section: Bpmn Skeleton Generationmentioning

confidence: 99%

“…In this paper, we present an approach that focuses on BPM and SOA environments in a domain-dependent and platform-independent way. Previous technical solutions [13][14][15] are combined to present a methodological, model-driven approach that integrates domain specific modelling with domain specific monitoring in an end-to-end solution. The appropriateness and the feasibility of our approach is shown through a use case and a complete prototype implementation.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Business Matter Experts do Matter: A Model-Driven Approach for Domain Specific Process Design and Monitoring

Mos

Cortes-Cornax

2016

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Business process design and monitoring are essential elements of Business Process Management (BPM), often relying on Service Oriented Architectures (SOA). However the current BPM approaches and standards have not sufficiently reduced the Business-IT gap. Today's solutions are mostly domain-independent and platform-dependent, which limits the ability of business matter experts to express business intent and enact process change. In contrast, the approach presented in this paper focuses on BPM and SOA environments in a domain-dependent and platform-independent way. We propose to add a domain specificlayer on top of current solutions so business stakeholders can design and understand their processes in a more intuitive way. We rely on previously proposed technical solutions and integrate them in an end-to-end methodology (from design to monitoring and back). The appropriateness and the feasibility of the approach is justified through a use case and a complete prototype implementation.

show abstract

“…More details about a particular language are out of the scope of this paper. However, rich language definitions are possible for various domains, as we show also in [14].…”

Section: Overview Of the Approachmentioning

confidence: 98%

Section: Process Enrichmentmentioning

confidence: 99%

Section: Bpmn Skeleton Generationmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Business Matter Experts do Matter: A Model-Driven Approach for Domain Specific Process Design and Monitoring

Mos

Cortes-Cornax

2016

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

show abstract

“…The domain-specific and BPMN layers may be connected via an intermediate layer, which is responsible of taking domain-specific modeling artifacts (process files, organizational structures) from a variety of tools in their respective form and generating artifacts used by other tools (e.g. BPMN enabled editors) (Mos and Jacquin, 2013). We refer to this approach as Multi-layered Business Process Modeling (MBPM) (Mos, 2014).…”

Section: Introductionmentioning

confidence: 99%

Towards semantically-aided domain specific business process modeling

Lagos¹,

Mos²,

Cortes-Cornax

2018

DTA

Self Cite

View full text Add to dashboard Cite

Purpose Domain-specific process modeling has been proposed in the literature as a solution to several problems in business process management. The problems arise when using only the generic Business Process Model and Notation (BPMN) standard for modeling. This language includes domain ambiguity and difficult long-term model evolution. Domain-specific modeling involves developing concept definitions, domain-specific processes and eventually industry-standard BPMN models. This entails a multi-layered modeling approach, where any of these artifacts can be modified by various stakeholders and changes done by one person may influence models used by others. There is therefore a need for tool support to keep track of changes done and their potential impacts. The paper aims to discuss these issues. Design/methodology/approach The authors use a multi-context systems-based approach to infer the impacts that changes may cause in the models; and alsothe authors incrementally map components of business process models to ontologies. Findings Advantages of the framework include: identifying conflicts/inconsistencies across different business modeling layers; expressing rich information on the relations between two layers; calculating the impact of changes taking place in one layer to the rest of the layers; and selecting incrementally the most appropriate semantic models on which the transformations can be based. Research limitations/implications The authors consider this work as one of the foundational bricks that will enable further advances toward the governance of multi-layer business process modeling systems. Extensive usability tests would enable to further confirm the findings of the paper. Practical implications The approach described here should improve the maintainability, reuse and clarity of business process models and in extension improve data governance in large organizations. The approaches described here should improve the maintainability, reuse and clarity of business process models. This can improve data governance in large organizations and for large collections of processes by aiding various stakeholders to understand problems with process evolutions, changes and inconsistencies with business goals. Originality/value This paper fulfills an identified gap to enabling semantically aided domain–specific process modeling.

show abstract