Object-oriented software engineering
Object-oriented software engineering
Object-oriented analysis and design with applications (2nd ed.)
Object-oriented analysis and design with applications (2nd ed.)
Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The OPEN toolbox of techniques
The OPEN toolbox of techniques
The unified software development process
The unified software development process
The road to the unified software development process
The road to the unified software development process
Advanced use case modeling: software systems
Advanced use case modeling: software systems
Writing Effective Use Cases
A Formal Approach to Use Cases and Their Relationships
«UML» '98 Selected papers from the First International Workshop on The Unified Modeling Language «UML»'98: Beyond the Notation
TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
Use Cases: Requirements in Context
Use Cases: Requirements in Context
Digging into Use Case Relationships
UML '02 Proceedings of the 5th International Conference on The Unified Modeling Language
Scenario construction tool based on extended UML metamodel
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Complementary use case scenario representations based on domain vocabularies
MODELS'07 Proceedings of the 10th international conference on Model Driven Engineering Languages and Systems
| Hi-index | 0.00 |
Use cases are a powerful and widely recognised tool for functional requirements elicitation and specification of prospective software applications. However, there still are major problems and misunderstandings about the use case approach. One of these is the troublesome notion of use case interleaving which is discussed in this work. Interleaving is still present in the current UML specification. A. Simons correctly realised that interleaving compares with goto/comefrom semantics that were already judged harmful by Dijkstra at the emergence of the Structured Programming era. Simons, thus, has requested the explicit dropping of interleaving semantics. The authors give further support for Simons request by showing that interleaving causes severe inconsistencies within UML and contradicts other proven and practically relevant use case concepts such as Goal-Based Use Cases of A. Cockburn, and contractual specifications of use cases expressed by pre- and postcondition approaches. Significant fixes to UML are proposed, in addition to those suggested by Simons. These will dramatically clarify prevailing problems and confusion with use cases and use case relationships among both practitioners and researchers.