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.

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. ®

Related stories

• 10 ways to improve your code (10 March 2008)
• Time for UML tools to evolve (29 February 2008)
• Agile lands role in games and business software (28 February 2008)
• UML officially an unfunny matter (20 February 2008)
• Tools vendors stuck on UML and agility (13 February 2008)
• Penguin-powered UML modeling (29 January 2008)
• Dip into concept programming (16 January 2008)
• Telltale signs your model is stuck (3 January 2008)
• Sequence diagramming that's fit for purpose (22 December 2007)
• Why simplicity starts with design (16 December 2007)
• Bloody code! (4 December 2007)
• Model use cases that work (23 November 2007)
• The ICONIX Process in pieces: Domain modelling (13 November 2007)
• A simple unit test for GUIs (12 November 2007)
• Designing software for testability (29 October 2007)
• Don't unit test GUIs (22 October 2007)
• Why UML won't save your project (8 October 2007)
• Disintermangling use case scenarios from requirements (17 August 2007)
• Use case driven object modelling with UML: Theory and practice (29 March 2007)
• Vague and ambiguous use cases (26 February 2007)