Chapter 4. Analysis

Table of Contents

4.1. Introduction
4.2. The Analysis Process (To be written)
4.2.1. Output of the Analysis Process (To be written)
4.3. Class Diagrams (To be written)
4.3.1. The Class Diagram (To be written)
4.3.2. Advanced Class Diagrams (To be written)
4.4. Creating Class Diagrams in ArgoUML
4.4.1. Classes
4.4.2. Associations (To be written)
4.4.3. Class Attributes and Operations (To be written)
4.4.4. Advanced Class Features (To be written)
4.5. Sequence Diagrams (To be written)
4.5.1. The Sequence Diagram (To be written)
4.5.2. Identifying Actions (To be written)
4.5.3. Advanced Sequence Diagrams (To be written)
4.6. Creating Sequence Diagrams in ArgoUML
4.6.1. Sequence Diagrams
4.6.2. Actions (To be written)
4.6.3. Advanced Sequence Diagrams (To be written)
4.7. Statechart Diagrams (To be written)
4.7.1. The Statechart Diagram (To be written)
4.7.2. Advanced Statechart Diagrams (To be written)
4.8. Creating Statechart Diagrams in ArgoUML
4.8.1. Statechart Diagrams (To be written)
4.8.2. States (To be written)
4.8.3. Transitions (To be written)
4.8.4. Actions (To be written)
4.8.5. Advanced Statechart Diagrams (To be written)
4.9. Realization Use Cases (To be written)
4.10. Creating Realization Use Cases in ArgoUML (To be written)
4.11. Case Study (To be written)
4.11.1. Concept Class Diagrams (To be written)
4.11.2. System Sequence Diagrams (To be written)
4.11.3. System Statechart Diagrams (To be written)
4.11.4. Realization Use Cases (To be written)

4.1. Introduction

Analysis is the process of taking the “customer” requirements and re-casting them in the language of, and from the perspective of, a putative solution.

We are not actually trying the flesh out the detailed solution at this stage. That occurs in the Design Phase (see Chapter 5, Design).

Unlike the boundary between Requirements and Analysis Phases, the boundary between Analysis and Design Phases is inherently blurred. The key is that analysis should define the solution no further than is necessary to specify the requirements in the language of the solution. The artifacts in Analysis generally represent a high level of abstraction.

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