Hinkelmann, Knut

Hinkelmann, Knut


Gerade angezeigt 1 - 3 von 3
  • Publikation
    Business Process Flexibility and Decision-aware Modeling - The Knowledge Work Designer
    (Springer, 2016) Hinkelmann, Knut; Karagiannis, Dimitris; Mayr, Heinrich C.; Mylopoulos, John [in: Domain-Specific Conceptual Modeling]
    This chapter describes the Knowledge Work Designer, a modelling method for knowledge work. It is based on two principles: (1) the separation of business logic and process logic and (2) the support of both structures and unstructured knowledge. Process logic can be represented in a structured way in BPMN and in a non-structured way with CMMN. For real processes there is no strict separation between structured processes and cases. Therefore the Knowledge Work Designer offers a deep integration of BPMN and CMMN. Business logic can be represented in a structured way using decision tables. Unstructured business logic can be represented in documents. The separation of business logic and process logic allows for simpler process model and easier maintenance.
    04 - Beitrag Sammelband oder Konferenzschrift
  • Publikation
    Integration of BPMN and CMMN
    (12.06.2015) Hinkelmann, Knut
    In this presentation an integration between the two OMG standards Business Process Model and Notation (BPMN) and Case Management Model and Notation (CMMN) is proposed. The presentation was given at an in OMG technical meeting.
    06 - Präsentation
  • Publikation
    Combining Process Modelling and Case Modeling
    (2014) Hinkelmann, Knut; Pierfranceschi, Arianna [in: 8th International Conference on Methodologies, Technologies and Tools enabling e-Government MeTTeG14]
    Adaptive Case Management deals with processes that are not predefined or repeatable, but depend on evolving circumstances and decisions regarding a particular situation. While case management is often considered as different from conventional business process management, in reality they cannot be strictly separated. A structured business process can contain parts which deal with non-routine cases. The Object Management Group (OMG) published the Business Process Model & Notation (BPMN) as well as the Case Management Model & Notation (CMMN). There is an ongoing debate whether these two languages should be combined are kept independent. After a short introduction into CMMN and BPMN we analyse an application process as it is typical for public administration in order to identify strengths and weaknesses of both BPMN and CMMN. We show that typical processes contain both structured and non-structured parts and neither BPMN nor CMMN alone is adequate to model the process. Finally, we propose recommendations for a metamodel, which combines elements of BPMN and CMMN.
    04B - Beitrag Konferenzschrift