Use Case Driven Object Modeling with UML: A Practical Approach (Addison-Wesley Object Technology): Amazon.de: Doug Rosenberg, Kendall Scott: Englische Bücher

Amazon.com

Combining some of today's best ideas about customer-driven object-oriented design, Use Case Driven Object Modeling with UML: A Practical Approach shows you how to use Unified Modeling Language (UML) in the real world, keeping with the author's proprietary software design process.

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

Kurzbeschreibung

Applied Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example provides a practical, hands-on guide to putting use case methods to work in real-world situations. This companion workbook to Use Case Driven Object Modeling with UML bridges the gap between the theory presented in the authors' first book, and the practical issues involved in the development of an internet/e-commerce application. Uniquely conceived as a workbook, featuring an e-commerce system for an on-line bookstore as a running example, the book dissects its design in detail, demonstrates the most common design mistakes, and reveals the correct solutions. The hands-on exercises give you the opportunity to detect, identify, and correct critical errors on your own, before reviewing the solutions provided in the book. The workbook is structured around the proven ICONIX Process, a streamlined approach to UML modeling designed to avoid analysis paralysis without skipping analysis and design. It presents the four key phases of this minimalist approach to use case driven design: domain modeling; use case modeling; robustness analysis; and sequence diagramming.For each of these topics, the book provides an overview, detailed discussion, top 10 mistakes, and a set of exercises for honing object modeling and design skills. Another unique aspect of this book is the three chapters on reviews. The authors devote a chapter each to requirements review; preliminary design review; and critical design review. This focus on "designing quality in" by teaching how to review UML models fills a major gap in the published literature. The book shows you, by example, how to avoid more than 70 specific design errors as shown in the "Top 10" error lists on the inside covers and within each chapter. With the information, examples, and exercises in this book, you will develop the knowledge and skills you need to apply use case modeling more effectively to your next application. 0201432897B04302001

Alle Produktbeschreibungen

Kundenrezensionen

5 Sterne

4 Sterne

3 Sterne

2 Sterne

1 Sterne

8 Rezensionen

3.2 von 5 Sternen

Kundenrezension verfassen

Die hilfreichsten Kundenrezensionen

3 von 3 Kunden fanden die folgende Rezension hilfreich

155 Pages of Pride, Prejudice and Advertising 8. Oktober 1999

Von Ein Kunde

Format:Taschenbuch

I could not fine one piece of information in this book that was new or insightful. The author often uses a rational like "My experience has taught me this." This would mean so much more if he provided the logic behind his implied wizardry. It is also quite often the case that the book jumps around the UML and the author presents his (or is his company's) own special way of doing things. His section on grammatical analysis looks like a botched attempt to succinctly capture what Wirfs-Brock did so well in her "Designing Object-Oriented Software" (published in 1990 and still a "five star" excellent read). The "case study" used for the book is vague and will likely have the reader spending more time trying to decipher the case concept before understanding the notational concepts. The one good part of the book, which is not a new idea either but was worth brushing up on, was idea of traceability within a project lifecycle. Overall, "Applying Use Cases: a Practical Guide," by Schneider and Winters is a much better read and will get you further along in your Use Case endeavors.

Kommentar |

War diese Rezension f�r Sie hilfreich?

Nein

2 von 2 Kunden fanden die folgende Rezension hilfreich

Will the real UML please stand up? 18. Januar 2000

Von Ignatius O'Reilly

Stick with the Martin Fowler or Craig Larman books folks, this one is more confusing than helpful. It's also poorly written, with little coherence as ideas are scattered all over. A veritable stream of conciousness. Maybe because Rosenberg himself hasn't figured it all out. In fact, at the beginning of the chapter on interaction modeling, he says don't be surprised if this chapter doesn't make sense, because he was supporting this in his CASE tool for a year before he even knew what it did. Wow. So he's selling the product, but he's not even sure what it's for?

The second chapter starts talking about domain modeling. Where'd he get the "relevant" material to look through? Oh, I see, he's reviewing the user manuals, documentation, GUI and tables from the old system. That works for him, but probably he ends up building systems that look like the old ones. Build the domain model (from the old system), then prototype the system, then write use cases, then figure out your requirements (chapter 7)? Too bad for people new to UML who try to make sense of this book. Probably the idea is to steer people to the cd, which will undoubtably make everything clear.

It takes a while to figure out what this book is really about - and it's not the UML! If you read the beginning chapter, he talks about the Unified approach he developed with his colleagues. What, you think, is he leading Booch, Rumbaugh, Jacobson at Rational? Nah. He means his own "Iconix" Unified Modeling Language approach, with what he liked of himself, and those lesser guys, B, R and J.

I can really see why he gets into some heated conversations on the Rational mailing lists. The appendix, with a summary of one of these exchanges, and the top ten lists are the best part of this book.

The Keyword here is "Practical" 2. Dezember 1999

Von Todd Vierheller

"Use Case Driven Object Modeling with UML, A Practical Approach" is perhaps the best book on the market for a down-to-earth, hands-on introduction to the Unified Process. As the title suggests, it leans heavily on the methodology of Ivar Jacobson, one of the three amigos. If you are trying to figure out what to do or where to start, this will point you in the right direction.

Three things in particular I liked about the book:

1. "The Approach in a Nutshell" as well as constant reference back to it.

2. The lists of ten.

3. The chapter on "robustness analysis" showing the transition from analysis to design (always a difficult transition in any methodology). This is the best part of the book in my opinion. It was real "hands-on".

"The Approach in a Nutshell" gives a great overview of the process including milestones, and provides a framework for everything to fit into. As the reader progresses through the book, each chapter summarizes that part of "the approach in a nutshell" that the chapter fits into. If this was the only feature in the book, it would be worth the price.

If you have ever read another series with "lists of ten", these are better. The lists of ten (there are over half-a-dozen) are worth taping up on the walls. They reflect the experience of someone who has been there and done that. The lists of ten alone are worth the price of the book.

The transition from analysis to design has rather heavy focus in this book, and deservedly so. Going from analysis to design is tricky in any methodology, and "Use Case Driven Object Modeling with UML, A Practical Approach" shines in this area. The authors refer to this as "robustness analysis," and this section alone is worth the price of the book.

This won't be the only book concerning the Unified Process that you will ever buy. But it is more than likely going to be one of the most useful to you.

This is not a tutorial on the UML; purchase "UML Distilled, Second Edition" by Martin Fowler and Kendall Scott if that is what you are looking for. The title may be slightly misleading in this respect. The real focus is on the "Practical Approach" part. If you are trying to sort out HOW TO DO IT, then this is a necessary addition to your library. It won't replace your books on the UML or the Unified Process, but it will help you pull it all together into a cohesive whole so you can get a grasp on how to start and how to proceed.

In addition to being very informative and clear in direction, the book is also surprisingly interesting to read. Its clarity and brevity keep it simple. You won't get bogged down reading this one. It is very well written.