Deriving use cases from business process models

17Citations
Citations of this article
34Readers
Mendeley users who have this article in their library.
Get full text

Abstract

Use cases are intended to capture the functional requirements of an information system. The problem of identifying use cases is however not satisfactorily resolved yet. The approach presented in this paper is to derive use cases from the business system models that are produced by applying DEMO (Demo Engineering Methodology for Organizations). These models have three attractive properties: essence, atomicity and completeness. Essence means that the real business things are identified, clearly distinguished from informational things. Atomic means that one ends up with things that are units from the business point of view. Complete means that no business things are overlooked and that the models do not contain irrelevant things. A three-step procedure is proposed for deriving use cases from these models, such that they do possess the same properties of essence, atomicity and completeness. © Springer-Verlag Berlin Heidelberg 2003.

Cite

CITATION STYLE

APA

Dietz, J. L. G. (2003). Deriving use cases from business process models. Lecture Notes in Computer Science (Including Subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 2813, 131–143. https://doi.org/10.1007/978-3-540-39648-2_13

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free