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
Scenarios in System Development: Current Practice
IEEE Software
Evaluation and diagnosis of concurrency architectures
Evaluation and diagnosis of concurrency architectures
On the extension of UML with use case maps concepts
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Use Case Maps and Lotos for the prototyping and validation of a mobile group call system
Computer Communications
Applying reduction techniques to software functional requirement specifications
SAM'04 Proceedings of the 4th international SDL and MSC conference on System Analysis and Modeling
Abstract operational semantics for use case maps
FORTE'05 Proceedings of the 25th IFIP WG 6.1 international conference on Formal Techniques for Networked and Distributed Systems
| Hi-index | 0.00 |
A set of scenarios is a useful way to capture many aspects of the requirements of a system. Use Case Maps are a method for scenario capture which is good for describing multiple scenarios, including scenario interactions, for developingan architecture, and for analysing architectural alternatives. However, once a component architecture is determined, Message Sequence Charts are better for developing and presenting the details of interactions, and provide access to well-developed methodologies and tools for analysis and synthesis. This paper considers what must be specified in UCM scenarios and the architecture to make it possible to derive MSCs automatically, and it describes our experience in executingthese transformations within a prototype tool, the UCM Navigator.