Use case maps for object-oriented systems
Use case maps for object-oriented systems
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Use Case Maps as Architectural Entities for Complex Systems
IEEE Transactions on Software Engineering
Turning clockwise: using UML in the real-time domain
Communications of the ACM
On the Role of Activity Diagrams in UML - A User Task Centered Development Process for UML
«UML» '98 Selected papers from the First International Workshop on The Unified Modeling Language «UML»'98: Beyond the Notation
Use Case Maps for the Capture and Validation of Distributed Systems Requirements
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Evaluating Concurrency Options in Software Specifications
MASCOTS '99 Proceedings of the 7th International Symposium on Modeling, Analysis and Simulation of Computer and Telecommunication Systems
UCM-ROOM modelling: from use case maps to communicating state machines
ECBS'97 Proceedings of the 1997 international conference on Engineering of computer-based systems
Use Case Maps and Lotos for the prototyping and validation of a mobile group call system
Computer Communications
Proceedings of the 24th International Conference on Software Engineering
Deriving Message Sequence Charts from Use Case Maps Scenario Specifications
SDL '01 Proceedings of the 10th International SDL Forum Copenhagen on Meeting UML
Software Performance Models from System Scenarios in Use Case Maps
TOOLS '02 Proceedings of the 12th International Conference on Computer Performance Evaluation, Modelling Techniques and Tools
Introduction to the user requirements notation: learning by example
Computer Networks: The International Journal of Computer and Telecommunications Networking - ITU-T system design languages (SDL)
Software performance models from system scenarios
Performance Evaluation
Telecommunications Systems - Modeling, analysis, design and management
Getting 'Whole Picture' Behavior In A Use Case Model
Journal of Integrated Design & Process Science
Advanced steps with standardized languages in the re-engineering process
Computer Standards & Interfaces
Specifying Component Behavior with Port State Machines
Electronic Notes in Theoretical Computer Science (ENTCS)
URN: towards a new standard for the visual description of requirements
SAM'02 Proceedings of the 3rd international conference on Telecommunications and beyond: the broader applicability of SDL and MSC
Understanding existing software with use case map scenarios
SAM'02 Proceedings of the 3rd international conference on Telecommunications and beyond: the broader applicability of SDL and MSC
MASD: Multi-agent systems development methodology
Multiagent and Grid Systems
Functional and non-functional requirements specification for enterprise applications
PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
Partial order semantics of sequence diagrams for mobility
SMTT'03 Proceedings of the 2003 international conference on Scenarios: models, Transformations and Tools
Use case modeling and refinement: a quality-based approach
ER'06 Proceedings of the 25th international conference on Conceptual Modeling
| Hi-index | 0.01 |
Descriptions of reactive systems focus heavily on behavioral aspects, often in terms of scenarios. To cope with the increasing complexity of services provided by these systems, behavioral aspects need to be handled early in the design process with flexible and concise notations as well as expressive concepts. UML offers different notations and concepts that can help describe such services. However, several necessary concepts appear to be absent from UML, but present in the Use Case Map (UCM) scenario notation. In particular, Use Case Maps allow scenarios to be mapped to different architectures composed of various component types. The notation supports structured and incremental development of complex scenarios at a high level of abstraction, as well as their integration. UCMs specify variations of run-time behavior and scenario structures through sub-maps "pluggable" into placeholders called stubs. This paper presents how UCM concepts could be used to extend the semantics and notations of UML for the modeling of complex reactive systems. Adding a "UCM view" to the existing UML views can help bridging the gap separating requirements and use cases from more detailed views (e.g. expressed with interaction diagrams and statechart diagrams). Examples from telecommunications systems are given and a corresponding design trajectory is also suggested.