BPMN Model Interchange

Kurz, Matthias

doi:10.1145/2882879.2882886

Cited by 8 publications

(6 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this case, the OMG established a new group called the BPMN Model Interchange Working Group (BPMN MIWG) to provide support for an exchange of models between different tools. The primary goal of this group is to support and guide vendors in creating compliant BPMN tools, identify issues in the BPMN specification, and facilitate model interchange [53]. Currently, The BPMN MIWG is working on enhancing the model interchange feature by importing, refining, and exporting some models from several vendor tools [53].…”

Section: Bpmn Model Interchange Working Group (Miwg)mentioning

confidence: 99%

“…The primary goal of this group is to support and guide vendors in creating compliant BPMN tools, identify issues in the BPMN specification, and facilitate model interchange [53]. Currently, The BPMN MIWG is working on enhancing the model interchange feature by importing, refining, and exporting some models from several vendor tools [53]. There are two types of business processes in BPMN 2.0, the first is a process model (model semantics) that contains the semantics, while the second is a process diagram which presents the visual representation.…”

Section: Bpmn Model Interchange Working Group (Miwg)mentioning

confidence: 99%

“…Moreover, there are two XML formats for BPMN processes: 1) XML Schema Definition (XSD) and 2) XML Metadata Interchange (XMI). However, XSD-based is the more popular format [53]. Additionally, there are three relevant aspects specific to the interchange formats: i) meta-model, ii) serialization (serial representation), and iii) mappings between a meta-model and serialization [54].…”

Section: Bpmn Model Interchange Working Group (Miwg)mentioning

confidence: 99%

“…There are two XML-based formats: the XML Metadata Interchange (XMI) and the XML Schema Definitions (XSDs), but the serialization is based on XML Schema Definitions (XSDs) [53]. There are also two types of definitions: model definitions and graphical definitions.…”

Section: Workflow (Wf) Business Rules (Br) Business Rule States (Brmentioning

confidence: 99%

“…There are also two types of definitions: model definitions and graphical definitions. The model definition describes the elements of the business process and their relations; while the graphical definitions describe the visualization aspects [53]. There are two dimensions that need to be considered during a business process serialization: the semantics of the meta-model elements when different representations are used, and the terms that describe the model elements [92].…”

Section: Workflow (Wf) Business Rules (Br) Business Rule States (Brmentioning

confidence: 99%

See 4 more Smart Citations

Process-Oriented Requirements Engineering: User-Centric LORS Framework

Al-Sabri¹,

Al‐Mashari²

2017

JSEA

View full text Add to dashboard Cite

In recent years, the process orientation requirements engineering field has received significant interest. However, dealing with ordinary users within an enterprise for developing as-is business process is very complex because this requires skills, responsibility, knowledge, and expertise of business processes. This research answers the following questions: 1) how to systematically gather information regarding as-is business process requirements in an informal environment and by non-expert users? and 2) how can an enterprise refine the identified business process with a semantic process model? The primary purpose of this research is to develop a supporting framework that is suitable for the definition of an as-is business process to be deployed within the enterprise environment. Hence, the focus is on gathering requirements to define the as-is business process. This framework concentrates on three significant aspects of this process: development, refinement, and serialization the semantics of the process model. To accomplish this objective, the LORS framework has been proposed, which consists of four phases (List, Order, Refinement, and Serialization). The framework presents a new unique technique to identify the business process, refine the process, and generate the model semantics. This study assumes that a simple and complete framework will help non-expert users define a high-quality as-is process, such that enhance and facilitate the matching process with existing reference models. We present a case study, evaluate the case study relative to specified criteria, and research the limitations and implications discovered from our research. This research concludes that the LORS framework is simple, flexible, visible, interactive, dynamic, and effective.

show abstract

Section: Bpmn Model Interchange Working Group (Miwg)mentioning

confidence: 99%

Section: Bpmn Model Interchange Working Group (Miwg)mentioning

confidence: 99%