Sizing Use Cases: How to Create a Standard Metrical Approach
OOIS '02 Proceedings of the 8th International Conference on Object-Oriented. Information Systems
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
Digging into Use Case Relationships
UML '02 Proceedings of the 5th International Conference on The Unified Modeling Language
Tool support for more precise use case specifications
Proceedings of the Warm Up Workshop for ACM/IEEE ICSE 2010
CAiSE'10 Proceedings of the 22nd international conference on Advanced information systems engineering
User requirements modeling and analysis of software-intensive systems
Journal of Systems and Software
On the refinement of use case models with variability support
Innovations in Systems and Software Engineering
Scenario construction tool based on extended UML metamodel
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
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
Analysis of techniques for documenting user requirements
ICCSA'12 Proceedings of the 12th international conference on Computational Science and Its Applications - Volume Part IV
Fixing Generalization Defects in UML Use Case Diagrams
Fundamenta Informaticae - Concept Lattices and Their Applications
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 |
This article traces the unstable semantics of use cases from Jacobson to UML 1.3. The UML 1.1 metamodel formally defined the "uses" and "extends" use case relationships as stereotypes of generalisation, yet both received interpretations that varied between inheritance and composition, reflecting a large degree of confusion among developers. The recently revised UML 1.3 has quietly dropped these in favour of new "include" and "extend" relationships, which are styled instead as kinds of dependency. Despite this change, the deployment of use case diagrams encourages analysts to conceptualise and develop models which conceal arbitrary jumps in the flow of control, corresponding to goto and comefrom statements, and in which unpleasant non-local dependencies exist across modules. A discussion of examples reveals how a conscientious designer must disassemble use case models completely to produce properly- structured code. A radical solution is proposed.