ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Google+ ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1918 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
The Unified Modelling Language Reference Manual
Rumbaugh, Jacobson&Booch
0 201 30998 X
Francis Glassborow
modelling languages
Appeared in:
The first part of this book gives you a very brief overview. It includes the section on history that so many authors seem to consider an essential part of any technical book. It also includes a short chapter on the nature and purpose of models. Again, not something that I find particularly useful for the intended readership, but such sections seem common.

The second part of the book leads you through the UML concepts. It starts with a walkthrough before devoting chapters to various views (static, use case, state machine, activity, interaction, physical, and model management) before concluding with chapters on extension mechanisms and the UML environment. In a way this is one of the more valuable aspects of this book. Professional software developers should be familiar with the material in this section.

Part 3 starts with a chapter of 386 pages that is an encyclopaedia of terms. I am not sure about calling this a chapter. It is not something to be read, but a reference section. However, it is informative and spending time browsing it will enhance your understanding.

In general this is the book for you after you have taken a course (either formally, or by means of self study) on UML basics. I have to say that much of the material is heavy going with a great deal of interdependency. For example we have:

initial state

A pseudostate that indicates the default starting place for a transition whose target is the boundary of a composite state.

See also composite state, creation, entry action, initialisation, junction state.
I sense that Ivar Jacobson has had quite a bit to do with writing the text as much of is tainted with his heavy opaque style.

If you are going to make regular use of the UML (and if you are serious about software development, it would be hard not to) you probably need access to this book.