Description UML 2 and the Unified Process contains a wealth of practical, powerful, and usefultechniques that you can apply immediately. As you progress throughthe text, you will learn OO analysis and design techniques, UMLsyntax and semantics, and the relevant aspects of the UP. The bookprovides you with an accurate and succinct summary of both UML andUP from the point of view of the OO analyst and designer. For Sale in Indiansubcontinent only Fully updated for UML 2.0, highlights the latest features of the IBM/Rational Unified Process Emphasizes tips and tricks that help the reader become an expert analyst and designer Includes a new section on the OMG's MDA initiative, coverage of RUP stereotypes, and a new appendix relating the book to UML certification I. Introducing UML and UP What is UML? What is the Unified Process? II. Requirements The requirements workflow. Use case modeling. Advanced use case modeling. III. Analysis The analysis workflow. Objects and classes. Finding analysis classes. Relationships. Inheritance and polymorphism. Analysis packages. Use case realization. Advanced use case realization. Activity diagrams. Advanced activity diagrams. IV. Design The design workflow. Design classes. Refining analysis relationships. Interfaces and components. Use case realization-design. State machines. Advanced state machines. V. Implementation The implementation workflow. Deployment. VI. Supplementary Material Introduction to OCL. Jim Arlow has been programming and designing object-orientedsoftware systems since 1990. He has created object models for bluechip companies such as British Airways and M&G. He is arespected OO consultant in Europe and has written and deliveredmany training courses on object technology and Java. Jim is aregular speaker at conferences such as Object World, and has beenan invited speaker at University College London, City University,and the British Computer Society. Ila Neustadt has worked in IT for British Airways for mo
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”.
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.