Rating: 
Summary: Decent book on how to use Rotaional Rose and UML
Review: I purchase this book to learn how to use Roational Rose 2002, and to get a better understanding of UML. After reading this book, I have achieved the goal. Few suggestions to the authors: 1) At the end of the book, if there were a COMPLETE sample, illusating the whole process, from Business Use Case Diagrams, to Deployement diagrams, then this book would be more complete and useful. 2) The book should come with a trail version of Rational Rose 2002. Otherwise, how are the readers going to practice using the tool? Thanks,
Sincerely, David Zuo.
Rating:
Summary: Decent book on how to use Rotaional Rose and UML
Review: I purchase this book to learn how to use Roational Rose 2002, and to get a better understanding of UML. After reading this book, I have achieved the goal. Few suggestions to the authors: 1) At the end of the book, if there were a COMPLETE sample, illusating the whole process, from Business Use Case Diagrams, to Deployement diagrams, then this book would be more complete and useful. 2) The book should come with a trail version of Rational Rose 2002. Otherwise, how are the readers going to practice using the tool? Thanks,
Sincerely, David Zuo.
Rating: 
Summary: Could be condensed to about a 50 page book
Review: I would have to agree that this book does not cover UML AT ALL! If you have no idea what UML is, then this book MIGHT present something new (but not necessarily usefull) to you. If you have never used Rose before then a quick scan through this book will familiarize you with the environment through the book's multiple screen shots. However, the book should be retitled "Overly heavy user's manual for Rational Rose." There is no insight into UML or using Rose that is not covered more precisely in the user's manual that accompanies Rose. If you are considering using Rose and have no idea what its capabilities are prior to purchase, this book still will not be of use (try the web - it's free). The step-by-step instructions are already outdated if you use Rose 2000 and they take up over 400 pages if you add them together (much of the space is used repeating the same procedure). Add to that the 400-500 pages of screen shots and you are left with about 50 pages of actual content. Overall, this book is horribly composed and is nothing more than a walk-through of Rose 98/98i. END
Rating: 
Summary: Thorough Rose user manual, but...
Review: Its many screen shots and detailed steps definitely help you maximize Rational Rose, but as a UML guide it falls short. From the title I was expecting to get a walkthrough of UML using Rose as the vehicle, but it is really the reverse: a walkthrough of Rose using UML as the vehicle. I have very few questions left about Rose but I'm buying another book on UML :-(.
Rating:
Summary: It's useless, don't buy it.
Review: Maybe its name should be "Complete screen shots of Rational Rose", it really is. There are absolutely no contents. You cannot use it to learn UML or OOA/D. If you don't have Rational Rose software but want to learn how to use the tool, the book might be somewhat useful since it contains (almost) all the screens Rose has. That's the only usage of this book I can think of.
Rating:
Summary: Tree Huggers Unite!
Review: Seldom do I take pen in hand to review a technical book, but herewith the exception that proves the rule. The compelling reason to break the rule is that there is, within this treatise, a glimmer of the true reality one finds out there in the world of project plans, organizational politics, object oriented gurus and missed deadlines. How such a simple project could possibly be extended into the magnificent total of 950+ pages is more an example of why projects fail that the description of a methodology that would help them to succeed. The authors seem like pleasant people, the kind that make sure that the pussy cats have a fresh bowl of cream before they go to work in the morning. On the other hand, as authors, given the choice between the project for which this code was written and the project this code was written for...sadly...would opt for the latter. I am also slightly suspect of their qualifications given the blizzard of witless, pointless, recurring detail they have spewn onto the printed page. It's almost like they concocted a rich stereotype for the legal market that developed a life of it's own within their word processor. (I'm sure the Sierra Club has them on their list of tree haters). You see, I think that 'object oriented' might have something to do with it. I can't count the number of nights I've spent trying to code off of documents consisting of little stick figures that seemed to be making brownies, the collaboration diagram that implied sleeping with the enemy, and sequence charts that seemed to describe the Macarena. Interestingly, the object-oriented gurus weren't around at this hour. They had played patti-cake with the users from 9 'til 5 and were safely home in their snug little beds. How bad was it? On one major project, no guff, we were told "just code something......we'll clean it up later". So, in conclusion, I think what you have here is just what I've come the expect from these guys: Reams of blinding yet curiously pointless, useless yet remarkably similar, pointless yet expressed with religious fervor BULLSHIT which you get to figure out how to make work while they are safe and sound in their snug little beds. Sleep well darlings.
Rating:
Summary: Tree Huggers Unite!
Review: Seldom do I take pen in hand to review a technical book, but herewith the exception that proves the rule. The compelling reason to break the rule is that there is, within this treatise, a glimmer of the true reality one finds out there in the world of project plans, organizational politics, object oriented gurus and missed deadlines. How such a simple project could possibly be extended into the magnificent total of 950+ pages is more an example of why projects fail that the description of a methodology that would help them to succeed. The authors seem like pleasant people, the kind that make sure that the pussy cats have a fresh bowl of cream before they go to work in the morning. On the other hand, as authors, given the choice between the project for which this code was written and the project this code was written for...sadly...would opt for the latter. I am also slightly suspect of their qualifications given the blizzard of witless, pointless, recurring detail they have spewn onto the printed page. It's almost like they concocted a rich stereotype for the legal market that developed a life of it's own within their word processor. (I'm sure the Sierra Club has them on their list of tree haters). You see, I think that 'object oriented' might have something to do with it. I can't count the number of nights I've spent trying to code off of documents consisting of little stick figures that seemed to be making brownies, the collaboration diagram that implied sleeping with the enemy, and sequence charts that seemed to describe the Macarena. Interestingly, the object-oriented gurus weren't around at this hour. They had played patti-cake with the users from 9 'til 5 and were safely home in their snug little beds. How bad was it? On one major project, no guff, we were told "just code something......we'll clean it up later". So, in conclusion, I think what you have here is just what I've come the expect from these guys: Reams of blinding yet curiously pointless, useless yet remarkably similar, pointless yet expressed with religious fervor BULLSHIT which you get to figure out how to make work while they are safe and sound in their snug little beds. Sleep well darlings.
Rating: 
Summary: Convenient for learning Rational Rose
Review: The title of this book could more appropriately be "Mastering Rational Rose using UML" and not the other way around. This is one of the better books on Rational Rose and gives a quick overview of the different Rose features. It does not cover all of UML but it can be sufficient depending on your needs. UML is very broad - it will be incredibly difficult to sum it all in one book. The authors have done admiringly well. It will be up to readers to research further into specific areas of their interest after obtaining the overview here. I would recommend this book to readers who would like a gentle introduction to UML using one of the most powerful tools around, Rational Rose. For audiences that are already very familiar with UML, this book is recommended if you would like to get acquainted with Rational Rose faster. I hope you find this review helpful.
Rating:
Summary: Convenient for learning Rational Rose
Review: The title of this book could more appropriately be "Mastering Rational Rose using UML" and not the other way around. This is one of the better books on Rational Rose and gives a quick overview of the different Rose features. It does not cover all of UML but it can be sufficient depending on your needs. UML is very broad - it will be incredibly difficult to sum it all in one book. The authors have done admiringly well. It will be up to readers to research further into specific areas of their interest after obtaining the overview here. I would recommend this book to readers who would like a gentle introduction to UML using one of the most powerful tools around, Rational Rose. For audiences that are already very familiar with UML, this book is recommended if you would like to get acquainted with Rational Rose faster. I hope you find this review helpful.
Rating:
Summary: Rational rose and problems
Review: There are absolutely nothing about UML. Do not buy this book. There is only 10 pages about UML.
| 
