Rating: 
Summary: Great book
Review: This is a great book. It was the first book that actually described RUP, besides the documentation. It's a good and an easy read, and you'll know hat RUP is all about after you have read the book. You will need to practice just like anything else, but this book is a very good starting point. The newer versions of this book is much better, so buy that instead.
Rating: 
Summary: It's The Introduction to RUP
Review: This is a very dense introduction for RUP. You need to read twice to get the complete idea. But the book can be read by workflows (disciplines) individually to emphasize your interest areas. I'm sorry for the folks that think this book is publicity for the Rational software. Did they read the book? This book is already part of the RUP AS A PRODUCT. I read because i want to complete my knolwedge on the process and software engineer process iteself. The book emphasizes in the goods of the process as a process model and a framework not as a product. Buy it, if you are interested in one of the most popular software engineer process outer or want to get some good advices to your own processes. If you're an opposite of RUP, if you aren't interested in software enginnering process at all, don't get it and don't waste your time submitting bad reviews. Judge the book as is: an introduction to RUP.
Rating: 
Summary: RUP is insufficient for software engineering
Review: While this book has received great reviews I must offer disagreement. As an experienced OO professional (I've been working in OO practically since the beginning) the RUP leaves a lot to be desired. For one thing there is not nearly enough emphasis on requirements gathering and process engineering. For the most part the analysis aspect of RUP focuses on Use Case Scenarios. I feel that this is a major weakness. Use Case Scenarios focus on how user's use the system, but doesn't answer the question: What system? To dive into Use Case Scenarios without first applying process engineering at a detailed level leaves you with a system that no one really asked for. Furthermore I feel there is not enough emphasis on using Use Case Scenarios as a vehicle for test designs. One of the greatest advantages of Use Case Scenarios, when there done at a very detailed level, is to use them as a System Test design. This would include "expected results" for each step. Also, I don't feel there is sufficient evidence for support of logical object modeling as apposed to physical object modeling. It's common knowledge with database design that logical modeling comes first, then the physical. This same tactic should be employed with OO modeling. This includes both class models and use case scenarios. This is especially valuable in the Java and EJB environment where Session beans differ from Entity beans and both differ from regular Java classes, singletons etc. Another reviewer mentioned that this book might be a vehicle for selling Rational products. I agree. That's exactly what this is.
If you're an experienced analyst there are still some takeaways from the book, but you will have to augment it with your own knowledge and experience. The danger lies with inexperienced analysts thinking that they can define and design complex systems using RUP, and that it's sufficient. It's not.
| 
