UML 2.0 - Pocket Reference - If you really are going to carry it around


I have to admit that I am lured into the pocket size form factor used by O'Reilly and others. The cute baby animals on the cover, like the gorilla on the front of the "UML 2.0 - Pocket Reference" is just fun. I also have "The Elements of UML Style" in the same easy to consume and not really pocket sized size. Parts of this review also apply to both pocket books, but the majority is about the UML 2.0 - Pocket Reference.

If you do actually end up bringing this "pocket" reference around with you then great, but consider when will you actually use it. While you are walking around the park thinking about UML and all of its confusing details? This book only covers syntax and usage, not really semantics which is where most people struggle anyhow, as the semantics and detailed syntax consume over 1000 pages. You could bring it to meetings and wow people with perfect diagrams. Again, this book might help with that, but how often are you drawing a diagram on the white board and everyone is confused because you lines are not specific enough, or the shape is just not right. This does not happen because the people in the meeting have the context of the conversation and thus do not need perfection, the drawing is just a tool to move the conversation forward not get hung up on syntax, semantic maybe, but this book won't help with that beyond the bare surface.

Additionally this spartan "pocket" reference decided to include OCL, which is 5 pages long. Distilling a language, context, and usage in 5 tiny pocket pages really was just a waste of space. There are 100+ page books on OCL to do it justice, if the book is even current or matches your implementation of UML.

It seems far more rational to make your own pocket guide using a print out from websites with examples or the front and back flaps of UML Distilled, by Martin Fowler. This follows the 80/20 approach in that you get 80% of the value with 20% of the cost and complexity. Pick the diagrams or elements you typically use, such as classes and components or sequence diagrams and limit your pocket guide to those. Or just bring your laptop and have some favorite UML sites bookmarked.

Finally if they are really trying to make a reference, create tabs for the sections at least, having to look up the page in the front or term in the back is not very efficient if you use the book frequently. And if you are like me and the pocket references end up on a bookshelf they don't even fit in, the black sheep of your library.

Comments

Post a Comment

Popular posts from this blog

Configuring Javascript SyntaxHighligher 3+ in a Blogger site

Image
In this post I tactically outline a quality way to configure the Javascript based SyntaxHighlighter library into a Blogger site. The configuration below makes use of the recent autoloader available in version 3 and greater of the SyntaxHighlighter.  The configuration code below is in fact using the SyntaxHighlighter which incidentally allows you to copy the code examples quickly.  Check out this very popular library here . Configuration: 1.  Login into blogger.com and click/select the site you want to configure ( http://www.blogger.com/home ) to support syntax highlighting.  Generally if there are multiple sites you would like to enable each site's template will need to be configured individually. 2.  Click the Template link from the sidebar of the Blogger Site main page shown below. 3.  Save the template, if you choose, by clicking on Backup/Restore in the upper righthand corner and following the instructions.  Better to be safe rather than sorry if you are not famil
Read more

Common Misunderstanding of UML

Over at Stack Overflow a question was posted " Is UML practical? ". The question itself is fine, but several of the answers were so narrowly focused. I believe that the everyday developer only sees UML as only a common set of shapes drawing a picture. Granted it has a common set of shapes for notation, but UML is first and foremost about modeling. (Big surprise coming from a Modeling Website). Where did this dis-information come from? In my experience the UML for diagrams message comes from schools/universities and popular UML books. Schools will often only teach UML as a way to diagram the solution you and your team of group participants are going to code up. Well of course it seems a little redundant in that contrived learning environment. UML's concepts are to large to teach in the same class as project management 101 or multi-developer projects 101. Most people just don't go any further with it and thus the collective knowledge is that UML is for making d
Read more

Reference Cards, Cheat Sheets, Posters, whatever they are called.

Tonight I tried to find quick reference sheets for both UML and BPMN, free of course.  There are quite a fewer different terms for them be it poster, reference cards, cheat sheets, quick guides etc.  However, once I got into several sites by searching for "Reference Cards" I found the other names for these small printable guides to various technologies. Oh yes, and much more managable or likely to be used than " pocket references " which don't fit in your pocket. List of quality sites quick guides: refcardz.dzone.com itPoster.net (singular) cheat-sheets.org scribd.com/ (kind of) I did not find a suitable quality UML guide ( Stackoverflow has a list ), but the BPMN poster  at itPoster.net though outdated at time of this post was still really well done. There are several red herring links which get referenced a lot, but are not that good, ex: ( How are you to carry this around? ) Any other good sites that have a listing of printable reference guides?
Read more