Forschungsprojekt ECOMOD

Referenzgeschäftsprozesse und Strategien im E-Commerce

Forschungsgruppe Unternehmensmodellierung
08.07.2021
  Mapping Business Processes to WorkflowsDiese Seite auf Deutsch  

Overview
Approach

Business Process Modelling
Workflow Modelling
Conceptual Mapping
Implementation Issues
References




Approach
Towards Generating Software on the Basis of Business Processes
The implementation is based on the mapping of business process models to a workflow model and the appropriate configuration of a WfMS. The overall vision including applied software and corresponding documents as well as modelling languages is shown in the figure below.
The tool MetaEdit+ has been used for
  • modelling business processes (using the modelling language  MEMO-OrgML) and
  • mapping business processes to workflow-descriptions in  XPDL.
The Enhydra Shark workflow-engine has been applied as a runtime environment for workflows (for further details see  Implementation Issues):
  • The workflow-engine uses the generated workflow-descriptions for the execution of workflows.
  • Additionally, users can be managed and associated with workflow-participants inside the Shark-workflow-engine.
  • Java-applications can be developed and linked to workflow-applications in the workflow-engine.
Top
Overview of Models/Diagrams and their Relationships
The actual implementation of the mapping of business process models to a running application consists of four different diagram types. The figure below visualizes the different models togehter with an example for each diagram type.
Workflow Specification Diagram Process Decomposition
A workflow-specification diagram is the root-diagram for the generation of an XPDL-conformant workflow-specification. It contains all participants (one or more), workflow-data (zero or more), and applications required (zero or more) for the workflow-process. For further information see foundations of workflow modelling. The workflow-specification-diagram contains a reference to a process-decomposition containing all (sub-)processes used within the given workflow process. The root process of the decomposition-hierarchy (mandatory) represents the workflow process itself and additional decomposed processes are possible. At least one elementary process has to be assigned to each composed process in the decomposition-diagram using a decomposition-relationship. For further information see  foundations of business process modelling modelling.
Process Model Workflow Activity Specification Diagram
The control flow of every decomposed process has to be specified using a process-model-diagram. This diagram has to include all sub-processes of the given composed process (connected via a decomposition-relationship). For further information see foundations of business process modelling modelling. Every elementary process in the process-decomposition-diagram has to be further described using a workflow-activity-specification-diagram. This diagram contains the binding of workflow-relevant data (actual parameters) to the formal parameters of a workflow-application. For further information see foundations of workflow modelling.
Top