The Rational Unified Process: An Introduction by Philippe KruchtenThe Rational Unified Process: An Introduction by Philippe Kruchten

The Rational Unified Process: An Introduction

byPhilippe Kruchten

Paperback | December 10, 2003

Pricing and Purchase Info

$56.22 online 
$62.99 list price save 10%
Earn 281 plum® points

Prices and offers may vary in store

Quantity:

In stock online

Ships free on orders over $25

Not available in stores

about

The Rational Unified Process is a software engineering process developed and marketed originally by Rational Software, and now IBM. It is a disciplined approach to assigning and managing tasks and responsibilities in a development organization. The goal of this process is to produce, within a predictable schedule and budget, high-quality software that meets the needs of its end users. The Rational Unified Process captures many of the best practices in modern software development and presents them in a tailorable form that is suitable for a wide range of projects and organizations. The Rational Unified Process delivers these best practices to the project team online in a detailed, practical form. This book provides an introduction to the concepts, structure, contents, and motivation of the Rational Unified Process. Goals of This Book In this book, you will learn what the Rational Unified Process is and what it is not; master the vocabulary of the Rational Unified Process and understand its structure; develop an appreciation for the best practices that we have synthesized in this process; and understand how the Rational Unified Process can give you the guidance you need for your specific responsibility in a project. This book is not the complete Rational Unified Process. Rather, it is a small subset to introduce the RUP. In the full Rational Unified Process you will find the detailed guidance needed to carry out your work. The full Rational Unified Process-;the online knowledge base-;is a product that can be obtained from IBM. This book makes numerous references to the Unified Modeling Language UML , but it is not an introduction to the UML. That is the focus of two other books: The Unified Modeling Language User Guide Addison-Wesley, 1999 and The Unified Modeling Language Reference Manual Addison-Wesley, 1999 . This introductory book speaks about modeling and object-oriented techniques, but it is not a design method, and it does not teach you how to model. Detailed steps and guidance on the various techniques that are embedded in the Rational Unified Process can be found only in the process product. Several chapters of this book discuss project management issues. They describe aspects of planning an iterative development, managing risks, and so on. This book, however, is by no means a complete manual on project management and software economics. For more information, we refer you to the book Software Project Management: A Unified Framework Addison-Wesley, 1998 . The Rational Unified Process is a specific and detailed instance of a more generic process described in the textbook The Unified Software Development Process Addison-Wesley, 1998 . who should read this book? The Rational Unified Process, An Introduction, Third Edition , is written for a wide range of people involved in software development: project managers, developers, quality engineers, process engineers, method specialists, system engineers, and analysts. This book is relevant especially to members of an organization that has adopted the Rational Unified Process or is about to adopt it. It is likely that an organization will tailor the Rational Unified Process to suit its needs, but the core process described in this book should remain the common denominator across all instances of the Rational Unified Process. This book will be a useful companion to students taking one of the many professional education courses delivered by IBM Rational Software and its partners in industry and academia. It provides a general context for the specific topics covered by the course. We assume that you have a basic understanding of software development. It is not necessary that you have specific knowledge of a programming language, of an object-oriented method, or of the Unified Modeling Language. How to Use This Book Software professionals who are working in an organization that has adopted the Rational Unified Process, in whole or part, should read the book linearly. The chapters have been organized in a natural progression. Project managers can limit their reading to Chapters 1, 2, 4, and 7, which provide an introduction to the implications of an iterative, risk-driven development process. Process engineers or methodologists may have to tailor and install the Rational Unified Process in their organizations. They should carefully study Chapters 3, 14, and 17, which describe the process structure and the overall approach to implementing the Rational Unified Process. Organization and Special Features The book has two parts. Part I describes the process, its context, its history, its structure, and its software development lifecycle. It describes some of the key features that differentiate the Rational Unified Process from other software development processes: Chapter 1: Software Development Best Practices Chapter 2: The Rational Unified Process Chapter 3: Static Structure: Process Description Chapter 4: Dynamic Structure: Iterative Development Chapter 5: An Architecture-Centric Process Chapter 6: A Use-Case-Driven Process Part II gives an overview of the various components of process, or disciplines. There is one chapter for each discipline. Chapter 7: The Project Management Discipline Chapter 8: The Business Modeling Discipline Chapter 9: The Requirements Discipline Chapter 10: The Analysis and Design Discipline Chapter 11: The Implementation Discipline Chapter 12: The Test Discipline Chapter 13: The Configuration and Change Management Discipline Chapter 14: The Environment Discipline Chapter 15: The Deployment Discipline Chapter 16: Typical Iteration Plans Chapter 17: Implementing the Rational Unified Process Most discipline chapters are organized into six sections: Purpose of the discipline Definitions and key concepts Roles and artifacts A typical workflow: an overview of the activities Tool support Summary Two appendixes summarize all the roles of the process and artifacts the work products of the process that are introduced in Chapters 7 through 15. A list of acronyms and glossary of common terms are provided, as is an annotated bibliography. For More Information Information about the Rational Unified Process, such as a data sheet and a downloadable demo version, can be obtained from IBM, Rational Software via the Internet at www.rational.com/rup/. If you are already using the Rational Unified Process, additional information is available from the Rational Developers Network, which has extra goodies, updates, and links to partners. The hyperlink to the RDN is in the online version of RUP. Academic institutions can contact IBM for information on a special program for including the Rational Unified Process in the curriculum. Second Edition The second edition of The Rational Unified Process: An Introductionmade the book current with the Rational Unified Process 2000. Third Edition This third edition of The Rational Unified Process: An Introductionmakes the book current with the Rational Unified Process 2003. This edition implements several changes of terminology, some redesign of parts of the process in particular, the test and environment disciplines , as well as the further development of RUP as a process framework. New elements are introduced--the concept of process components and process plug-ins, a new tool set comprising RUP Modeler, RUP Organizer, RUP Builder, and MyRUP, and a separate Process Engineering Process. It incorporates the feedback of many readers and acknowledges the acquisition of Rational Software by IBM. Acknowledgments The Rational Unified Process reflects the wisdom of a great many software professionals from Rational Software and elsewhere. The history of the process can be found in Chapter 2. But putting together a book, even as small and modest as this one, required the dedicated effort of a slate of people, whom I would like to recognize here. Early members of the Process Development Group assembled the Rational Unified Process and contributed to this introduction. Stefan Bylund, then Kurt Bittner, and finally Bruce Macisaac contributed to the analysis and design chapter. Maria Ericsson developed the business engineering and requirements management aspect with Leslee Probasco. The test part was started by Bruce Katz and then completely redesigned by Paul Szymkowiak. John Smith expanded the project management aspects for RUP 2000. Jas Madhur contributed the ideas on configuration management, change management, and deployment. Hakan Dyrhage contributed many ideas to the organization and structure of the process and to its implementation and configuration. Margaret Chan was responsible for the product integration and for the assembly of most of the artwork in this book with Susan Buie. Sigurd Hopen developed the PEP with the help of Bjoern Gustafsson. Per Kroll is the manager of the development group, Mike Barnard the product manager. Alfredo Bencomo, Chinh Vo, Philip Denno, Lars Jenzer, Glenys Macisaac, and Fionna Chong developed the product infrastructure. And Debbie Gray is the devoted administrative assistant of a team spread across nine time zones. The Rational Unified Process and this book benefited over the past 8 years from the reviews and ideas of Stefan Ahlqvist, Dave Bernstein, Grady Booch, Murray Cantor, Geoff Clemm, Catherine Connor, Mike Devlin, Christian Ehrenborg, Ian Gavin, Christina Gisselberg, Sam Guckenheimer, Bjoern Gustafsson, Matt Herdon, Ivar Jacobson, Paer Jansson, Ron Krubek, Dean Leffingwell, Andrew Lyons, Bruce Malasky, Roger Oberg, Gary Pollice, Terri Quatrani, Walker Royce, Jim Rumbaugh, Ian Spence, John Smith, and Brian White. We are very grateful to Grady Booch for writing Chapter 1. Special thanks go to the Rational field, members of our Chat_RUP list, and our users, members of the RUP_Forum, for their feedback, and contributions. And finally many thanks to our editor Mary O'Brien, our former editor J. Carter Shanklin, as well as Brenda Mulligan, Amy Fleischer and her team, and all the staff at Addison-Wesley for getting this book out as quickly and smoothly as they did. Philippe KruchtenVancouver, B.C., Canada 0321197704P11172003
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 tran...
Loading
Title:The Rational Unified Process: An IntroductionFormat:PaperbackProduct dimensions:336 pages, 8.55 × 6.75 × 0.95 inShipping dimensions:8.55 × 6.75 × 0.95 inPublished:December 10, 2003Publisher:Pearson EducationLanguage:English

