A Design Methodology for Workflow System Development

Kim, Jaehyoun; Carlson, C. Robert

doi:10.1007/3-540-36233-9_2

Cited by 1 publication

(5 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…So far, surprisingly little research has been performed on this topic. In [37,23,12,21,22] different approaches regarding this topic are described. These approaches differ in the number of phases that need to be followed, the steps in these phases, and the scope of the development methodology.…”

Section: Related Workmentioning

confidence: 99%

“…In contrast, [12,21] propose specific modeling techniques that have to be used during the development process. In [12], UML descriptions are proposed for identifying business process requirements.…”

Section: Related Workmentioning

confidence: 99%

“…Then the WIDE meta-model is used to design an implementation independent workflow schema and associated exception handling which can then subsequently mapped to the required workflow language. In [21], UML use cases and UML interaction diagrams are used to develop a so-called multi-level workflow schema which provides an abstraction of the workflow at different levels.…”

Section: Related Workmentioning

confidence: 99%

“…This provides various possibilities for verification whereas in [12,21] different modeling mechanisms are mentioned but nothing is said about the verification of these models. Moreover, as both the EUC and CWN use the same language, this allows for a seamless integration between the requirements and design phase.…”

Section: Related Workmentioning

confidence: 99%

“…Moreover, as both the EUC and CWN use the same language, this allows for a seamless integration between the requirements and design phase. None of the approaches described in [37,23,12,21,22] report on obtained experiences when applying the proposed approach.…”

Section: Related Workmentioning

confidence: 99%

See 4 more Smart Citations

From Requirements via Colored Workflow Nets to an Implementation in Several Workflow Systems

Mans

Aalst

Russell

et al. 2009

Transactions on Petri Nets and Other Models of Concurrency III

View full text Add to dashboard Cite

Abstract. Hospitals and other healthcare organizations need to support complex and dynamic workflows. Moreover, these processes typically invoke a number of medical disciplines. This makes it important to avoid the typical disconnect between requirements and the actual implementation of the system. In this paper we apply a development approach where an Executable Use Case (EUC) and a Colored Workflow Net (CWN) are used to close the gap between a given requirements specification and the realization of these requirements based on workflow technology. In order to do so, we describe a large case study where the diagnostic process of the gynecological oncology care process of the Academic Medical Center (AMC) hospital is used as a candidate process. The process consists of hundreds of activities. These have been modeled and analyzed using an EUC and a CWN. Moreover, based on the CWN, the process has been implemented using four different workflow systems. In this way, we demonstrate the general application of the approach and its applicability to distinct technology systems.

show abstract

Section: Related Workmentioning

confidence: 99%