Path: csiph.com!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Fredrik Jonson Newsgroups: comp.lang.java.programmer Subject: Re: Do C++ and Java professionals use UML?? Date: 20 Jul 2012 07:16:46 GMT Lines: 23 Message-ID: References: <7b5978a1-16bd-4700-acd8-b6446f5c3218@j4g2000yqf.googlegroups.com> X-Trace: individual.net KMqwdN0E3Hlu5n0h2/5vLA3WS4Unm2VHJ/mLTxfhpnfL2vavhdZCiDkFR01anPYgA= Cancel-Lock: sha1:Fia7cs9DboNPH+oR0SurWULp0YY= User-Agent: slrn/pre1.0.0-18 (Linux) Xref: csiph.com comp.lang.java.programmer:16139 In Roedy Green wrote: > I think the biggest problem [of UML] comes with keeping it up > to date. The more expensive UML tools have round trip engineering which makes keeping it up to date with code less of a hassle. My limited experience with round trip engineering is that has its own weakness; it picks up all minor parts of the code too, including things that are not necessarily is important to get the main picture of the design. Still, as others already mentioned, it is convenient to have a common design language that is not implementation specific, and that is known by most programmers out there. That's the strength of UML. Never mind the fancy tools, which gets in your way, UML is first and foremost valuable as a language to communicate design among your peers. Myself, I mostly use class diagrams and sequence diagrams to introduce a design to other developers. In most cases the diagrams never go further than a whiteboard. When I have to, I use Umlet to persist them too. -- Fredrik Jonson