Toward a methodology for case modeling

Hewelt, Marcin; Pufahl, Luise; Mandal, Sankalita; Wolff, Felix; Weske, Mathias

doi:10.1007/s10270-019-00766-5

Cited by 11 publications

(7 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…When the modeling task is complex, having a method-moreover if it is at least partially automated-eases the task, e.g., [25]. A method can be defined as the concepts, notation, and procedure that guide the structured execution of a complex task [26,27].…”

Section: Background and Related Workmentioning

confidence: 99%

Domain Model Based Design of Business Process Architectures

et al. 2022

View full text Add to dashboard Cite

A business process architecture (BPA) model depicts business processes in an organization and their relations. An artifact for generating BPA models is proposed as the outcome of a design science research project. The proposed artifact consists of a method (i.e., a set of concepts, a proposed notation, and a detailed procedure), which is termed the domain-based BPA (dBPA) method due to using domain models as a starting point. The dBPA method tackles issues of currently available approaches: lack of structured inputs, limited consideration of process relations types, and restricted use of industry-standard modeling languages. The paper formalizes the dBPA method and illustrates its application in the manufacturing industry. Evaluation of the dBPA method revealed that practitioners perceived it as useful to achieve its goal with the benefits of being objective and clear and allowing to create complete and understandable BPA models that enable the integration of processes and the software that automates them.

show abstract

Section: Background and Related Workmentioning

confidence: 99%

Domain Model Based Design of Business Process Architectures

et al. 2022

View full text Add to dashboard Cite

show abstract

“…Either, recipients can collect their parcels themselves or use the service of parcel delivery at a desired time frame by a local carrier, whereby the focus of the project is the latter one. Fragment-based case management consists of four basic concepts [6,8]: process fragments describing the flow of a case, the goal state describing when a case is finished, a data class diagram describing relevant data for a case and their structure, and finally, the object-life cycles for each data type describing the allowed changes on them.…”

Section: Fragment-based Case Management and Motivationmentioning

confidence: 99%

“…In fCM, not all of the fragments have to be used for the execution of a certain case to achieve the defined goal of the parcel delivery. Because fCM is both data-driven and event-driven, it is very important to have a valid Object-Lifecycle (OLC) which is consistent with the modeled fragments [8]. It describes the state transitions of each data object as shown in Fig.…”

Section: Fragment-based Case Management and Motivationmentioning

confidence: 99%

“…Motahari-Nezhad and Swenson [16] distinguish between adaptive and production case management; whereas the first one assumes that knowledge workers work very independently based on their knowledge which can quickly change, in the latter certain structure in the work exists which can be also defined at design time. Fragment-based Case Management (fCM) offers one way of implementing the Case Management approach as a hybrid variant between the two paradigms [8,9]. Nevertheless, it keeps the control-flow-based approach of process models in parts to ensure that certain processes are executed correctly.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Exception Handling in the Context of Fragment-Based Case Management

Andree

Ihde

Pufahl

2020

Enterprise, Business-Process and Information Systems Modeling

Self Cite

View full text Add to dashboard Cite

Case Management supports knowledge workers in defining, executing, and monitoring the handling of their cases, e.g. in healthcare or logistics. Fragment-based case management (fCM) allows to define a case model with the help of several process fragments, which can be flexible combined at run-time based on case characteristics and the case worker's intuition. Cases are often influenced by unknown exception, e.g., the sudden change of patient condition's or a storm delaying transports. So far, fCM only reacts to known circumstances. In this paper, we want to extend fCM by an exception handling approach. Thereby, existing exception patterns for workflow systems are used and extended by the fragment-level for handling unknown events. In order to enable direct integration and avoid a duplication of semantics, precise rules are specified in order to clarify how to extend which pattern in detail. The applicability of the developed exception handling technique is exemplified on a last mile delivery for parcels.

show abstract

“…Hewelt and Weske describe fCM, focusing on the language and syntax [11]. Consecutive works propose methods for eliciting [10] and verifying [13] case models. These works do not consider associations or cardinality constraints.…”

Section: Related Workmentioning

confidence: 99%

Technical Report: Refining Case Models Using Cardinality Constraints

Haarmann,

Montali,

Weske

2020

Preprint

Self Cite

View full text Add to dashboard Cite

Traditionally, business process management focuses on structured, imperative processes. With the increasing importance of knowledge work, semi-structured processes are entering center stage. Existing approaches to modeling knowledge-intensive business processes use data objects but fail to sufficiently take into account data object cardinalities. Hence, they cannot guarantee that cardinality constraints are respected, nor use such constraints to handle concurrency and multiple activity instances during execution. This paper extends an existing case management approach with data object associations and cardinality constraints. The results facilitate a refined data access semantics, lower and upper bounds for process activities, and synchronized processing of multiple data objects. The execution semantics is formally specified using colored Petri nets. The effectiveness of the approach is shown by a compiler translating case models to colored Petri nets and by a dedicated process execution engine.

show abstract

Toward a methodology for case modeling

Cited by 11 publications

References 30 publications

Domain Model Based Design of Business Process Architectures

Domain Model Based Design of Business Process Architectures

Exception Handling in the Context of Fragment-Based Case Management

Technical Report: Refining Case Models Using Cardinality Constraints

Contact Info

Product

Resources

About