Analysis and design bridge the gap between requirements and implementation. This workflow uses use cases to identify a set of objects that is subsequently refined into classes, subsystems, and packages.
Responsibilities in analysis and design are distributed among the roles Software Architect (the big picture issues), Designer (the details), and Database Designer (the details that require specialized knowledge about handling persistence).
Analysis and design result in a design model, which can be abstracted using three architectural views. The logical view presents the decomposition of the system into a set of logical elements (classes, subsystems, packages, and collaborations). The process view maps those elements to the processes and threads in the systems. The deployment view maps the processes to a set of nodes on which they execute.
The design of the user interface proceeds in parallel, resulting in a user-interface prototype.
In some cases, a separate analysis model can be useful for presenting an overview or abstraction of the system or to bootstrap the design activities.
