I am still working my way through the book but so far I am impressed by the authors direct no nonsense views on design and test. I am a software tester and my new project uses UML which I have not worked with before. This book has given me a good overview and explains the terms and diagrams used in UML design very clearly.
Keep up the good work guys.

The Rosenbert & Stephens's Book is a great example of doing by practice, but highly supported by foundations about what is important in UML.
The book offers a great discussion not only how use UML effectively, but how can you go through practice and coding. That's essencial if you want coding in a right way, but explore the UML notation.
The approach with ICONIX was fantastic. You develop a e-Commerce system completely using UML, Iconix process and coding with JAVA. I coudn't found books that offer this path.
Fantastic. Excelent aquisition.

Since 2001 I had a lot of courses on UML modelling at the university and in inhouse company workshops. But none of them gave me the real power to write use cases so that I can easilly extract an object model from it. I always had problems to bridge the use cases to sequence diagrams and class models.

This book gave me the clues (with red and bold highlighted) such
"You can't drive object-oriented designs from use-cases unless you tie your use cases to objects."

Now I have to say, I write use cases more confidetially, knowing that they build a real basis for futher object modelling. 5 stars!!

This book was extremely helpful because it takes the reader from Use Cases to code development using a real-life "sample" system (an internet book store) to describe the steps. The ICONIX Process is used in this book and the goal of the book is to get from Analysis to Code using a minimal, yet sufficient core subset of UML. Each step is broken down into detail and examples of how to do each step are provided and explained. Built into the "sample" project are mistakes (ones that are commonly made in real life) and the book shows those mistakes as well as the corrected versions. In addition, the book discusses the Enterprise Architect (EA) tool, which our company is evaluating, making the examples provided even more pertinent. The only thing that would have made this book more useful would have been appendices or detailed examples of using the EA tool with the "sample" project. It would be great if one could obtain the sample project in a *.EAP file where folks that have the EA tool could load the sample project to understand how the project was actually laid out in the EA tool. This book is very well-written and, as a bonus, has some decent humor throughout keeping the reader's interest. If you are using EA and Use Case Driven development, this is an excellent book for you.

This book does everything it promises and more. While reading this book you will learn a design methodology that will help you in every project you work on. What you won't learn is a framework that does all the work for you. You also won't learn to rely on someone else's code. Instead you will learn how to really think about your project from the initial design to the final solution. You will learn how to properly document the requirements and the user interaction with the system. You will learn how to be a Software "Developer" not just a Software "Programmer". Some will say there is no difference, but others that have read this book will understand the work and thought process that goes into real development of a software solution.

This book puts the whole business analysis process into perspective with a practical guide for how to go from step A to step Z. I am new to the ICONIX process and am very impressed with how ICONIX eliminates the burden of learning all the steps of UML and instead teaches in detail just the essential components of UML, so you can quickly develop the use cases, requirements, test cases, and coding specifications. The book is written with the business analyst in mind by highlighting the theory, but concentrating and demonstrating the practices with straight forward guidelines and examples. The Enterprise Architect modeling tool, which we are learning how to use, is referenced occasionally and is shown to be a very useful tool for the business analyst. This is one of the finest IT books I have ever purchased.

If your domain model consists of webpages and form validation and if page navigation is your big problem, this book is for you. (In modern development however, we use frameworks to solve those problems.) This book will be useful for those people on your project who think that Struts2, Spring web flow and Velocity are all inadequate for page navigation; you'll want to give them some stone tools so they can reinvent the wheel. The examples in this book so remind me of the concerns we had in the 90s with the JSP development.

The book combines explaining how to drive use cases to code and lots of examples. In fact one of the best parts is the 'bad example' followed by the corrected version - lots of those.

Iconix is pretty easy to use ONCE YOU UNDERSTAND IT. This book goes a long way toward understanding how to write good use cases that CAN be used for software development rather than just documentation.

I've read many, many use case books and this one boils the details down to something that is pragmatic. I've used the Iconix technique in both industry and the university and it works in both areas.

Good book? Yes. Buy it? Yes!

Easily one of the best methodology books I've read in quite some time. The book is very well written and flows very well. The structure walks you through the entire ICONIX process from beginning to end and explains in-detail the steps involved and most importantly "why". I also liked how the authors referenced other highly ranked OO books to reinforce how to allocate behavior to your objects during sequence diagraming.

I never heard of ICONIX until recently and I was very happy I got this book. The process is logical, stream-lined, and easy to pickup. The chapter on sequence diagrams just clicked for me and brought everything together.

I highly recommend this book!

The book has a directness and simplicity that mirrors the development approach they describe; and, it covers more than "object modeling" - this is a complete concept-to-code approach which strikes a very nice balance. Excellent!

