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 runtime. 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.

-- JasonKealey - 12 Oct 2005


  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title Bridging the Requirements/Design Gap in Dynamic Systems with Use Case Maps (UCMs)
Authors D. Amyot and G. Mussbacher
Type Conference
Conference/Journal Title 23rd International Conference on Software Engineering (ICSE'01)
Month May
Year 2001
Pages 743-744
Keywords Architectural reasoning, design, model derivation, requirements,
scenarios, UCM styles, UML, URN, use cases.
Topic attachments
I Attachment Action Size Date Who Comment
icse01.pdfpdf icse01.pdf manage 40 K 12 Oct 2005 - 19:28 JasonKealey ICSE01
Topic revision: r2 - 09 Aug 2006, DanielAmyot
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback