Rating: 
Summary: A book without sparkles
Review: A good book has a lot of sparkles, which represents the author's deep understanding on a concept and his unique way to depict it. But I didn't see many sparkles in this book.A good book introducing a car should say: "A car has four wheels so that it can run on the road. To guide the direction of the wheels, we have a steering wheel. To provide power to roll the wheels, we have the engine. To connect the engine with the wheels, we have transmission system". The way this book uses is: "A car has wheels. It has steering wheels. It has an engine. It has transmission. It has water tank. It has seats. It has doors. ....".
Rating: 
Summary: Nice introduction to rational rose (if you know UML)
Review: A very nice short introduction to the Rational Rose tool, pleasant to read, good to jump start using Rose. It helps if you already have some prior UML knowledge, because the book is more focusing on using the Rose in RUP, not UML. If you just want to quickly learn UML, you may want to consider UML Distilled by Martin Fowler . Lacking of introduction to foreward/reverse engineering in Java/J2EE is a small pitfall, otherwise it deserves 5 stars.
Rating: 
Summary: Good start for konwing UML using ROSE
Review: Author introduces a series UML tools thru a simple example. It helps the use who knows a little UML and give more knowledge on how to use ROSE to build application process. It's easy to read and good OOA, OOD developer.
Rating: 
Summary: useless
Review: complete waste of money. It's more of a Rational Rose for dummies book than anything else. Dont waste your money
Rating:
Summary: A light introduction to Rational Rose
Review: I agree with other reviewers that this is more of a book about using Rational Rose than UML itself. Problem is, Rational Rose itself is not at all difficult - it's the UML modeling that is hard! It is readable, well-written, and covers all the basics. In a few places it does offer some very insightful explanations of UML concepts (like how one should think of a control class, for instance). On the other hand a lot of space in the book is wasted in pedantic walkthroughs like, "to create a use case, click on such-and-such, then choose so-and-so from the file menu, then drag it here...") The level of detail for examples is about the same as in Rational's Rose 2000 tutorial from their web site. Serious developers will hunger for more thorough examples and discussions; while I do not know of a good Rational Rose book, I recommend O'Reilly's "UML in a Nutshell" for a more comprehensive, interesting treatment of UML. This book is appropriate for those who have little knowledge of Rose or UML. Serious developers will eventually need another book.
Rating:
Summary: A Must to First Time Rose Users
Review: I am glad that I had this book when I first started to use Rose. It is well structured and organized. It tells you what you need to do exactly, how to do it step by step. More important, it tells you nothing more. I think this is very important because I often find books that fill with too much information that are not necessary useful to first time users. I also find it is a better manual than the tutorial comes with Rose for a beginner to Rose. Once you know more about Rose, the Rose tutorial/manual will be a better choice.
Rating:
Summary: Overpriced and almost meet the objective
Review: I am senior software engineer, I picked up this book neither to learn UML nor to design, but to learn rational rose. If you want to learn design I don't recommend this book. If you want to learn UML notation I don't recommend this book. For example it doesn't address a very important topic that is tasks communication: - Asynchronous message communication - Synchronous message communication with or without replay If you want to learn rational rose, this book gives you a start but very much overpriced (Double the real value). I thought learning the tools from a book I would learn it in detail, but I was wrong, I could've picked up a few a pages tutorial, and it would do the job, Frankly I believe the price is a robbery, you taking this a device from a person never cared a bout any book price.
Rating:
Summary: Rational Rose in a Hurry
Review: I found myself in a bind. I had Rational training scheduled three months out, but we had project deadlines that were only 4 weeks away. I knew some UML, but I had never worked with the tool before. Luckily, I found this book. It gives very detailed instructions for creating the various UML artifacts that Rose can generate. A continuing example runs throughout the book so you get to see how all the various elements can be linked together to help you organize your analysis and design. If your goal is to learn how to use Rose - and do it quickly - this book is for you.
Rating:
Summary: Rational Rose in a Hurry
Review: I found myself in a bind. I had Rational training scheduled three months out, but we had project deadlines that were only 4 weeks away. I knew some UML, but I had never worked with the tool before. Luckily, I found this book. It gives very detailed instructions for creating the various UML artifacts that Rose can generate. A continuing example runs throughout the book so you get to see how all the various elements can be linked together to help you organize your analysis and design. If your goal is to learn how to use Rose - and do it quickly - this book is for you.
Rating:
Summary: Good start for a Rose/UML beginner.
Review: I found this text easy to read and very informative. I remain unclear on some of the steps outlined in the book. For instance, why would anyone want to use external files to describe use case text? This belongs in a requirements management system like Rational Requisite Pro which just happens to link quite nicely to Rose use cases. Second, I'm not sure why the author has the use cases copied from the Use Case view to the Logical view. Anytime such replication is required, beware. Regardless, this was an excellent introduction to UML and Rose. I now need to find other texts to elaborate on proper Use case development in UML.
| 
