- Shopping Bag ( 0 items )
"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 RUPwith 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.
|Pt. I||Introducing the Rational Unified Process||1|
|Ch. 1||Introducing the Rational Unified Process||3|
|Ch. 2||The Spirit of the RUP: Guidelines for Success||27|
|Ch. 3||Comparing Processes: The RUP, Agile Methods, and Heavyweight Government Standards||49|
|Ch. 4||The RUP for a Team of One: Project Deimos||67|
|Pt. II||The Lifecycle of a Rational Unified Process Project||85|
|Ch. 5||Going Through the Four Phases||87|
|Ch. 6||The Inception Phase||93|
|Ch. 7||The Elaboration Phase||113|
|Ch. 8||The Construction Phase||139|
|Ch. 9||The Transition Phase||161|
|Pt. III||Adopting the Rational Unified Process||177|
|Ch. 10||Configuring, Instantiating, and Customizing the Rational Unified Process||179|
|Ch. 11||Adopting the Rational Unified Process||197|
|Ch. 12||Planning an Iterative Project||223|
|Ch. 13||Common Mistakes When Adopting and Using the RUP ... and How to Avoid Them||243|
|Pt. IV||A Role-Based Guide to the Rational Unified Process||271|
|Ch. 14||A Project Manager's Guide to the RUP||273|
|Ch. 15||An Analyst's Guide to the RUP||287|
|Ch. 16||An Architect's Guide to the RUP||311|
|Ch. 17||A Developer's Guide to the RUP||333|
|Ch. 18||A Tester's Guide to the RUP||359|
The RUP guides software practitioners in effectively applying modern software best practices, such as developing iteratively, taking an architecture-centric approach, mitigating risk at every stage in the process, and continuously verifying the quality of the software. Although thousands of projects today are using the RUP effectively, many teams are intimidated by the thought of implementing a new process that they perceive as large and complex. The RUP does not have to be large, and it is not complex.
The goal of this book is to show you how simple the RUP actually is. It explains the underlying software development principles behind the RUP and guides you in the application of the process in your development organization. It will also show you the way to carve a RUP Process Configuration of the right size for your organization or project.
During more than a decade of assisting companies in adopting the RUP and its predecessors, and six years of leading the development of the RUP product, we have had the opportunity to see what works and what does not. We have seen the rewardsof successful adoption of the RUP, and we have seen the challenges that projects and team members may encounter along the way. We have also been privileged to work with many leading software practitioners and have learned from them through daily interaction and practical experience in actual projects.
Lately, we have seen a number of companies adopt too much of the RUP. Yes, there is such a thing as "too much of the RUP." We felt there was a need for a book on the RUP that not only tells you what to do, and what artifacts to produce, but also tells you how to streamline your process and what not to do. We wanted to explain how to adopt the RUP in practice, and when to apply what parts of the RUP in a given project. We wanted to help you understand how to apply the RUP to projects of different sizes or of different types.
Through this book, we want to share some of the insights we and our colleagues have gained over the years: Our intent is to provide Project Managers, Analysts, Architects, Developers, Testers, Process Engineers, and other team members and stakeholders with an easy-to-understand guide to the RUP. We have done this by extracting, from our practical experiences with the RUP, the essence of what each role needs to know about the RUP and explaining their role within it.
This book is not a substitute for the RUP product itself. While the book provides a couple of hundred pages of practical guidance, the RUP product provides thousands of pages of direction for a wide array of roles and activities, as well as templates for accelerating your work. It also provides tight integration with desktop tools, a search engine, graphical navigation, and other features you expect from a Web-based knowledge base. Unlike this book, the RUP is continuously evolving, bringing you up-to-date guidance to apply to your projects. Finally, this book will also guide you in customizing the RUP framework to suit your specific needs.
By reading this book, you will learn
This book is targeted specifically to
This book is divided into four parts: introduction, walkthrough, adoption, and role-specific guidelines.
Part I introduces the RUP. Chapter 1 RUP is and the motivation behind its development and its application. Chapter 2, "The Spirit of the RUP," describes the underlying principles behind the RUP--these are based on the experiences gleaned from a number of successful projects and distilled into a few simple guidelines. Understanding these principles will help you better apply the RUP to your own projects. Chapter 3 provides a method for comparing processes, and we use it to compare the RUP to other agile processes, to more conventional processes, and to process assessment frameworks such as SEI CMM and SPICE. These comparisons will help you understand which project type should use what type of RUP configuration. Chapter 4 provides an example that applies the RUP to a very small project: one person for one week. By peeling away the ceremony needed for larger projects, you can focus on the essential elements of the RUP.
Part II presents the RUP by walking through each of the four phases in a RUP project: Inception, Elaboration, Construction, and Transition. Chapter 5 addresses some common misconceptions of the four phases by explaining how the iterative approach applies to them. Chapters 6-9 describe each of the four phases in detail. We focus on what is to be achieved--that is, the objectives of each phase--and guide you in reaching those objectives. This will help you to stay focused on the most essential activities in an actual project. Additionally, we present the RUP activities in a time-based perspective-that is, in the order they are applied in a real project-to give you a reference to understand when to do the activities as you work through a project.
Adopting the RUP requires some preparation and some preliminary knowledge on the part of the adopting organization. Part III provides basic knowledge in key areas to support a streamlined implementation. Chapter 10 walks you through the RUP product, detailing how it can be extended and customized to meet project- and organization-specific needs. Chapter 11 briefly outlines some strategies that may be useful for implementing the process including incremental rollout, pilot projects, and training curricula. Our experience shows that moving from a waterfall approach to iterative development can be a difficult transition for Project Managers, and Chapter 12 provides guidelines for planning a RUP project. Over the years, we have seen patterns of success and patterns of failure in RUP adoptions. Chapter 13 discusses the patterns of failure and how to avoid them, guarding you from repeating the mistakes of others.
The RUP product provides comprehensive guidelines for a wide array of software development activities. Part IV, Chapters 14-18, presents guides for each of the five key roles in any software project: the Project Manager, Analyst, Architect, Developer, and Tester. For each role, we present the RUP from that role's perspective, and we describe the mission, the desired qualifications, and the key activities, as well as recommended reading and training. Note that there is no separate chapter for the Process Engineer: Most of this role is described in Chapters 10 and 11.
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:
Additional information about the RUP product, including a data sheet and a product demo, can be obtained from Rational Software at our site.
Posted March 10, 2003
Posted April 9, 2010
No text was provided for this review.