- Paperback: 464 pages
- Publisher: Addison-Wesley Professional; 1 edition (April 18, 2003)
- Language: English
- ISBN-10: 0321166094
- ISBN-13: 978-0321166098
- Product Dimensions: 7 x 1.1 x 8.9 inches
- Shipping Weight: 1.3 pounds (View shipping rates and policies)
- Average Customer Review: 18 customer reviews
- Amazon Best Sellers Rank: #1,609,816 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP: A Practitioner's Guide to the RUP 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Frequently bought together
Customers who bought this item also bought
From the Back Cover
"Per Kroll and Philippe Kruchten are especially well suited to explain the RUP...because they have been the central forces inside Rational Software behind the creation of the RUP and its delivery to projects around the world."
--From the Foreword by Grady Booch
This book is a comprehensive guide to modern software development practices, as embodied in the Rational Unified Process, or RUP. With the help of this book's practical advice and insight, software practitioners will learn how to tackle challenging development projects--small and large--using an iterative and risk-driven development approach with a proven track record.
The Rational Unified Process Made Easy will teach you the key points involved in planning and managing iterative projects, the fundamentals of component design and software architecture, and the proper employment of use cases. All team members--from project managers to analysts, from developers to testers--will learn how to immediately apply the RUP to their work. You will learn that the RUP is a flexible, versatile process framework that can be tailored to suit the needs of development projects of all types and sizes.
Key topics covered include:
- How to use the RUP to develop iteratively, adopt an architecture-centric approach, mitigate risk, and verify software quality
- Tasks associated with the four phases of the RUP: Inception, Elaboration, Construction, and Transition
- Roles and responsibilities of project managers, architects, analysts, developers, testers, and process engineers in a RUP project
- Incrementally adopting the RUP with minimal risk
- Common patterns for failure with the RUP--and how to avoid them
Use this book to get quickly up to speed with the RUP, so you can easily employ the significant power of this process to increase the productivity of your team.
About the Author
Per Kroll manages the development of RUP and is responsible for IBM Rational process strategy. He launched and is the project lead for the open source process initiative Eclipse Process Framework (EPF). In addition to his highly acclaimed books, Per has written for a variety of trade magazines.
Philippe Kruchten is the lead architect of the Rational Unified Process. He has more than thirty years of experience in the development of large software-intensive systems for the telecommunications, defense, aerospace, and transportation industries. His book The Rational Unified Process: An Introduction (Addison-Wesley) has been translated into eight languages and has sold more than 160,000 copies in its two previous editions.
Top customer reviews
Despite title of the book, it wasn't always easy reading and only careful contemplation of particular parts and relentless renewal of what was already read, revealed some deep currents of the book. Similarly to the RUP, which is software product with model described in OMG/SPEM, and thus result of software development process also the book as a system of articles can be seen as result of similar development process. The book has its well defined structure, beautiful architecture, which provide curious reader with many abstract overlapping views on such a complex theme as the software development is. Many parallels, questions and almost dilemmas arose while reading the book, particularly about software quality factors, process centricity and their relation to participants involved in the process. Every successful project is the effort of people who play various roles within the process on a domain they understand well but not always such effort is enough to make project successful. Sometimes it's necessary to include among project objectives also improvement of its participants and perfect success can be achieved only in case if participants can make such well defined progress. Here it reminds me about favourite "perfect is enemy of good" and thinking whether principles that guide people don't relate to the originality of their products. The book is great, reader oriented, but alerts me about where to start and especially when to start for better understanding it. I guess it's OOAD (020189551X), The UML User Guide (0321267974), The United Software Development Process (0201571692) and Object Solutions (0805305947), which provide a curious and detail oriented reader with rough structure where the roof can be rationally placed on.
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!
- "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.