The Rational Unified Process An Introduction

by Kruchten, Philippe

• ISBN13: 9780321197702
• ISBN10: 0321197704
• Edition: 3rd
• Format: Paperback
• Copyright: 2003-12-10
• Publisher: Addison-Wesley Professional

Summary

bull; Reflects all of the changes that were integrated into RUP v2003-the latest version of the very popular produc t bull; Learn the key concepts, fundamentals of structure, integral content, and motivation behind the RUP bull; Covers all phases of the software development lifecycle -from concept, to delivery, to revision

Author Biography

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.

0321197704AB11072003

Table of Contents

Preface	p. xiii
Goals of This Book	p. xiii
Who Should Read This Book?	p. xiv
How to Use This Book	p. xv
Organization and Special Features	p. xv
For More Information	p. xvi
Second Edition	p. xvi
Acknowledgments	p. xvii
The Process	p. 1
Software Development Best Practices	p. 3
The Value of Software	p. 3
Symptoms and Root Causes of Software Development Problems	p. 4
Software Best Practices	p. 5
Develop Software Iteratively	p. 6
Manage Requirements	p. 8
Use Component-Based Architectures	p. 9
Visually Model Software	p. 11
Continuously Verify Software Quality	p. 12
Control Changes to Software	p. 14
The Rational Unified Process	p. 15
Summary	p. 16
The Rational Unified Process	p. 17
What Is the Rational Unified Process?	p. 17
The Rational Unified Process as a Product	p. 18
Process Structure: Two Dimensions	p. 22
Software Best Practices in the Rational Unified Process	p. 23
Other Key Features of the Rational Unified Process	p. 30
A Brief History of the Rational Unified Process	p. 32
Summary	p. 34
Static Structure: Process Description	p. 35
A Model of the Rational Unified Process	p. 35
Workers	p. 36
Activities	p. 38
Artifacts	p. 40
Workflows	p. 43
Additional Process Elements	p. 47
A Process Framework	p. 50
Summary	p. 51
Dynamic Structure: Iterative Development	p. 53
The Sequential Process	p. 53
Overcoming Difficulties: Iterate!	p. 60
Gaining Control: Phases and Milestones	p. 61
A Shifting Focus across the Cycle	p. 64
Phases Revisited	p. 66
Benefits of an Iterative Approach	p. 76
Summary	p. 78
An Architecture-centric Process	p. 81
The Importance of Models	p. 81
Architecture	p. 82
The Importance of Architecture	p. 82
A Definition of Architecture	p. 84
Architecture Representation	p. 85
An Architecture-centric Process	p. 90
The Purpose of Architecture	p. 92
Component-Based Development	p. 93
Other Architectural Concepts	p. 94
Summary	p. 96
A Use-Case-Driven Process	p. 97
Definitions	p. 97
Identifying Use Cases	p. 103
Evolving Use Cases	p. 104
Organizing Use Cases	p. 105
Use Cases in the Process	p. 107
Summary	p. 109
Process Workflows	p. 111
The Project Management Workflow	p. 113
Purpose	p. 113
Planning an Iterative Project	p. 114
The Concept of Risk	p. 117
The Concept of Metrics	p. 119
What Is a Metric?	p. 121
Workers and Artifacts	p. 122
Workflow	p. 123
Building an Interation Plan	p. 132
Summary	p. 138
The Business Modeling Workflow	p. 139
Purpose	p. 139
Why Business Modeling?	p. 140
Using Software Modeling Techniques for Business Modeling	p. 141
Business Modeling Scenarios	p. 143
Workers and Artifacts	p. 144
Workflow	p. 146
From the Business Models to the Systems	p. 148
Modeling the Software Development Business	p. 153
Tool Support	p. 153
Summary	p. 154
The Requirements Workflow	p. 155
Purpose	p. 155
What Is a Requirement?	p. 156
Types of Requirements	p. 158
Capturing and Managing Requirements	p. 161
Designing a User-Centered Interface	p. 162
Requirements Workflow	p. 163
Workers in Requirements	p. 165
Artifacts Used in Requirements	p. 167
Tool Support	p. 169
Summary	p. 169
The Analysis and Design Workflow	p. 171
Purpose	p. 171
Analysis versus Design	p. 171
How Far Must Design Go?	p. 172
Workers and Artifacts	p. 173
The Design Model	p. 174
The Analysis Model	p. 175
The Role of Interfaces	p. 175
Artifacts for Real-Time Systems	p. 176
Component-Based Design	p. 176
Workflow	p. 177
Tool Support	p. 181
Summary	p. 181
The Implementation Workflow	p. 183
Purpose	p. 183
Builds	p. 184
Integration	p. 184
Prototypes	p. 185
Workers and Artifacts	p. 188
Workflow	p. 189
Tool Support	p. 192
Summary	p. 192
The Test Workflow	p. 193
Purpose	p. 193
Quality	p. 194
Testing in the Iterative Lifecycle	p. 194
Dimensions of Testing	p. 195
The Test Model	p. 198
Workers and Artifacts	p. 199
Workflow	p. 202
Tool Support	p. 205
Summary	p. 206
The Configuration and Change Management Workflow	p. 207
Purpose	p. 207
The CCM Cube	p. 208
Workers and Artifacts	p. 213
Workflow	p. 215
Tool Support	p. 218
Summary	p. 219
The Environment Workflow	p. 221
Purpose	p. 221
Workers and Artifacts	p. 222
Workflow	p. 223
Summary	p. 225
The Deployment Workflow	p. 227
Purpose	p. 227
Workers and Artifacts	p. 229
Workflow	p. 232
Summary	p. 235
Typical Iteration Plans	p. 237
Purpose	p. 237
Defining the Product Vision and the Business Case	p. 238
Building an Architectural Prototype	p. 240
Implementing the System	p. 244
Summary	p. 247
Configuring and Implementing the Rational Unified Process	p. 249
Introduction	p. 249
The Effect of Implementing a Process	p. 250
Implementing the Rational Unified Process Step by Step	p. 252
Configuring the Process	p. 258
Implementing a Process Is a Project	p. 260
Summary	p. 262
Summary of Workers	p. 263
Summary of Artifacts	p. 267
Acronyms	p. 271
Glossary	p. 273
Bibliography	p. 279
Index	p. 287
Table of Contents provided by Syndetics. All Rights Reserved.

Excerpts

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 Processthe online knowledge baseis 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) andThe 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 bookSoftware 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 textbookThe 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 professi