The introduction to the book starts with an interesting phrase "The difference between "theory" and "practice" is that in theory there is no difference between theory and practice, but in practice there is." The authors like to apply this statement to UML modeling, and continue later saying, in theory, everything in UML is useful, but in practice, a whole lot of people and projects need to know how to drive an OO software design from use cases.

Use Case Driven Object Modeling with UML-Theory and Practice shows how to take an object-oriented software design from use case all the way through coding and testing, based on the minimalist, UML-based ICONIX process. The authors focus on one simple question, "how do you get from use cases to code?". The authors are real experts on the ICONIX process. This book is for Beginners as well as for advanced programmers. Beginners will learn a powerful methodology, Use-Case Driven Object Modeling. On the other hand, advance developers can apply Use Case to their preferred methodology.

The authors break down the design of an Internet bookstore, which involves showing many common mistakes, and then showing the relevant pieces of the model with their mistakes corrected. What really makes this book unique is the fact that you, the reader, get to correct the mistakes.
Chapter highlights

Highlights of this book include:

1. Each chapter starts with the theory, and then explores said theory using the Internet Bookstore project.
2. Each chapter has a "Top 10" list of guidelines, and the first half of each chapter is structured around its top 10 list.
3. This book also contains practical exercises of various types like, Workbook exercises, Student exercises and Inline exercises within the chapters.

Personally, I believe this is a very good book, very informative and well written. Before reading this book, I hadn't heard of ICONIX process, and this book did give me a good insight about the same. If you are sold on ICONIX and have been using it, the Top 10 list of guidelines, and the exercises at the end of each chapter in itself is worth the price of the book.

The introduction to the book starts with an interesting phrase "The difference between "theory" and "practice" is that in theory there is no difference between theory and practice, but in practice there is." The authors like to apply this statement to UML modeling, and continue later saying, in theory, everything in UML is useful, but in practice, a whole lot of people and projects need to know how to drive an OO software design from use cases.

Use Case Driven Object Modeling with UML-Theory and Practice shows how to take an object-oriented software design from use case all the way through coding and testing, based on the minimalist, UML-based ICONIX process. The authors focus on one simple question, "how do you get from use cases to code?". The authors are real experts on the ICONIX process. This book is for Beginners as well as for advanced programmers. Beginners will learn a powerful methodology, Use-Case Driven Object Modeling. On the other hand, advance developers can apply Use Case to their preferred methodology.

The authors break down the design of an Internet bookstore, which involves showing many common mistakes, and then showing the relevant pieces of the model with their mistakes corrected. What really makes this book unique is the fact that you, the reader, get to correct the mistakes.
Chapter highlights

Highlights of this book include:

1. Each chapter starts with the theory, and then explores said theory using the Internet Bookstore project.
2. Each chapter has a "Top 10" list of guidelines, and the first half of each chapter is structured around its top 10 list.
3. This book also contains practical exercises of various types like, Workbook exercises, Student exercises and Inline exercises within the chapters.

Personally, I believe this is a very good book, very informative and well written. Before reading this book, I hadn't heard of ICONIX process, and this book did give me a good insight about the same. If you are sold on ICONIX and have been using it, the Top 10 list of guidelines, and the exercises at the end of each chapter in itself is worth the price of the book.

I always liked Doug's ICONIX process for getting requirements through to initial design. It is better than any competing methodology, period. This time, however, he and Matt actually provide a concrete example of what it takes to get something built for real from that design. Now my developer friends will actually listen. Good stuff.

I always liked Doug's ICONIX process for getting requirements through to initial design. It is better than any competing methodology, period. This time, however, he and Matt actually provide a concrete example of what it takes to get something built for real from that design. Now my developer friends will actually listen. Good stuff.

*** New Concepts in old methodology ***

This book is well written by someone who actually has real-experience. The author is an expert on this subject. He wrote this book and made it very practical based on his real experience.

Use case is powerful. UML is undeniable. Object-oriented-system modeling needs both Use Case and UML.

Nowadays some invented methodologies are available such as eXtreme Programming, Agile, Model-Driven Development (MDD), Domain-Driven Design (DDD), Test-Driven Development (TDD), and so on. This book can support those methodologies because Use Case and UML are powerful on high-level design.

This book is for all levels: Beginning to Advance. For beginners, you will learn a powerful methodology, Use-Case Driven Object Modeling. For advance developers who are using Agile, MDD, or so on, you can apply Use Case to your methodology. It is very powerful. I tried put Use Case into XP. Outcomes are very extremely wonderful.

This book is not a necessary and must-buy book. But if you can afford, you should get one. It is worthy.