Use case maps for object-oriented systems
Use case maps for object-oriented systems
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Use Case Maps for the Capture and Validation of Distributed Systems Requirements
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Evaluation and diagnosis of concurrency architectures
Evaluation and diagnosis of concurrency architectures
Modification analysis support at the requirements level
Ninth international workshop on Principles of software evolution: in conjunction with the 6th ESEC/FSE joint meeting
Comparing methodologies for the transition between software requirements and architectures
SMC'09 Proceedings of the 2009 IEEE international conference on Systems, Man and Cybernetics
Mining textual requirements to assist architectural software design: a state of the art review
Artificial Intelligence Review
A taxonomy for requirements engineering and software test alignment
ACM Transactions on Software Engineering and Methodology (TOSEM)
| Hi-index | 0.00 |
Two important aspects of future software engineering techniques will be the ability to seamlessly move from analysis models to design models and the ability to model dynamic systems where scenarios and structures may change at run-time. Use Case Maps (UCMs) are used as a visual notation for describing causal relationships between responsibilities of one or more use cases. UCMs are a scenario-based software engineering technique most useful at the early stages of software development. The notation is applicable to use case capturing and elicitation, use case validation, as well as high-level architectural design and test case generation. UCMs provide a behavioural framework for evaluating and making architectural decisions at a high level of design. Architectural decisions may be based on performance analysis of UCMs. UCMs bridge the gap between requirements and design by combining behaviour and structure in one view and by flexibly allocating scenario responsibilities to architectural components. They also provide dynamic (run-time) refinement capability for variations of scenarios and structure and they allow incremental development and integration of complex scenarios. Therefore, UCMs address the issues mentioned above.