Close the gap between analysis and design

Get robust

So we rewrote this part of the use case and added it into the diagram, and in the process we discovered another domain class (Delivery Address List). This is exactly the kind of scenario where robustness analysis proves invaluable - discovering hidden functionality and missing domain classes, just in time to begin designing.

Figure 5-29. The corrected robustness diagram excerpt for Exercise 5-3

The corrected robustness diagram

In the fourth and final excerpt from our book, we'll take a look at detailed design using a minimalist approach to sequence diagrams.

Use Case Driven Object Modeling with UML: Theory and Practice is available for purchase through Register Books, at the special price of £34.99. ®

Sponsored: Designing and building an open ITOA architecture