Object-oriented software engineering
Object-oriented software engineering
Object-oriented modeling and design
Object-oriented modeling and design
Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
The unified software development process
The unified software development process
Use case driven object modeling with UML: a practical approach
Use case driven object modeling with UML: a practical approach
A language facility for designing database-intensive applications
ACM Transactions on Database Systems (TODS)
Writing Effective Use Cases
Object-Oriented Software Construction
Object-Oriented Software Construction
TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
A UML-Based Pattern Specification Technique
IEEE Transactions on Software Engineering
Unified Modeling Language Reference Manual, The (2nd Edition)
Unified Modeling Language Reference Manual, The (2nd Edition)
Modeling and Composing Scenario-Based Requirements with Aspects
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
SPLC '06 Proceedings of the 10th International on Software Product Line Conference
An approach for aspect-oriented use case modeling
Proceedings of the 13th international workshop on Early Aspects
Precise specification of use case scenarios
FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
Open issues in industrial use case modeling
UML'04 Proceedings of the 2004 international conference on UML Modeling Languages and Applications
Fixing Generalization Defects in UML Use Case Diagrams
Fundamenta Informaticae - Concept Lattices and Their Applications
Hi-index | 0.00 |
A use case is a description of the interactions of a system with the actors that use it. The Achilles' heel of use cases is the unclear UML semantics, in particular the definition of the extend relationship. This article is an attempt to clarify the semantics of the extension mechanism. In particular, we advocate for the application of the open-closed principle, adding modification details in the extending use case, instead of in the base case. A revision of the UML standard would be impractical, but a disciplined reinterpretation of the extend and extension point concepts could represent a great improvement. Textual and graphical approaches (based in the UML Behavior meta-model) are considered. Using these recommendations, the base use cases can be independently described, while the extending use cases will be self-contained.