The following ISBNs are associated with this title:

ISBN - 10:0321197704

ISBN - 13:9780321197702

Reviews

From the Author

The Rational Unified Process is a software engineering process developed and marketed originally by Rational Software, and now IBM. It is a disciplined approach to assigning and managing tasks and responsibilities in a development organization. The goal of this process is to produce, within a predictable schedule and budget, highquality software that meets the needs of its end users.The Rational Unified Process captures many of the best practices in modern software development and presents them in a tailorable form that is suitable for a wide range of projects and organizations. The Rational Unified Process delivers these best practices to the project team online in a detailed, practical form.This book provides an introduction to the concepts, structure, contents, and motivation of the Rational Unified Process.GOALS OF THIS BOOKIn this book, you will Learn what the Rational Unified Process is and what it is not. Master the vocabulary of the Rational Unified Process. Understand its structure. Develop an appreciation for the best practices that we have synthesized in this process. Understand how the Rational Unified Process can give you the guidance you need for your specific responsibility in a project.This book is not the complete Rational Unified Process. Rather, it is a small subset to introduce the RUP. In the full Rational Unified Process you will find the detailed guidance needed to carry out your work. The full Rational Unified Process—the online knowledge base—is a product that can be obtained from IBM.This book makes numerous references to the Unified Modeling Language (UML), but it is not an introduction to the UML. That is the focus of two other books: The Unified Modeling Language User Guide and The Unified Modeling Language Reference Manual.This introductory book speaks about modeling and objectoriented techniques, but it is not a design method, and it does not teach you how to model. Detailed steps and guidance on the various techniques that are embedded in the Rational Unified Process can be found only in the process product.Several chapters of this book discuss project management issues. They describe aspects of planning an iterative development, managing risks, and so on. This book, however, is by no means a complete manual on project management and software economics. For more information, we refer you to the book Software Project Management: A Unified Framework.The Rational Unified Process is a specific and detailed instance of a more generic process described in the textbook The Unified Software Development Process. WHO SHOULD READ THIS BOOK?The Rational Unified Process, Third Edition is written for a wide range of people involved in software development: project managers, developers, quality engineers, process engineers, method specialists, system engineers, and analysts.This book is relevant especially to members of an organization that has adopted the Rational Unified Process or is about to adopt it. It is likely that an organization will tailor the Rational Unified Process to suit its needs, but the core process described in this book should remain the common denominator across all instances of the Rational Unified Process.This book will be a useful companion to students taking one of the many professional education courses delivered by IBM Rational Software and its partners in industry and academia. It provides a general context for the specific topics covered by the course.This book assumes that you have a basic understanding of software development. It does not require specific knowledge of a programming language, of an objectoriented method, or of the Unified Modeling Language. HOW TO USE THIS BOOKSoftware professionals who are working in an organization that has adopted the Rational Unified Process, in whole or part, should read the book linearly. The chapters have been organized in a natural progression.Project managers can limit their reading to Chapters 1, 2, 4, and 7, which provide an introduction to the implications of an iterative, riskdriven development process.Process engineers or methodologists may have to tailor and install the Rational Unified Process in their organizations. They should carefully study Chapters 3, 14 and 17, which describe the process structure and the overall approach to implementing the Rational Unified Process. ORGANIZATION AND SPECIAL FEATURESThe book has two parts.Part I describes the process, its context, its history, its structure, and its software development lifecycle. It describes some of the key features that differentiate the Rational Unified Process from other software development processes: Chapter 1: Software Development Best Practices Chapter 2: The Rational Unified Process Chapter 3: Static Structure: Process Description Chapter 4: Dynamic Structure: Iterative Development Chapter 5: An Architecturecentric Process Chapter 6: A UseCaseDriven ProcessPart II gives an overview of the various components of process, or disciplines. There is one chapter for each discipline. Chapter 7: The Project Management Discipline Chapter 8: The Business Modeling Discipline Chapter 9: The Requirements Discipline Chapter 10: The Analysis and Design Discipline Chapter 11: The Implementation Discipline Chapter 12: The Test Discipline Chapter 13: The Configuration and Change Management Discipline Chapter 14: The Environment Discipline Chapter 15: The Deployment Discipline Chapter 16: Typical Iteration Plans Chapter 17: Implementing the Rational Unified Process Most discipline chapters are organized into six sections: Purpose of the discipline Definitions and key concepts Roles and artifacts A typical workflow: an overview of the activities Tool support SummaryTwo appendixes summarize all the roles of the process and artifacts (the workproducts of the process) that are introduced in Chapters 7 through 15. A list of acronyms and glossary of common terms are provided, as is an annotated bibliography.FOR MORE INFORMATIONInformation about the Rational Unified Process, such as a data sheet and a downloadable demo version, can be obtained from IBM, Rational Software via the Internet at www.rational.com/rup/.If you are already using the Rational Unified Process, additional information is available from the Rational Developers Network, which has extra goodies, updates, and links to partners. The hyperlink to the RDN is in the online version of RUP.Academic institutions can contact IBM for information on a special program for including the Rational Unified Process in the curriculum.SECOND EDITIONThe second edition of The Rational Unified Process: An Introduction made the book current with the Rational Unified Process 2000.THIRD EDITIONThis third edition of The Rational Unified Process: An Introduction makes the book current with the Rational Unified Process 2003. This edition implements several changes of terminology, some redesign of parts of the process (in particular, the test and environment disciplines), as well as the further development of RUP as a process framework. New elements are introduced, such as the concept of process components and process plugins, a new tool set: RUP Modeler, RUP Organizer, RUP Builder and MyRUP, and the introduction of a separate Process Engineering Process. It incorporates the feedback of many readers, and acknowledges the acquisition of Rational Software by IBM.ACKNOWLEDGMENTSThe Rational Unified Process reflects the wisdom of a great many software professionals from Rational Software and elsewhere. The history of the process can be found in Chapter 2. But putting together a book, even as small and modest as this one, required the dedicated effort of a slate of people, whom I would like to recognize here.Early members of the Process Development Group assembled the Rational Unified Process and contributed to this introduction. Stefan Bylund, then Kurt Bittner, and finally Bruce Macisaac contributed to the analysis and design chapter. Maria Ericsson developed the business engineering and requirements management aspect with Leslee Probasco. The test part was started by Bruce Katz, and then completely redesigned by Paul Szymkowiak. John Smith expanded the project management aspects for RUP 2000. Jas Madhur contributed the ideas on configuration management, change management, and deployment. Hakan Dyrhage had contributed many ideas to the organization and structure of the process and to its implementation and configuration. Margaret Chan was responsible for the product integration and for the assembly of most of the artwork in this book with Susan Buie. Sigurd Hopen developed the PEP, with the help of Bjoern Gustafsson.Per Kroll is the manager of the development group, Mike Barnard the product manager. Alfredo Bencomo, Chinh Vo, Philip Denno, Lars Jenzer, Glenys Macisaac and Fionna Chong developed the product infrastructure. And Debbie Gray is the devoted administrative assistant of a team spread across nine time zones.The Rational Unified Process and this book benefited over the 8 years from the reviews and ideas of Stefan Ahlqvist, Dave Bernstein, Grady Booch, Murray Cantor, Geoff Clemm, Catherine Connor, Mike Devlin, Christian Ehrenborg, Ian Gavin, Christina Gisselberg, Sam Guckenheimer, Bjoern Gustafsson, Matt Herdon, Ivar Jacobson, Paer Jansson, Ron Krubek, Dean Leffingwell, Andrew Lyons, Bruce Malasky, Roger Oberg, Gary Pollice, Terri Quatrani, Walker Royce, Jim Rumbaugh, Ian Spence, John Smith, and Brian White. We are very grateful to Grady Booch for writing Chapter 1.Special thanks go to the Rational field, members of our Chat_RUP list, and our users, members of the RUP_Forum, for their feedback, and contributions.And finally many thanks to our editor Mary O’Brien, our former editor J. Carter Shanklin, as well as Brenda Mulligan, Kristin Erickson, Marilyn Rash and her team, and all the staff at AddisonWesley for getting this book out as quickly and smoothly as they did.—Philippe KruchtenVancouver, B.C., Canada 0321197704P08202003

