What do you think?
Rate this book
Uml and the Unified Process and Uml: Practical Object-Oriented Analysis and Design
An accessible, practical guide to essentials of both UML and the Unified Process, aimed at the OO designer or analyst. Gives the reader a quick, focused tour through the Object Oriented Analysis and Design process. Softcover.
416 pages, Paperback
First published January 1, 2001
20 people are currently reading
304 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 7 of 7 reviews
February 18, 2015
A practical overview of UML for both for beginners and for advanced users too.
----quotes----
A common error of novice UML modelers is to delete things from diagrams but leave them in the model.
In fact, a common modeling error made by novices might be called “death by diagrams”: the model is overdiagrammed but underspecified.
You can capture the strategic aspects of a system in a “4+1 view” of architecture: logical view, process view, implementation view, deployment view, and use case view.
According to [Standish 1] , incomplete requirements and lack of user involvement were the two top reasons cited for project failure.
For any requirements document, in whatever form, the key questions are “how useful is it to me?” and “does it help me to understand what the system should do or not?”
Unfortunately, some projects are scared of things that are short and simple and are enamored of large quantities of documentation. Grady Booch calls this tendency “paper envy”.
----quotes----
A common error of novice UML modelers is to delete things from diagrams but leave them in the model.
In fact, a common modeling error made by novices might be called “death by diagrams”: the model is overdiagrammed but underspecified.
You can capture the strategic aspects of a system in a “4+1 view” of architecture: logical view, process view, implementation view, deployment view, and use case view.
According to [Standish 1] , incomplete requirements and lack of user involvement were the two top reasons cited for project failure.
For any requirements document, in whatever form, the key questions are “how useful is it to me?” and “does it help me to understand what the system should do or not?”
Unfortunately, some projects are scared of things that are short and simple and are enamored of large quantities of documentation. Grady Booch calls this tendency “paper envy”.
January 21, 2024
good and complete immersion in the UML language. Also a good insight into history.
February 17, 2016
Very thorough and clear explanation of UML2, delivered in a sensible organisation and developing from analysis view through design into implementation.
Along the way, it covers the whole gamut of UML diagramming, including all the more obscure arcana - if you ever need to diagram delegates providing interfaces on behalf of components, or parameter sets of IO pins, or interrupting edges triggered by signals recived in an interruptible activity region, this is the book for you.
It's not going to teach OOAD - it should be thought of more of a manual on how to document your OO analysis & design in UML2, rather than teaching how to do the analysis & design, and in fairness, there's not an enormous amound on the Unified Process either.
Having said that, it's excellent on UML: highly recommended.
Along the way, it covers the whole gamut of UML diagramming, including all the more obscure arcana - if you ever need to diagram delegates providing interfaces on behalf of components, or parameter sets of IO pins, or interrupting edges triggered by signals recived in an interruptible activity region, this is the book for you.
It's not going to teach OOAD - it should be thought of more of a manual on how to document your OO analysis & design in UML2, rather than teaching how to do the analysis & design, and in fairness, there's not an enormous amound on the Unified Process either.
Having said that, it's excellent on UML: highly recommended.
January 19, 2008
THE description of UML, but whether UML is useful or not is an entirely different matter.
May 16, 2010
Very good book about UML, introducing all diagrams (and their creating) in both theoretical and practical way.
August 22, 2012
A good book to start. The book flow of ideas in relatively good, not perfect though.
Displaying 1 - 7 of 7 reviews