Use Case Maps for Object-Oriented Systems

Rating:
Summary: A Notation with Uniquely Useful Capabiliites
Review: Use case maps provide a unique method of linking the high-level functional specification of system behavior to traditional object-oriented notations. Traditional notations focus almost exclusively on the behavior of individual system components. They are essential for definition of behavior specific components but offer little to no insight into how components interwork to meet overall system objectives. System objectives that are essential to defining customer value are obscured in detailed considerations of specific component behavior. Use case maps provide a unique way of viewing system behavior.

UML activity diagrams provide some of the same services but have difficulty with things that use case maps excel at. Use case maps by avoiding early commitments allow the evaluation of architectural alternatives. They allow specifiers and designers to keep their minds open to new opportunities by avoiding an early transition to specific implementation issues. Architectural alternatives may be specified and evaluated easily in the use case map notation.

The use case map ability to easily adapt to and handle uncertainties in requirements and operation will become even more important as time goes on. It is a commonplace observation now that no new systems are built. Development is about evolving an existing system to meet new requirements. This is something that use case maps can do very well. They capture system operation above the technological details of implementation. They focus on identifying and clarifying behavior and so can point out the issues that must be addressed in system evolution. The maps can be coupled to various architectures and so can maintain and so maintain their meaning with and can be used to evaluate a variety of implementation architectures that are proposed for system evolution.

The ability of the maps to adapt allows them to be used to specify systems that must dynamically adapt to user and network behavior. This is an important class of system now and will become even more important as more and more applications move to the network mode of operation.

Use case maps have found a following in the research community and tools are being built that allow performance predictions, function test cases, non-functional analysis and others to be carried out on use case map specifications.

The book is clear with good examples. It covers both the notation itself and the means to best apply it. This is a very worthwhile book that will be of interest to anyone with interests in requirements engineering, software engineering or design methodologies in general. It is well worth reading.