Rational Unified Process, The: An Introduction

by Kruchten, Philippe

• ISBN13: 9780201707106
• ISBN10: 0201707101
• Edition: 2nd
• Format: Paperback
• Copyright: 2000-01-01
• Publisher: Addison-Wesley Professional

Summary

This book is the fastest way to get up- and-running with Rational Unified Process 2000 -- the industry's most powerful tool for incorporating best practices into software development. Authored by RUP's Lead Architect, it reflects all the major improvements made in the newest version of RUP, including its improved support for business engineering, management of non-functional requirements, and deployment of multi-tier distributed applications. Discover how RUP 2000 can enable development teams to maximize software quality -- within predictable schedules and reasonable budgets. Understand what RUP 2000 is, how it evolved, and how it fits into the development process. Next, review the structure of RUP 2000, mastering its use throughout the entire project lifecycle. This edition includes substantial new coverage of application interface design (including Web applications); patterns and frameworks; real-time and reactive systems; lifecycle testing, and more. There are new process roadmaps that demonstrate RUP 2000 at work with many projects and technologies; as well as expanded checklists and guidelines for process artifacts, activities, and phases.

Table of Contents

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