It is easy to say that it is light, or it is only introductory. Among our reviewers community we certainly have experts of all kind. But I think the purpose of the book is exactly that, to offer a clear and effective starting point for using UML notation and Rational Rose tool for software architecture design. If you are already a guru in software design and UML of course you don't need this one. It helped to me and it can help others, I am convinced on that. I recommend.

complete waste of money. It's more of a Rational Rose for dummies book than anything else. Dont waste your money

Together with the Rose tutorial comes with software, you are going to start using Rose fast. Just wish the book comes with the example model in a CD or somehow users can get from internet. That will save lots of trouble and I can look into details not mentioned in the book and do some thinking "why she modeled it this way?"....and why she has this object/class, isn't it already in...?

Together with the Rose tutorial comes with software, you are going to start using Rose fast. Just wish the book comes with the example model in a CD or somehow users can get from internet. That will save lots of trouble and I can look into details not mentioned in the book and do some thinking "why she modeled it this way?"....and why she has this object/class, isn't it already in...?

Rational software ships this book free when you buy Rational Rose. Even then it is overpriced. If you don't know UML, this book may lead you astray. The author tells you how to draw things with Rational Rose, but not why you might want to draw them. Without a doubt, the worst UML book I've ever encountered. I feel sorry for the author; it seems that she (?) was probably tasked by Rational to write a user's manual for Rational rose, and someone at Rational thought they could make some more money by publishing it as a separate book. Unfortunately, it's insufficiently thorough to be a worthwhile user's manual.

This book gives a worked example to using Rational Rose. It covers basics of UML, but not in detail. Overall, you should be able to appreciate the advantages of Visual modelling once you read this book. I would say this book is ideal for a person who has just learnt UML and OOAD concepts and is on the lookout for full fledged example of using those concepts. For just that, the book is over priced.

This book, just like the title says, is just about visual modelling with rational rose and doesn't explain the details whether about UML or OODA. Just about Visual Modelling.
I recommend this book for peoples who are looking for tutorial in Rational Rose, this will be the right one. But I don't recommend this book anybody, who is looking for UML or OODA books, because it is not the right book for that.
For a tutorial is this book probably too expensive ...

This book is not worth the asking price. Quantrani has followed a style of writing where "less is more". However, there is so little content and the examples are so simplistic that as I was reading the book, I couldn't help but think that I've been had yet again on another poorly executed "training guide". I think you would be far better off buying another book or simply reading the tutorial material for Rose on Rational's site.

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.

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. ....".

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.

You pay [too much] for a How-to Book. No explantions/examples about object-oriented programming (as UML defines it). The idea is good: you start with an example and refine it on the way. But consuming half a page to show me the actions for a specific task underestimates my I.Q. level. If you want a book that explains briefly the menus of Rational Rose it's a right choise. If you want a book that explains how to develop programs using UML, search elsewhere.

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.

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.

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.

This is a very straightforward cookbook of Ratinal Rose. I use it whenever I need quick reference in developing my software.

Terry has done a pretty well enough job of translating the technical elements into fairly direct English and should not be hard for beginners to grasp the concept of UML on Rational Rose.

No wonder she's a Rose evangelist!

So you can distinguish a cardinal from a chicken? Can you fly?

Terry describes the basic diagrams and syntax of UML with a very simple Course Enrolment example that serves to show what things look like. Not much more here.

This book is extremely well-written and straight to the point. It's a nice and simple introduction to the world of UML using Rational Rose. The case study (ESU course registration) used in the book is simple enough for all the readers to understand. I finished reading the book within 3 days and started using Rose on my EJB project painlessly. I highly recommend this book for all new UML/Rose users. Thanks the author for "gave birth to Visual Modeling with Rational Rose and UML". Great "child"!

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.

I've been working on word templates for my project based on the Rational Unified Process (RUP) web pages for my project. We will use these templates to create concept models, design models, code reviews, and inspections.

While the RUP web page provides a great overview of a development process in the large, it lacks much of the details needed when the rubber meets the road. Exact templates for design documents and detailed step-by-step instructions are not provided. Such detail is not the purpose of the RUP pages. This is the primary reason that I am melding RUP and other standards to produce the templates listed above.

I have found that "Visual Modeling with Rational Rose 2000 and UML" by Terry Quatrani is an excellent guide for moving from the inception phase through the elaboration phase and into the implementation phase. The book is a step by step description of the details involved in using Rose 2000 (or 98i) to create use-cases, tie them into design, and move to implementation.

I highly recommend using the Quantrani book as the guide to fill in the details not present in the RUP pages. This edition, while somewhat focused on a single example, is significantly better than the previous edition.

This is quite nicely structured and descriptive, but it offered nothing new, at least to me. You'll better go with the (original) UML user manual and the information offered by Rational on Rose. It further touches only a few aspects of Rose.

Terry's book is topshelf. She applies a practical hands-on guide to using Rose 2000 to a case study. The book is well written, informative, and an enjoyable read.