DERIVING USE CASES FROM BUSINESS PROCESSES The advantages of DEMO

Abstract

The mismatch between the business requirements and the actual functionality of the delivered software application is considered to be a crucial problem in current software development. Solving this problem means to find out how to consistently place the software specification model on a previously developed business process model. If considering in particular the UML-based software design, we need to answer in this regard a fundamental question, namely - how to find all relevant use cases, based on sound business process modeling? Adopting the business process modeling as a basis for identification of use cases has been studied from three perspectives - Language/Action Perspective, Organizational Semiotics and Petri Net. The goal of the current paper is to study and analyze the strengths of DEMO concerning the derivation of use cases. This could be helpful not only for the investigation of DEMO but also for the further activities directed towards finding out the most appropriate way(s) of identifying use cases from business processes.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 18 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.