Read from the Book

The Rational Unified Process is a software engineering process developed and marketed originally by Rational Software, and now IBM. It is a disciplined approach to assigning and managing tasks and responsibilities in a development organization. The goal of this process is to produce, within a predictable schedule and budget, high-quality software that meets the needs of its end users. The Rational Unified Process captures many of the best practices in modern software development and presents them in a tailorable form that is suitable for a wide range of projects and organizations. The Rational Unified Process delivers these best practices to the project team online in a detailed, practical form. This book provides an introduction to the concepts, structure, contents, and motivation of the Rational Unified Process. Goals of This Book In this book, you will learn what the Rational Unified Process is and what it is not; master the vocabulary of the Rational Unified Process and understand its structure; develop an appreciation for the best practices that we have synthesized in this process; and understand how the Rational Unified Process can give you the guidance you need for your specific responsibility in a project. This book is not the complete Rational Unified Process. Rather, it is a small subset to introduce the RUP. In the full Rational Unified Process you will find the detailed guidance needed to carry out your work. The full Rational Unified Process—the online knowledge base—is a product that can be obtained from IBM. This book makes numerous references to the Unified Modeling Language (UML), but it is not an introduction to the UML. That is the focus of two other books: The Unified Modeling Language User Guide (Addison-Wesley, 1999) and The Unified Modeling Language Reference Manual (Addison-Wesley, 1999). This introductory book speaks about modeling and object-oriented techniques, but it is not a design method, and it does not teach you how to model. Detailed steps and guidance on the various techniques that are embedded in the Rational Unified Process can be found only in the process product. Several chapters of this book discuss project management issues. They describe aspects of planning an iterative development, managing risks, and so on. This book, however, is by no means a complete manual on project management and software economics. For more information, we refer you to the book Software Project Management: A Unified Framework (Addison-Wesley, 1998). The Rational Unified Process is a specific and detailed instance of a more generic process described in the textbook The Unified Software Development Process (Addison-Wesley, 1998). who should read this book? The Rational Unified Process, An Introduction, Third Edition , is written for a wide range of people involved in software development: project managers, developers, quality engineers, process engineers, method specialists, system engineers, and analysts. This book is relevant especially to members of an organization that has adopted the Rational Unified Process or is about to adopt it. It is likely that an organization will tailor the Rational Unified Process to suit its needs, but the core process described in this book should remain the common denominator across all instances of the Rational Unified Process. This book will be a useful companion to students taking one of the many professional education courses delivered by IBM Rational Software and its partners in industry and academia. It provides a general context for the specific topics covered by the course. We assume that you have a basic understanding of software development. It is not necessary that you have specific knowledge of a programming language, of an object-oriented method, or of the Unified Modeling Language. How to Use This Book Software professionals who are working in an organization that has adopted the Rational Unified Process, in whole or part, should read the book linearly. The chapters have been organized in a natural progression. Project managers can limit their reading to Chapters 1, 2, 4, and 7, which provide an introduction to the implications of an iterative, risk-driven development process. Process engineers or methodologists may have to tailor and install the Rational Unified Process in their organizations. They should carefully study Chapters 3, 14, and 17, which describe the process structure and the overall approach to implementing the Rational Unified Process. Organization and Special Features The book has two parts. Part I describes the process, its context, its history, its structure, and its software development lifecycle. It describes some of the key features that differentiate the Rational Unified Process from other software development processes: Chapter 1: Software Development Best Practices Chapter 2: The Rational Unified Process Chapter 3: Static Structure: Process Description Chapter 4: Dynamic Structure: Iterative Development Chapter 5: An Architecture-Centric Process Chapter 6: A Use-Case-Driven Process Part II gives an overview of the various components of process, or disciplines. There is one chapter for each discipline. Chapter 7: The Project Management Discipline Chapter 8: The Business Modeling Discipline Chapter 9: The Requirements Discipline Chapter 10: The Analysis and Design Discipline Chapter 11: The Implementation Discipline Chapter 12: The Test Discipline Chapter 13: The Configuration and Change Management Discipline Chapter 14: The Environment Discipline Chapter 15: The Deployment Discipline Chapter 16: Typical Iteration Plans Chapter 17: Implementing the Rational Unified Process Most discipline chapters are organized into six sections: Purpose of the discipline Definitions and key concepts Roles and artifacts A typical workflow: an overview of the activities Tool support Summary Two appendixes summarize all the roles of the process and artifacts (the work products of the process) that are introduced in Chapters 7 through 15. A list of acronyms and glossary of common terms are provided, as is an annotated bibliography. For More Information Information about the Rational Unified Process, such as a data sheet and a downloadable demo version, can be obtained from IBM, Rational Software via the Internet at www.rational.com/rup/. If you are already using the Rational Unified Process, additional information is available from the Rational Developers Network, which has extra goodies, updates, and links to partners. The hyperlink to the RDN is in the online version of RUP. Academic institutions can contact IBM for information on a special program for including the Rational Unified Process in the curriculum. Second Edition The second edition of The Rational Unified Process: An Introduction made the book current with the Rational Unified Process 2000. Third Edition This third edition of The Rational Unified Process: An Introduction makes the book current with the Rational Unified Process 2003. This edition implements several changes of terminology, some redesign of parts of the process (in particular, the test and environment disciplines), as well as the further development of RUP as a process framework. New elements are introduced--the concept of process components and process plug-ins, a new tool set comprising RUP Modeler, RUP Organizer, RUP Builder, and MyRUP, and a separate Process Engineering Process. It incorporates the feedback of many readers and acknowledges the acquisition of Rational Software by IBM. Acknowledgments The Rational Unified Process reflects the wisdom of a great many software professionals from Rational Software and elsewhere. The history of the process can be found in Chapter 2. But putting together a book, even as small and modest as this one, required the dedicated effort of a slate of people, whom I would like to recognize here. Early members of the Process Development Group assembled the Rational Unified Process and contributed to this introduction. Stefan Bylund, then Kurt Bittner, and finally Bruce Macisaac contributed to the analysis and design chapter. Maria Ericsson developed the business engineering and requirements management aspect with Leslee Probasco. The test part was started by Bruce Katz and then completely redesigned by Paul Szymkowiak. John Smith expanded the project management aspects for RUP 2000. Jas Madhur contributed the ideas on configuration management, change management, and deployment. Hakan Dyrhage contributed many ideas to the organization and structure of the process and to its implementation and configuration. Margaret Chan was responsible for the product integration and for the assembly of most of the artwork in this book with Susan Buie. Sigurd Hopen developed the PEP with the help of Bjoern Gustafsson. Per Kroll is the manager of the development group, Mike Barnard the product manager. Alfredo Bencomo, Chinh Vo, Philip Denno, Lars Jenzer, Glenys Macisaac, and Fionna Chong developed the product infrastructure. And Debbie Gray is the devoted administrative assistant of a team spread across nine time zones. The Rational Unified Process and this book benefited over the past 8 years from the reviews and ideas of Stefan Ahlqvist, Dave Bernstein, Grady Booch, Murray Cantor, Geoff Clemm, Catherine Connor, Mike Devlin, Christian Ehrenborg, Ian Gavin, Christina Gisselberg, Sam Guckenheimer, Bjoern Gustafsson, Matt Herdon, Ivar Jacobson, Paer Jansson, Ron Krubek, Dean Leffingwell, Andrew Lyons, Bruce Malasky, Roger Oberg, Gary Pollice, Terri Quatrani, Walker Royce, Jim Rumbaugh, Ian Spence, John Smith, and Brian White. We are very grateful to Grady Booch for writing Chapter 1. Special thanks go to the Rational field, members of our Chat_RUP list, and our users, members of the RUP_Forum, for their feedback, and contributions. And finally many thanks to our editor Mary O'Brien, our former editor J. Carter Shanklin, as well as Brenda Mulligan, Amy Fleischer and her team, and all the staff at Addison-Wesley for getting this book out as quickly and smoothly as they did. Philippe KruchtenVancouver, B.C., Canada 0321197704P11172003

