Just enough design
Original post: 10/27/2006
Here’s a nice article on UML. While some developers use UML even more don’t but should. I would guess that it’s often seen as overkill, providing detailed diagrams just to turn around and do detailed coding. This article restates the basic point that the level of your UML should match your goal. For many situations, generalized UML should be sufficient enough to provide an overall idea what the system is doing.
At any rate here’s a quick clip and a link.
“unless you are going to generate major parts of your application, I don’t see a real reason to try to be fully compliant to the UML standard–because the benefit you get from that is rather low. I think that it is more important to use UML to express high-level decisions and design. Then, (if needed…) reverse engineer the code to get detailed design. if you are doing detailed design in UML you’d probably be much quicker coding it anyway.” Arnon Rotem-Gal-Oz 9/19/06
http://www.ddj.com/blog/architectblog/archives/2006/09/on_using_uml.html
