Introduction

The purpose of the Analysis and Design workflow is to model your software. During the Construction phase, this workflow focuses on evolving your analysis model based on your requirements model and further evolving your design model to describe how you intend to build your software. Your primary goal is to develop a detailed design model based on the collection of models your software architecture document (SAD), requirements model, business model, and enterprise models defined in other workflows. You will perform modeling techniques such as class modeling, sequence diagramming, collaboration diagramming, persistence modeling, state modeling, and component modeling. The other goals of this workflow during the Construction phase are to a) adapt your design to your implementation environment and b) to finalize your user interface design. Your design must not only reflect your models, it should also reflect the target environment of your organization, including the unique features of the programming language(s) you will work in and the persistent storage mechanism (e.g., a relational database) that you will store your objects in. Furthermore, although user interface prototyping is an important activity of the Requirements workflow covered in volume 1, The Unified Process Inception Phase (Ambler, 2000a) the final user interface design effort is actually part of your Analysis and Design workflow activities. During the Requirements workflow, the purpose of user interface prototyping is to understandthe requirements for your software and to communicate your understanding of those requirements. It is then evolved, as part...