Rating: 
Summary: Answers the question: How do you get from use cases to code.
Review: How do you get from use cases to code? More specifically, how do you get from use cases to code using a combination of OOAD techniques from Jacobson, Booch, and Rumbaugh? I've been answering this question for people in a variety of ways, including onsite training workshops, multimedia CDROM tutorials, magazine articles, and EMAIL postings to OTUG, the Object Technology User's Group, since about 1992. Yep, that's about 3 years BEFORE the advent of UML. About a year and a half ago, I met Kendall Scott, who was looking for his next project after winning every award in sight with UML Distilled, and we decided it was time to answer the question in book form. As the book has taken shape, I've been "debugging" it during every UML training workshop that I've taught over the last 6 months, and I think we've pretty much got "the truth, the whole truth, and nothing but the truth" in it now. It's clear, it's concise, and it's easy to read and follow. In spots, it's even funny. The book focuses on the practical aspects of driving a project from use cases to code in a traceable manner, and omits any and all theory that is extraneous to that goal. It comes complete with Top 10 lists at the back of every chapter, and "Analysis Paralysis Alerts" to warn you when you're about to fall into a modeling trap that your schedule probably doesn't allow for. If you're having trouble weeding through the myriad of details that comprise the UML, and you don't want to learn three different ways to express every modeling concept, but just want somebody to tell you what you really need to know in the simplest and most straightforward manner, we think you'll like this book. Doug Rosenberg
Rating: 
Summary: I like this book, better UML.
Review: I am sturdying UML. This book is very good
Rating: 
Summary: 155 Pages of Pride, Prejudice and Advertising
Review: 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.
Rating: 
Summary: The title is misleading
Review: I expected this book to delve more into UML and use cases than it does. It really is a book about the ICONIX methodology. It only deals with UML and use cases at a high level. The robustness analysis is interesting and may help people who have trouble linking the user interface to the model. If you are looking for a book on the ICONIX methodology then this book is for you. If you are looking for a book on UML or use cases then this is not the right book.
Rating:
Summary: The title is misleading
Review: I expected this book to delve more into UML and use cases than it does. It really is a book about the ICONIX methodology. It only deals with UML and use cases at a high level. The robustness analysis is interesting and may help people who have trouble linking the user interface to the model. If you are looking for a book on the ICONIX methodology then this book is for you. If you are looking for a book on UML or use cases then this is not the right book.
Rating: 
Summary: This book helped me get started with design using UML
Review: I found this book very good. This book will help you write your "use cases" and make sure you don't forget important details in your design. My review for this book is simple: If you are stuck trying to start your design. If you have problems figuring out the how and what in terms of designing your systems. You must read this book. I'm sure the writing of use cases for my next project will be much easier.
Rating:
Summary: Ditto this NOT being Unified Process
Review: I had to read this book for a class I took. Here is my interpretation of the purpose of this book: "I think the world should have used my ICONIX process! This UML stuff is inferior. I hate UML, but I will use it to sell my book." Fortunately, the class also used Martin Fowler's great UML Distilled book. If you want to know about UML, get that one instead!
Rating:
Summary: Ditto this NOT being Unified Process
Review: I had to read this book for a class I took. Here is my interpretation of the purpose of this book: "I think the world should have used my ICONIX process! This UML stuff is inferior. I hate UML, but I will use it to sell my book." Fortunately, the class also used Martin Fowler's great UML Distilled book. If you want to know about UML, get that one instead!
Rating:
Summary: Don't pay for advertising
Review: If you are interested in the approach see the web-site instead. Why buy this guys company advertisement?
Rating:
Summary: Not Unified Process
Review: If you are looking for a book on the Unified Process (as I was), then this book is not for you. This book covers the author's Iconix process. Considering the book's title I would have expected it to examine use cases and UML more than it does.
I was really intereted in the Unified Process. But, the Iconix methodology is a good one, and were it to be more prevalent in the industry I would take a harder look at it.
| 