Table of Contents

(NOTE: Each chapter concludes with a summary.)

Preface.

I. THE PROCESS.

1. Software Development Best Practices.

The Value of Software.

Symptoms and Root Causes of Software Development Problems.

Software Best Practices.

Develop Software Iteratively.

Manage Requirements.

Use Component-Based Architectures.

Visually Model Software.

Continuously Verify Software Quality.

Control Changes to Software.

The Rational Unified Process.

2. The Rational Unified Process.

What Is the Rational Unified Process?

The Rational Unified Process as a Product.

Software Best Practices in the Rational Unified Process.

Other Key Features of the Rational Unified Process.

A Brief History of the Rational Unified Process.

3. Static Structure: Process Description.

A Model of the Rational Unified Process.

Roles.

Activities.

Artifacts.

Disciplines.

Workflows.

Additional Process Elements.

A Process Framework.

4. Dynamic Structure: Iterative Development.

The Sequential Process.

Overcoming Difficulties: Iterate!

Gaining Control: Phases and Milestones.

A Shifting Focus across the Cycle.

Phases Revisited.

Benefits of an Iterative Approach.

5. An Architecture-Centric Process.

The Importance of Models.

Architecture.

The Importance of Architecture.

A Definition of Architecture.

Architecture Representation.

An Architecture-Centric Process.

