Part 5. Additional Topics

Some projects have needs that extend beyond the advanced use case modeling process framework presented in Part 3. In this part, we provide additional topics that may be added to your use case modeling repertoire.

Chapter 16 discusses conceptual user interface modeling. This topic may be of interest to developers who have large, complex graphical user interfaces. Other projects may not require the level of sophistication that this chapter provides. For example, many embedded systems have little or no user interface.

Change is another area that affects some projects more than others. Many management information system projects suffer from “requirements creep,” or a rate of change in the requirements that threatens the success of the project. Chapter 17 provides the tools for managing change in the use case model.

Formal process definition is critical to achieving ISO 9001 certification and a requirement for high-ceremony projects [Miller 2000]. Since advanced use case modeling is a process framework, it must be customized to the level of detail necessary to meet the needs of your project. Chapter 18 describes how to identify the pieces of the process necessary for your project. This chapter presents the artifacts most often chosen by projects based on their level of ceremony. It also outlines a documentation methodology called the development case that comes from the Rational Unified Process.

Chapter 19 presents some of the elements necessary for building a quality use case model. Some of the properties of a good requirements document are applied to the use case model to illustrate the best way to ensure their quality. Many of these properties are based on common sense. Creating a quality use case model involves iteration. This model may then be utilized to drive the downstream software development process. The creation of delivery increments is briefly explained with respect to use case prioritization.