Customer Reviews

The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP

5 star:		(13)
4 star:		(2)
3 star:		(1)
2 star:		(0)
1 star:		(0)

 

 

"RUP Made Easy" is the best book available for anyone trying to learn how to actually do RUP. "The Rational Unified Process: An Introduction" by Kruchten (3rd Ed.) does a better job of explaining the principles behind RUP, but the problem with "An Introduction" is that it does not explain how to actually do anything. "Made Easy", on the other hand, is filled with lots of practical examples. I usually recommend "An Introduction" for senior managers within the organization who need to understand why we are using RUP; but for the project managers, analysts and developers who are doing the actual work I always recommend "Made Easy". "Made Easy" is also the book I am most likely to turn to for reference when someone asks a question about RUP.

First of all, let me share with you something that most of you may already know: There are only three books on the RUP. Namely:
- "The Rational Unified Process, An Introduction", by Philippe Kruchthen
- This book
- The Eeles et al. book on J2EE and RUP.

I haven't read any of the other two books, so I cannot tell you how this book falls into the greater scheme of things. I.e. I do not know what sort of overlap exists with the RUP Intro book, or which of the two to read first, etc. What I can tell you though is that this book, as it stands on its own, is a very good book in helping you (a) understand what the RUP is and (b) understand how to apply it on your projects.

First of all, the two authors of the book are as authoritative as can be. Kruchten (the author of the Intro book) is the chief technical RUP guy in Rational. Kroll is the Rational director (or whatever his new title is now under IBM) responsible for the RUP. These guys know the RUP and in a sense _are_ the RUP.

Now, to focus more on the book per se, it is as follows: It starts with a general intro chapter and then it moves on to chapter 2, which captures the so-called "Spirit of the RUP". It contains 8 tenets which sort-of summarize the philosophy of the RUP. Just as with a legal system, where it is not sufficient to only know articles of laws and statutes but you have to be extremely familiar and cognizant of the context in which these laws are applied and the purpose they serve in order to judge correctly, similarly with the RUP you don't only need to know the product with all the info and features it provides, but you need to have absorbed the philosophy that governs the process in order to apply the given material in the appropriate and most fruitful manner.

Chapter 3 I found (the emphasis is on "I"; you mileage may vary) the most useful. It basically charts the whole territory of processes that are out there (RUP, XP, other agile processes, heavyweight assessment standards such as the CMM) based on two important criteria, and tries to make you understand where RUP falls in the plane (and it is not really a fixed point, as RUP is customizable so there is some sort of leeway in how much iterative and/or ceremonial we want it to be).

Chapter 4 is an aberattion to the rest of the book IMHO, and I haven't found it much useful, or to my liking. It basically tries to explain RUP phases etc. in the context of a one-man project. I am not saying that this is necessarily a bad way to try to introduce people to the concepts of RUP in a more practical context - maybe you'll like it; I just didn't.

Afterwards, in chapter 5-9 we have an expounding of the 4 RUP phases, while chapter 10 is product-specific. Chapter 11 is extremely important as it talks about how to adopt the RUP in your organization, and proposes as the way to do so, treating the RUP adoption as a project of its own and applying some sort of "meta-RUP" on it; very interesting! Chapter 12 talks about planning an iterative project and Ch. 13 covers "antipatterns" (although the authors, to their credit, avoid using that term). Ch. 13 is very important reading and some of the stuff in there (e.g. the discussion on what constitutes a bad use case) you will find useful in a context much wider than the RUP.

Because each one of the roles (PM, Architect, Developer, etc.) views the process from their own unique perspective (just as power forward views the ballgame more in the perspective of getting many rebounds, whereas the point guard views in the sense of passing assists and shooting the occasional 3-pointer) it is very useful to have a chapter discussing each role's unique perspective of the RUP. My opinion is the all roles must read the chapters for all roles, but if you are short on time, this also helps you focus on the stuff strictly pertaining to your role. Although I am not a tester per se, I liked very much the discussion on "Good Enough Quality" in the Tester chapter. "Paradigms of Good Enough" and "The Cost of Quality" I have found to be a "must-read".

Also, the book has good references (both books and Web articles - especially from the RationalEdge) and the usual good quality you would expect from an AW publication in general and an OTS book in particular. Finally, even though in the intro the authors play a little pun on themselves on being French and Swedish respectively and thus non-native English speakers, don't get scared by that comment. Their English is excellent.

All in all, a very good and useful read. Buy it if only for chapters 3, 13, and 18. Actually, you may want to buy it even if you are not intending to use the RUP.

I teach RUP classes in Brazil and the most difficult thing for the students is to understand the core practices of RUP(what I like to call Agile RUP) without getting swallowed by all the details of the hundreds activities, artifacts, roles, guidelines, etc.

This book is the best way for a student to understand RUP after a few lessons with a teacher. It's very practical and focused on the core practices of RUP.

Read this book and you probably will not fall in the trap of using RUP in a waterfall way or think of RUP as a heavyweight process :-) !!

For years, the only intro for RUP was Philippe Kruchten's book. And it was not enough... Then Larman's book came out (the great one, no doubt!), but this book is too much for someone who wants to understand process without going into UML discussions (the main purpose of Larman's book).
"Rational Unified Process Made Easy" finally closes the gap.
Even if you know (or think you know) RUP, it would be a good idea to buy this one.

There is plenty of theory written about RUP, but how it should be applied to your role or your project is often misunderstood.
This book not only provides the overview, but the contextual guidance to make RUP work for you.
As a long-term RUP mentor and user, I highly recommend it.

This book does a great job of showing steps of practical application of the RUP. The book may seem repetitive on a few points, but I feel the points bear repeating. This book has been invaluable in helping cut through the misinformation thrown around by some who have gotten the executive summary of RUP and know just enough to be dangerous. I recently completed a seven-part online course on the RUP that was based on this book. The book did a far better job of making the RUP understandable.

This is a good book telling the philosophy behind RUP. And it also gives some practical advice to adopt, config and apply RUP.Although it is not a thorough description of RUP because it doesn't systematicly describe the disciplines in RUP, it provides some other reference. A good book for RUP beginners.

I'm a solo developer, and without this book i would be refactoring my code every few days still.

Thank you RUP for putting my head on straight to understand iterations of the SDLC and apply them to even small projects with few assets.

RUP gives you the tools to understand your system before you write it by iteratively working with the people who will be using the system! Your customers/Users!

Excellent guide to get up to speed with RUP. Having never worked with RUP this guide proved extremely beneficial to get the project started and will be used through all iterations.

I read this book couple times and both found something interesting. May be it's the best one as for RUP. Even if you do not practice RUP, preferring other methodologies instead, reading this book wouldn't hurt.