View Review Details
| Book: | UML 2.0 in a Nutshell | |
| Subject: | Complete coverage about UML 2.0 syntax, and something more | |
| Date: | 2005-07-13 01:59:02 | |
| From: | Anonymous Reader | |
|
Rating:
 
You know, the UML 2.0 is composed bye four parts (four specifications): the Diagram Interchange Specification, the Infrastructure, the Superstructure and the Object Constrain Language. This book is a quite complete reference of the UML 2.0 Superstructure. The Superstructure is the one that tipically is used by a software production involved person. The book offers a smart introduction to the UML architecture, but, obviously, if you are interested to the UML Infrastructure or to the Diagram Interchange specification, you need to read the OMG specification, or other books. Yes because at the end of the book there are 8 pages about the OCL 2.0, with the basic of the OCL syntax. As a reference this book is almost complete and precise: it covers every kind of UML diagram and deeply explains the syntax. There is also a short chapter about Effective Diagramming, but you must remember that this is a reference and you must have a background about UML and or OO Design before you can get something useful from it. For example, I have other books about object oriented design (one from B. Meyer and one from Page-Jones) and they are focused on design but on UML (yes, the one from Page-Jones uses UML for diagram examples, but doesn't cover uml but some aspects) so I keep "UML 2.0 in a nutshell" on my desk in order to verify how to put down my diagrams using diagramming tools (such as Together Architect), even if they are based on the 1.4 UML specification. In this case the book is very useful but you cannot use it if you are trying to understand if your association is an Aggregation or a Composition, or if you are effectively explaining a concept with a use case diagram. It's obvious, but you need to keep in mind that this book stays at design books as a "Java 1.4 reference" book stays at a "Programming in java" book: surely you need both and probably you won't read UML specification from OMG as you probably won't read Java 1.5 specification from Sun. By the way, if you have a basic OOD background the reference could remember you, for example, what the term composition means, so you can immediately decide when to use it. Finally I think the book has a very good coverage about dynamic diagrams and about statechart and class diagrams. |
||
