UML Distilled: A Brief Guide to the Standard Object Modeling Language (3rd Edition) (The Addison-Wesley Object Technology Series) by Martin Fowler
$33.50
|
Agile Development with ICONIX Process: People, Process, and Pragmatism by Doug Rosenberg
$38.50
|
Use Case Driven Object Modeling with UMLTheory and Practice by Doug Rosenberg
$43.99
|
Writing Effective Use Cases (The Agile Software Development Series) by Alistair Cockburn
$40.80
|
Applying Use Cases: A Practical Guide (2nd Edition) (The Addison-Wesley Object Technology Series) by Geri Schneider
$40.60
|
The book begins with the genesis of the author's ICONIX Unified Object Modeling Approach, borrowing ideas and strategies from the "three amigos" who invented UML: Grady Booch, James Rumbaugh, and Ivar Jacobson. Throughout this text, the ICONIX method is used to model a stock trading system, with all the relevant UML diagrams, beginning with class definition and use cases.
The author's approach to software relies heavily on customer requirements and use case scenarios for which he has a good deal of practical advice. He provides numerous hints for avoiding bogged-down diagrams. After preliminary design, he advocates drilling down into specifics with robustness diagrams, which trace how classes interact with one another. The most detailed design work comes next with sequence diagrams.
Subsequent chapters offer tips on project management, implementation, and testing. Throughout this lively and intelligently organized book, the author presents numerous real-world tips (and Top 10 lists) that supply wisdom to his perspective on effective software design.
Written for the reader who already knows a little UML notation, Use Case Driven Object Modeling with UML provides an appealing blueprint for the software design success. --Richard Dragan
Dr. Dobb's Electronic Review of Computer Books
Read the full review for this book.
UML's second weakness is addressed by one new bit of notation, which Rosenberg calls a "robustness diagram." While the connection between the general idea of robustness and these diagrams seems a bit tenuous to me, they appear to be a useful bridge between use cases on the one hand, and implementation-oriented diagrams on the other. Their value becomes clear during the development of the book's running example, a simple stock-trading system. I have only two criticisms of this book. The first is that Rosenberg repeatedly refers to, and discusses, both older design notations and debates about the finer points of UML--in fact, he devotes an entire appendix to the difference between "uses" and "extends," despite the fact that he clearly doesn't think the difference is significant. This material might be of interest to the cognoscenti, but is out of place in a book aimed at newcomers. --Gregory V. Wilson, Dr. Dobb's Electronic Review of Computer Books
See all Editorial Reviews
Product Details
|