The Purpose of Architecture.

Component-Based Development.

Other Architectural Concepts.

6. A Use-Case-Driven Process.

Definitions.

Identifying Use Cases.

Evolving Use Cases.

Organizing Use Cases.

Use Cases in the Process.

II. PROCESS DISCIPLINES.

7. The Project Management Discipline.

Purpose.

Planning an Iterative Project.

The Concept of Risk.

The Concept of Measurement.

Roles and Artifacts.

Workflow.

Building an Iteration Plan.

8. The Business Modeling Discipline.

Purpose.

Why Business Modeling?

Using Software Engineering Techniques for Business Modeling.

Business Modeling Scenarios.

Roles and Artifacts.

Workflow.

From the Business Models to the Systems.

Modeling the Software Development Business.

Tool Support.

9. The Requirements Discipline.

Purpose.

What Is a Requirement?

Types of Requirements.

Capturing and Managing Requirements.

Requirements Workflow.

Roles in Requirements.

Artifacts Used in Requirements.

Tool Support.

10. The Analysis and Design Discipline.

Purpose.

Analysis versus Design.

How Far Must Design Go?

Roles and Artifacts.

Designing a User-Centered Interface.

The Design Model.

The Analysis Model.

The Role of Interfaces.

Artifacts for Real-Time Systems.

Component-Based Design.

Workflow.

Tool Support.

11. The Implementation Discipline.

Purpose.

Builds.

Integration.

Prototypes.

Roles and Artifacts.

Workflow.

Tool Support.

12. The Test Discipline.

Purpose.

Testing in the Iterative Lifecycle.

Dimensions of Testing.

Roles and Artifacts.

Workflow.

Tool Support.

13. The Configuration and Change Management Discipline.

Purpose.

The CCM Cube.

Roles and Artifacts.

Workflow.

Tool Support.

14. The Environment Discipline.

Purpose.

Process Engineering Process.

Roles and Artifacts.

Workflow.

Tool Support.

15. The Deployment Discipline.

Purpose.

Roles and Artifacts.

Workflow.

16. Typical Iteration Plans.

Defining the Product Vision and the Business Case.

Building an Architectural Prototype.

Implementing the System.

17. Implementing the Rational Unified Process.

Introduction.

The Effect of Implementing a Process.

Implementing the Rational Unified Process Step by Step.

Implementing a Process Is a Project.

Appendix A: Summary of Roles.

Appendix B: Summary of Artifacts.

Appendix C: Acronyms.

Glossary.

Bibliography.

Index. 0321197704T11172003