8.3. Model Structure
As we may now suspect, a single system can contain many sequence diagrams. The way that we organize these sequence diagrams definitely contributes to the likelihood that our model lives and grows with the system, versus it becoming 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. As described earlier, we call this collaboration a use case realization. It's named appropriately because the sequence diagrams (and in Chapter 9, the class diagrams) specify the behavior of individual use cases as a set of interacting objects (of course, the class diagrams specify the structure). Therefore, we'll organize our model by ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access