A BPM Lifecycle Plug-in for Modeling Methods Agility

Business Process Management literature has proposed several BPM lifecycles on a level of abstraction that is modeling method -agnostic, i.e. they consider the modeling language and tool support an underlying invariant or technological concern. While remaining on the same abstraction layer, we highlight a method agility requirement observed in commercial BPM consulting projects - concretely, it manifests as change requests for the modeling language or tool, from one lifecycle iteration to the next, leading to situations of model value co-creation as customer demands are assimilated in the modeling method. Based on a conceptualization of such situations, a lifecycle plug-in is proposed in the form of a methodology and associated tool support, allowing for responsive evolution of the adopted modeling method with impact on several lifecycle phases. Historical examples from the evolution of a BPM product are provided to illustrate and classify the demands that motivate the existence of this lifecycle plug-in

Semantic Bridging between Conceptual Modeling Standards and Agile Software Projects Conceptualizations

Software engineering benefitted from modeling standards (e.g. UML, BPMN), but Agile Software Project Management tends to marginalize most forms of documentation including diagrammatic modeling, focusing instead on the tracking of a project\u27s backlog and related issues. Limited means are available for annotating Jira items with diagrams, however not on a granular and semantically traceable level. Business processes tend to get lost on the way between process analysis (if any) and backlog items; UML design decisions are often disconnected from the issue tracking environment. This paper proposes domain-specific conceptual modeling to obtain a diagrammatic view on a Jira project, motivated by past conceptualizations of the agile paradigm while also offering basic interoperability with Jira to switch between environments and views. The underlying conceptualization extends conceptual modeling languages (BPMN, UML) with an agile project management perspective to enrich contextual traceability of a project\u27s elements while ensuring that data structures handled by Jira can be captured and exposed to Jira if needed. Therefore, concepts underlying the typical software development project management are integrated with established modeling concepts and tailored (with metamodeling means) for the domain-specificity of agile project management. A Design Science approach was pursued to develop a modeling method artifact, resulting in a domain-specific modeling tool for software project managers that want to augment agile practices and enrich issue annotation

A Model-Based Approach Towards the Conceptualization of Digital Twins: The Case of the EU-Project COGITO

In agile business ecosystems, digitalization is a key enabler for agility and flexibility. However, digital transformation is often challenging for instance due to unclear definitions and a lack of problem understanding. In this work this complexity is addressed with a model-based approach for conceptualizing digitalization and related meta modelling activities to enable the conceptual integration of diverse concepts. Existing modelling approaches – BPMN and ArchiMate – are leveraged with domain specific considerations that are relevant for the digitalization. The construction use case from the European project COGITO serves as a foundation for ideation and first requirements engineering. Physical experiments in the OMiLAB Innovation Environment are used as an experimental method towards identifying relevant digital twinning concepts, while modelling methods can be seen as an integration platform for physical and digital elements. Key digitalization aspects towards digital twinning are discussed and conceptualized in a meta model