How to Read This Book

Based on your role in your software organization and what you want to learn from this book, we recommend the following readings :

• If you are looking for a brief overview of the RUP, read Chapters 1, 2, and 4.

• If you are looking for a detailed overview of the RUP, read Chapters 1 “9.

• If you are looking for a detailed understanding of the RUP, including specific role responsibilities:

  - For Project Managers, read Chapters 1 “14.

  - For Analysts, read Chapters 1 “9, 13, and 15 ( optionally , browse through Chapters 8 and 9).

  - For Architects, read Chapters 1 “9, 13, and 16.

  - For Developers, read Chapters 1 “9, 13, and 17 (optionally, browse through Chapter 6).

  - For Testers, read Chapters 1 “9, 13, and 18.

  - For Process Engineers, read Chapters 1 “11 and 13.

• If you are an executive looking for a brief overview of the RUP and what it takes to adopt the RUP, read Chapters 1, 2, 4, and 11.

For More Information

Latest information related to this book, including updates, relevant articles, discussion forums, and author speaking schedules can be found on http://www.rupmadeeasy.com.

Additional information about the RUP product, including a data sheet and a product demo, can be obtained from Rational Software at http://www.rational.com/products/rup.

If you are already using the RUP product, additional resources are available from the RUP Knowledge Center on the Rational Developer Network (RDN) at http://www.rational.net.

Academic institutions can contact Rational Software for information on a special program for including the RUP in a software engineering curriculum: http://www.rational.com/corpinfo/college_relations/seed/index.jsp.

Acknowledgments

The Rational Unified Process captures the experiences of thousands of talented software practitioners , and we are honored to have been able to work with them to evolve the RUP product and to write this book.

This book would not have been possible without the RUP product and its current product team: Mike Barnard, Amanda Brijpaul, Susan Buie, Margaret Chan, Fionna Chong, Erin Curtis, Philip Denno, Carlos Goti, Debra Gray, Bj rn Gustafsson, Sigurd Hopen, Kelli Houston, Lars Jenzer, John Lambert, Bruce MacIssac, Bryant Macy, Glenys MacIsaac, John Ringoen, Dan Shiffman, Paul Szymkowiak, and Chinh Vo.

Over the years , the Rational field teams and technical experts have accumulated a lot of experience in implementing and using the RUP. We are grateful for the many insightful review comments and ideas from these experts, which added a lot of insights on what works and what does not out in the trenches. Especially, we would like to recognize Goran Begic, Thomas Bichler, Kurt Bittner, Anthony Crain, Sam Courtenay, J r me Desquilbet, Maria Ericsson, Carlos Goti, Jim Heumann, Joe Marasco, Pan-Wei Ng, Andy Phillipson, Gary Pollice, Leslee Probasco, Walker Royce, John Smith, and Ian Spence.

Our external reviewers provided invaluable feedback, forcing us to rethink the structure and content of the book, hopefully helping us to create a book that is easier to read and address the issues you find most relevant in a book about the RUP. These insights were provided by Susan Burk, Celso Gonzales, Gary Pollice, and Dan Rawsthorne.

We are also thankful to Grady Booch for reviewing the book and for writing the foreword.

When you put a French guy and Swedish guy together to write a book, needless to say huge opportunities to improve the manuscript's language are created. Rational Software editors Catherine Southwood, Mike Perrow, and Marlene Ellin dove into this task with a lot of energy and professionalism , as did our external editors Kelly Sweeney and Joseph Fatton.

We also wanted to give special thanks and love to our wives, Susan Kroll and Sylvie Kruchten, for being patient with the many weekends and nights spent writing and rewriting the book.

And finally, many thanks to our publisher, Mary O'Brien, and the production and marketing teams at Addison-Wesley, including Tyrrell Albaugh and Christopher Guzikowski, for helping us get this book out.