Object-oriented software engineering
Object-oriented software engineering
OPEN modeling language (OML) reference manual
OPEN modeling language (OML) reference manual
Question time! about use cases
Proceedings of the 13th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Using Uml: Software Engineering with Objects and Components
Using Uml: Software Engineering with Objects and Components
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
Evaluating UML using a generic quality framework
UML and the unified process
Getting 'Whole Picture' Behavior In A Use Case Model
Journal of Integrated Design & Process Science
A methodology of visual modeling language evaluation
SOFSEM'05 Proceedings of the 31st international conference on Theory and Practice of Computer Science
Describing use cases with activity charts
MIS'04 Proceedings of the 2004 international conference on Metainformatics
A comparative analysis of use case relationships
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
Fixing Generalization Defects in UML Use Case Diagrams
Fundamenta Informaticae - Concept Lattices and Their Applications
| Hi-index | 0.00 |
Use case diagrams are one of the key concepts in the Unified Modeling Language, but their semantics and notation have some gaps that lead to frequent misunderstandings among practitioners, even about very basic questions. In this paper we address some issues regarding the relationships in which use cases may take part. The Include and Extend relationships between two use cases have presently an inconsistent definition, since they are represented as stereotyped dependencies, but they are not true dependencies in the metamodel. Besides, the direction of the dependency arrow in the Extend relationship can be misleading, unnatural and difficult to understand for the common practitioner. Finally, we show also some conceptual problems regarding the included or extending use cases, which in our opinion are not true use cases.