Figure 1-3: Class Diagrams Map Out the Structure of the Code
Figure 1-4: Sequence Diagrams Help Us Allocate Operations (Behavior) to Classes
Figure 1-5: Robustness Diagrams Close the Gap Between Requirements and Detailed Design
Figure 1-6: Referencing Domain Objects by Name Removes Ambiguity from the Use Cases
Figure 1-7: The ICONIX Process—A Streamlined Approach to UML Modeling
Figure 5-2: Robustness Analysis Bridges the Gap Between What and How
Figure 5-3: Robustness Analysis Helps You Refine the Use Case Text and the Domain Model
Figure 5-6: Domain Model with Attributes for The Internet Bookstore
Figure 6-1: Preliminary Design Review and the ICONIX Process
Figure 7-1: Sequence Diagrams Drive the Allocation of Behavior to Software Classes
Figure 7-3: Static Model for The Internet Bookstore (Part 1)
Figure 7-4: Static Model for The Internet Bookstore (Part 2)
Figure 7-5: Static Model for The Internet Bookstore (Part 3)
3.143.111.233