Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • I couldn't seem to find that reference.. Commented Mar 20, 2011 at 22:45
  • I double-checked the link and it was ok so then I assume you mean where in the book? Chapter 14 is about when and how to draw diagrams. I now see I paraphrased it impresisely: "It is best to explore dynamic scenarios first and then determine their implications on the static structure. It is important to evolve the dynamic and static diagrams together, using very short iterative cycles ...". I couldn't find the documentation-part. The points are: 1. A complete model in diagrams is not that much cheaper than working code, 2. Diagrams are not testable so the design cannot be confirmed. Commented Mar 21, 2011 at 9:59
  • +1 for two reasons: class diagrams can easily be extracted from the code (could even be part of the build process) and, more importantly, behavior first. Alan Kay did say that OO was about messages being exchanged. Commented Mar 21, 2011 at 17:28