This paper discusses Use Case Maps (UCM), a scenario-based technique for modeling behavioral aspects of a system at a very high abstraction level. UCM is an informal notation that is easy to comprehend by humans. Its strong point is to show how things work generally. As such it can be used in the communication with stakeholders, including the non-technical inclined stakeholders (e.g., end-users). The notation is not strong enough to reason about system behavior in a formal sense. However, for validation purposes, UCMs can be augmented with specifications of component interfaces in order to reason about component compositions formally. UCM is an overlooked notation that has not received the attention it deserves. In particular, it can play an important role in software architecture to bridge the gap between requirements and the rather detailed design models offered by the Unified Modeling Language (UML). The goal of this paper is to show how UCM can play an important role in communication with stakeholders and validation of behavioral aspects of an architecture.

-- DanielAmyot - 11 Aug 2006


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

FormForVirtualLibrary edit

Title Use Case Maps A Technique for Communicating and Validating Behavioral Aspects of Architectures
Authors H. de Bruin
Type Conference
Conference/Journal Title Landelijk Architectuur Congres 2000
Month November
Year 2000
Pages 10
Keywords Component Interfaces, Software Architecture, Use Case Maps
Topic attachments
I Attachment Action Size Date Who Comment
LAC2000.pdfpdf LAC2000.pdf manage 105 K 11 Aug 2006 - 13:45 DanielAmyot Conference paper
Topic revision: r1 - 11 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