|Other Retailer||Price Checked Time||Their Price in NZD||Our Price|
|Amazon UK||6 days ago||81.1||$68.43||You save $12.67|
|Amazon US||5 days ago||69.67||$68.43||You save $1.24|
Preface. Why bother with the UML? Structure of the book. Changes for the Third Edition. Acknowledgements. 1. Introduction. What Is the UML? Ways of Using the UML. How We Got to the UML. Notations and Meta-Models. UML Diagrams. What is Legal UML? The Meaning of UML. UML is not enough. Where to Start with the UML. Looking for More Information. 2. Development Process. Iterative and Waterfall Processes. Predictive and Adaptive Planning. Agile Processes. Rational Unified Process. Fitting a Process to a Project. Fitting the UML into a process. Understanding Legacy Code. Choosing a Development Process. Where to Find Out More. 3. Class Diagrams: The Essentials. Properties. Attributes. Associations. Multiplicity. Programming Interpretation of Properties. Bi-directional Associations. Operations. Generalization. Notes and Comments. Dependency. Constraint Rules. When to Use Class Diagrams. Where to Find Out More. 4. Sequence Diagrams. Creating and deleting participants. Loops, conditionals and the like. Synchronous and Asynchronous Calls. When to use Sequence Diagrams. 5. Class Diagrams: Advanced Concepts. Keywords. Responsibilities. Static Operations and Attributes. Aggregation and Composition. Derived Properties. Interfaces and Abstract Classes. Read Only and Frozen. Reference Objects and Value Objects. Qualified Associations. Classification and Generalization. Multiple and Dynamic Classification. Association Class. Template (Parameterized) Class. Enumerations. Active Class. Visibility. Messages. 6. Object Diagrams. When to use Object Diagrams. 7. Package Diagrams. Packages and Dependencies. Package Aspects. Implementing Packages. Where to Find Out More. When to Use Package Diagrams. 8. Deployment Diagrams. When to use deployment diagrams. 9. Use Cases. Content of a Use Case. Use Case Diagrams. Levels of Use Cases. Use cases and features (or stories). When to Use Use Cases. Where to Find Out More. 10. State Machine Diagrams. Internal Activities. Activity States. Superstates. Concurrent States. Implementing State Diagrams. When to Use State Diagrams. Where to Find Out More. 11. Activity Diagrams. Decomposing an action. Partitions. Signals. Tokens. Flows and Edges. Pins and Transformations. Expansion Regions. Flow Final. Join Specifications. And there's more. When to Use Activity Diagrams. Where to Find Out More. 12. Communication Diagrams. When to use Communication Diagrams. 13. Composite Structures. When to Use Composite Structures. 14. Component Diagrams. When to use Component Diagrams. 15. Collaborations. When to Use Collaborations. 16. Interaction Overview Diagrams. When to use Interaction Overview Diagrams. 17. Timing Diagrams. When to use Timing Diagrams. Appendix A Changes between UML Versions. Revisions to the UML. Changes in UML Distilled. Changes from UML 1.0 to 1.1. Type and Implementation Class. Complete and Incomplete Discriminator Constraints. Composition. Immutability and Frozen. Returns on Sequence Diagrams. Use of the Term "Role". Changes from UML 1.2 (and 1.1) to 1.3 (and 1.5). Use Cases. Activity Diagrams. Changes from UML 1.3 to 1.4. Changes from UML 1.4. to 1.5. From UML 1.x to UML 2.0. Class Diagrams (Basic). Interaction Diagrams. Class Diagrams (Advanced). State Diagrams. Activity Diagrams. Bibliography. Index.
Pressured with tight deadlines, application developers do not have the luxury of keeping completely up-to-date with all of the latest innovations in software engineering. Once in a great while, a tremendous resource comes along that helps these professionals become more efficient. The first two editions of UML Distilled have been perennial best-sellers because of their concise, yet thorough, nature. This eagerly-anticipated third edition allows you to get acquainted with some of the best thinking about efficient object-oriented software design using the latest version of the industry-standard for modeling software: UML 2.0. The author has retained the book's convenient format that has made it an essential resource for anyone who designs software for a living. The book describes all the major UML 2.0 diagram types, what they are intended to do, and the basic notation involved in creating and deciphering them. A true treasure for the software engineering community.
Martin Fowler is an independent consultant who has applied objects to pressing business problems for more than a decade. He has consulted on systems in fields such as health care, financial trading, and corporate finance. His clients include Chrysler, Citibank, UK National Health Service, Andersen Consulting, and Netscape Communications. In addition, Fowler is a regular speaker on objects, the Unified Modeling Language, and patterns.