Abstract

The ability to attribute behaviour to architecture is important for high-level understanding, designing, evolving, and reengineering all kinds of systems (from objectoriented programs to parallel and distributed computer systems). Scenarios are a good way of doing it, but popular scenario techniques, such as message sequence charts, that use intercomponent “wiring” as their starting point do not scale up well. Use case maps provide a new, scenario-based way of attributing behaviour to architecture that solves the scaleup problem. The notation enables compact, composite maps to be drawn to represent behaviour patterns of whole systems in terms of causal paths, without reference to “wiring”. Through an example, the paper aims to convince software and system engineers that the approach has depth and adds value, despite (and because of) its simplicity and deferment of detail.

Also available as Technical report SCE-96-02, Carleton University, Ottawa, Canada.

-- Gunter Mussbacher - 12 Oct 2005

Discussion

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