I don't think this article covers "all you need to know" particularly well.
All You Need to Know About UML Diagrams
11–20 of 36 posts
Re: All You Need to Know About UML Diagrams
#12neat, the pictures could be better doh
You are right, pictures should be better focused and more unified in style. Can you recommend any software?
PlantUML[1] is pretty decent, especially if you like keeping the contents of the diagram in easily-versioned text.
[1]: http://plantuml.com/
Re: All You Need to Know About UML Diagrams
#13“The relation between different classes (represented by a connecting line), makes up a class diagram.”
Taken from class diagrams. Not everything you need to know it seems. It misses multiplicity at least. (Didn’t read/scan more)
Also, did you really intend to have one-to-many for both client and account? Since you labeled owns. One client multiple accounts is ok for the sample. One account can have multiple owners (clients) in theory but for the introduction (audience is I guess the inexperienced) I would go with 1.
Re: All You Need to Know About UML Diagrams
#14UML Diagrams are actually quite useful, sometimes you just need a structured way to reason about software.
There are two types of useful UML:
The first is what I call whiteboard UML - it looks like any UML course except you draw it on a whiteboard, snap a picture on your phone and start implementing it. A couple weeks latter you realize that the design has diverged from the whiteboard so you delete the pictures. The whiteboard was useful for those two weeks to get the discussion started.
The second is maintained, preferably automated. If you use viseo that means an entire team who's only job is to police the code to ensure everybody updates as change happens. Lesson: don't use viseo, use a tool that either generates your code (in C like languages this would be the header files), or a tool that imports the actually code to create diagrams. In either case the reason you do this is because every week you print the diagram out on poster paper and hang it on the wall of your cube/office. (if you are in an open floor plan UML is useless because you don't have a wall to hang it on).
Re: All You Need to Know About UML Diagrams
#15My favorite flavor, plantuml, available with a cheesy (but very convenient) cli wrapper via npm- https://www.npmjs.com/package/node-plantuml The --unicode mode is particularly delightful
+1 for plantuml. You can make very useful sequence diagrams with it, in ascii no less.
Re: All You Need to Know About UML Diagrams
#16My favorite flavor, plantuml, available with a cheesy (but very convenient) cli wrapper via npm- https://www.npmjs.com/package/node-plantuml The --unicode mode is particularly delightful
+1 for plantuml. You can make very useful sequence diagrams with it, in ascii no less.
It would be remiss at this point not to recommend websequencediagrams[0].. been using it for years (and convinced multiple workplaces to shell out for the self hosted version..). It's great :)
Re: All You Need to Know About UML Diagrams
#17Missing a warning: You can get lost in here and start to programm in uml- which will result in alot of generated template code, in need to be fleshed out-
or a attempt to integrate coding snippets into your uml editor of choice and the realization that the most accurate representation of systems- is actually sourcecode.
The concept is never the full realization, and shouldnt become it.
Re: All You Need to Know About UML Diagrams
#18aha, you almost got me there. keep your distance, uml. we shall not intermingle ever again...
Re: All You Need to Know About UML Diagrams
#19UML Diagrams are actually quite useful, sometimes you just need a structured way to reason about software.
There are two types of useful UML: The first is what I call whiteboard UML - it looks like any UML course except you draw it on a whiteboard, snap a picture on your phone and start implementing it. A couple weeks latter you realize that the design has diverged from the whiteboard so you delete the pictures. The whiteboard was useful for those two weeks to get the discussion started. The second is maintained, preferab…
I suppose in an open office you could use your UML diagram printouts to make a cubicle. After a half a year or so, if you keep pasting them up on top of each other, you might start getting some sound-proofing effects.
Re: All You Need to Know About UML Diagrams
#20UML Diagrams are actually quite useful, sometimes you just need a structured way to reason about software.
There are two types of useful UML: The first is what I call whiteboard UML - it looks like any UML course except you draw it on a whiteboard, snap a picture on your phone and start implementing it. A couple weeks latter you realize that the design has diverged from the whiteboard so you delete the pictures. The whiteboard was useful for those two weeks to get the discussion started. The second is maintained, preferab…
When UML was more popular at the height of the OO(AD) frenzy, there was a tool from Peter Coad's company called TogetherJ. IIRC it could do round-tripping between UML and Java code. I think I tried the tool out but not that feature. TogetherSoft was later acquired by Borland, as I remember.