Welcome to D
SIGMOD 2004
PODS 2004
SIGMOD RECOR
CIKM 2004
DASFAA 2004
DBPL 2003
DE-BULLETIN
DEBS 2004
DMKD 2004
DMSN 2004
DOLAP 2004
DPDJ 2004
EDBT 2004
ER 2003
<<< = ER'03 Papers>>>
GIS 2004
HDP 2004
HYPERTEXT 20
ICDE 2004
ICDT 2003
JCDL 2004
MDM
MIR 2004
MIS 2004
MMDB 2004
MOBIDE 2003
RIDE 2004
SBBD 2003
SIGIR FORUM
SIGIR 2004
SIGKDD EXPLO
SIGKDD 2004
SSDBM 2004
SSTD 2003
TIME 2004
TODS 2004
VLDB 2004
VLDB Journal
WEBDB 2004
WIDM 2004
XIME-P 2004
Footer

Deriving Use Cases from Business Process Models


Jan L.G. Dietz

  View Paper (PDF)  

Return to Metamodeling and Methodology


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.


©2005 Association for Computing Machinery