Don't model or apply the UML to all or most of the software design. Defer simple or straightforward design problems until programming—solve them while programming and testing. Model and apply the UML for the smaller percentage of unusual, difficult, tricky parts of the design space.
- 2. Iterative, Evolutionary, and Agile
- from Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, Third Edition
- Publisher: Prentice Hall
- Released: October 2004
that's why UML should not be used as a blueprint, it should only help us visualize the problem (and the responsibilities) in a more graphical way, than programming
Share this highlighthttp://www.safaribooksonline.com/a/applying-uml-and/51383/