Chapter 5. Design

Table of Contents

5.1. Introduction
5.2. The Design Process (To be written)
5.2.1. Output of the Design Process (To be written)
5.3. Package Diagrams (To be written)
5.3.1. The Package Diagram (To be written)
5.3.2. Advanced Package Diagrams (To be written)
5.4. Creating Package Diagrams in ArgoUML
5.4.1. Packages
5.4.2. Relationships between packages (To be written)
5.4.3. Advanced Package Features (To be written)
5.5. More on Class Diagrams (To be written)
5.5.1. The Class Diagram (To be written)
5.5.2. Advanced Class Diagrams (To be written)
5.6. More on Class Diagrams in ArgoUML (To be written)
5.6.1. Classes (To be written)
5.6.2. Class Attributes and Operations (To be written)
5.6.3. Advanced Class Features
5.7. Sequence and Collaboration Diagrams (To be written)
5.7.1. More on the Sequence Diagram (To be written)
5.7.2. The Collaboration Diagram (To be written)
5.7.3. Advanced Collaboration Diagrams (To be written)
5.8. Creating Collaboration Diagrams in ArgoUML (To be written)
5.8.1. Collaboration Diagrams (To be written)
5.8.2. Messages (To be written)
5.8.3. Advanced Collaboration Diagrams (To be written)
5.9. Statechart Diagrams (To be written)
5.9.1. The Statechart Diagram (To be written)
5.9.2. Advanced Statechart Diagrams (To be written)
5.10. Creating Statechart Diagrams in ArgoUML (To be written)
5.10.1. Statechart Diagrams (To be written)
5.10.2. States (To be written)
5.10.3. Transitions (To be written)
5.10.4. Actions (To be written)
5.10.5. Advanced Statechart Diagrams (To be written)
5.11. Activity Diagrams (To be written)
5.11.1. The Activity Diagram (To be written)
5.12. Creating Activity Diagrams in ArgoUML (To be written)
5.12.1. Activity Diagrams (To be written)
5.12.2. Action States (To be written)
5.13. Deployment Diagrams (To be written)
5.13.1. The Deployment Diagram (To be written)
5.14. Creating Deployment Diagrams in ArgoUML (To be written)
5.14.1. Nodes (To be written)
5.14.2. Components (To be written)
5.14.3. Relationships between nodes and components (To be written)
5.15. System Architecture (To be written)
5.16. Case Study (To be written)
5.16.1. Packages (To be written)
5.16.2. Class Diagrams (To be written)
5.16.3. Sequence Diagrams (To be written)
5.16.4. Collaboration Diagrams (To be written)
5.16.5. Statechart Diagrams (To be written)
5.16.6. Activity Diagrams (To be written)
5.16.7. The Deployment Diagram (To be written)
5.16.8. The System Architecture (To be written)

5.1. Introduction

We now have the problem we are trying to solve specified in the language of a putative solution. In the Design Phase, we construct all the details of that solution.

The blurred boundary between Analysis and Design is reflected in their use of many of the same UML tools. In this chapter we will mostly be reusing UML technology we have already met once. The big step is casting everything into concrete terms. We move from the abstract concepts of analysis to their concrete realization.

Once again the recursive, and iterative nature of our process means we will come back to the Design phase many times in the future.