Java™ Design: Objects, UML, and Process

9.4. Model Structure

In addition to the sequence diagrams that we'll create to design our system, we'll likely create a number of class diagrams. The way that we organize these diagrams definitely determines whether our model lives and grows with the system or becomes a monolith that is difficult to maintain and eventually is discarded.

As discussed in Chapter 4, it may be beneficial to create collaborations for each use case. We'll call this collaboration a use case realization. It's named appropriately because the sequence and class diagrams specify the behavior and structure of individual use cases. Therefore, we'll organize our model by associating each of the diagrams with their appropriate use case realization, which is effective because ...