| Foreword by Mary Barmeyer O'Brien | 
 | 
vii |  | 
| Preface to the 1902 Edition | 
 | 
xviii |  | 
| We Start | 
 | 
1 | (1) | 
| Our First Camp | 
 | 
2 | (2) | 
| Through Memphis | 
 | 
4 | (1) | 
| I Meet an Acquaintance | 
 | 
4 | (2) | 
| An Addition to Our Party | 
 | 
6 | (2) | 
| Bloomfield, Iowa | 
 | 
8 | (1) | 
| Beautiful Apples | 
 | 
9 | (2) | 
| Miss Milburn's Love Story | 
 | 
11 | (2) | 
| A Letter to Brother Mac | 
 | 
13 | (2) | 
| The Icarian Community | 
 | 
15 | (1) | 
| A Swing among the Trees | 
 | 
16 | (2) | 
| A Fatal Accident | 
 | 
18 | (1) | 
| Bereavement | 
 | 
19 | (2) | 
| A Funeral | 
 | 
21 | (2) | 
| On the Banks of the Big Muddy | 
 | 
23 | (1) | 
| Our Last Day with Miss Milburn | 
 | 
24 | (1) | 
| We Have Our Pictures Taken | 
 | 
25 | (2) | 
| A Yankee Homestead | 
 | 
27 | (2) | 
| We Meet a Friend | 
 | 
29 | (1) | 
| On the Banks of the Platte | 
 | 
30 | (2) | 
| The Order of Our Going | 
 | 
32 | (2) | 
| Fort Kearney | 
 | 
34 | (1) | 
| Eleven Graves | 
 | 
35 | (1) | 
| A Narrow Escape | 
 | 
36 | (2) | 
| Beaux | 
 | 
38 | (2) | 
| We Decide to Go to Montana | 
 | 
40 | (2) | 
| Prairie Dogs | 
 | 
42 | (2) | 
| Preaching Services | 
 | 
44 | (1) | 
| Music in Camp | 
 | 
45 | (3) | 
| The Mountains in Sight | 
 | 
48 | (2) | 
| A Town of Tents and Wagons | 
 | 
50 | (1) | 
| We Worship in the Wilderness | 
 | 
51 | (2) | 
| We Celebrate the Fourth | 
 | 
53 | (1) | 
| The Black Hills | 
 | 
54 | (1) | 
| We Visit a Beautiful Spring | 
 | 
55 | (2) | 
| We Cut Our Names in Stone | 
 | 
57 | (2) | 
| Laramie Plains | 
 | 
59 | (1) | 
| In the Rain | 
 | 
60 | (2) | 
| Indians | 
 | 
62 | (2) | 
| We Climb Elk Mountain | 
 | 
64 | (1) | 
| We Cross the North Platte | 
 | 
65 | (2) | 
| Neelie Is Sick | 
 | 
67 | (1) | 
| The Summit of the Rocky Mountains | 
 | 
68 | (2) | 
| Sim Buford Sick | 
 | 
70 | (1) | 
| Our Train Divided | 
 | 
71 | (2) | 
| We Overtake the California Train | 
 | 
73 | (2) | 
| On Bitter Creek | 
 | 
75 | (2) | 
| Delayed Another Day | 
 | 
77 | (1) | 
| A Fatal Shooting | 
 | 
78 | (2) | 
| Tried for Murder | 
 | 
80 | (2) | 
| We Leave the Train | 
 | 
82 | (2) | 
| Wild Currants Galore | 
 | 
84 | (2) | 
| Mr. Curry's Horses Stolen | 
 | 
86 | (1) | 
| Anxiously Waiting at Ham's Fork | 
 | 
87 | (2) | 
| The Wanderers' Return | 
 | 
89 | (1) | 
| Sim's Story of Their Wanderings | 
 | 
90 | (2) | 
| Bear River Mountain | 
 | 
92 | (2) | 
| We Meet Captain Hardinbrooke's Brother | 
 | 
94 | (2) | 
| Mormon Towns in Idaho | 
 | 
96 | (2) | 
| We Meet Men Returning to the States | 
 | 
98 | (1) | 
| Mother and I Save Joe's Life | 
 | 
99 | (2) | 
| Dick Is Sold. Oh, Dear | 
 | 
101 | (2) | 
| Mother's Birthday | 
 | 
103 | (1) | 
| Sweet Water Cañon | 
 | 
104 | (2) | 
| The End of Our Journey | 
 | 
106 | (1) | 
| The End of Our Journey | 
 | 
106 |  | 
| 0321166094 | 
 | 
| Figures | 
 | 
xxi |  | 
| Tables | 
 | 
xxv |  | 
| Foreword | 
 | 
xxvii |  | 
| Preface | 
 | 
xxix |  | 
| 
 | 
 | 
 | 
INTRODUCING THE RATIONAL UNIFIED PROCESS | 
 
 
 | 
 | 
1 | (84) | 
 | 
Chapter 1 Introducing the Rational Unified Process | 
 
 
 | 
 | 
3 | (24) | 
 | 
What Is the Rational Unified Process? | 
 
 
 | 
 | 
3 | (1) | 
| 
 | 
 | 
4 | (1) | 
 | 
Underlying Principles of the RUP Approach | 
 
 
 | 
 | 
4 | (1) | 
 | 
The RUP and Iterative Development | 
 
 
 | 
 | 
6 | (3) | 
 | 
The RUP-A Well-Defined Software Engineering Process | 
 
 
 | 
 | 
9 | (1) | 
 | 
The Dynamic Structure of the Rational Unified Process | 
 
 
 | 
 | 
10 | (1) | 
 | 
The Static Structure of the Rational Unified Process | 
 
 
 | 
 | 
13 | (6) | 
 | 
The RUP-A Customizable Process Product | 
 
 
 | 
 | 
19 | (1) | 
 | 
Configuration and Process Authoring Tools | 
 
 
 | 
 | 
20 | (1) | 
| 
 | 
 | 
22 | (1) | 
 | 
Who Uses the RUP Product? | 
 
 
 | 
 | 
24 | (2) | 
| 
 | 
 | 
26 | (1) | 
 | 
Chapter 2 The Spirit of the RUP: Guidelines for Success | 
 
 
 | 
 | 
27 | (22) | 
 | 
Attack Major Risks Early and Continuously, or They Will Attack You | 
 
 
 | 
 | 
28 | (1) | 
| 
 | 
 | 
31 | (1) | 
 | 
Ensure That You Deliver Value to Your Customer | 
 
 
 | 
 | 
31 | (1) | 
| 
 | 
 | 
32 | (1) | 
 | 
Stay Focused on Executable Software | 
 
 
 | 
 | 
33 | (1) | 
| 
 | 
 | 
34 | (1) | 
 | 
Accommodate Change Early in the Project | 
 
 
 | 
 | 
35 | (1) | 
| 
 | 
 | 
38 | (1) | 
 | 
Baseline an Executable Architecture Early On | 
 
 
 | 
 | 
38 | (1) | 
| 
 | 
 | 
40 | (1) | 
 | 
Build Your System with Components | 
 
 
 | 
 | 
40 | (1) | 
| 
 | 
 | 
42 | (1) | 
 | 
Work Together as One Team | 
 
 
 | 
 | 
43 | (1) | 
| 
 | 
 | 
45 | (1) | 
 | 
Make Quality a Way of Life, Not an Afterthought | 
 
 
 | 
 | 
46 | (1) | 
| 
 | 
 | 
47 | (1) | 
| 
 | 
 | 
48 | (1) | 
 | 
Chapter 3 Comparing Processes: The RUP, Agile Methods, and Heavyweight Government Standards | 
 
 
 | 
 | 
49 | (18) | 
 | 
How Can We Compare Processes? | 
 
 
 | 
 | 
50 | (1) | 
 | 
Agile Development: Low-Ceremony, Iterative Approaches | 
 
 
 | 
 | 
50 | (3) | 
 | 
SEI CMM, SEI CMMI, ISO/IEC, DOD-STD, MIL-STD: High Ceremony Striving for Higher Predictability | 
 
 
 | 
 | 
53 | (1) | 
 | 
SEI CMM: Process Assessment Framework | 
 
 
 | 
 | 
54 | (1) | 
 | 
SEI CMMI: Process Assessment Framework | 
 
 
 | 
 | 
55 | (1) | 
 | 
ISO/IEC 15504: Process Assessment Framework | 
 
 
 | 
 | 
55 | (1) | 
 | 
DOD-STD and MIL-STD: High-Ceremony Processes | 
 
 
 | 
 | 
56 | (2) | 
 | 
The RUP: An Iterative Approach with an Adaptable | 
 
 
 | 
 | 
| 
 | 
 | 
58 | (1) | 
 | 
How Iterative Do You Want to Be? | 
 
 
 | 
 | 
59 | (1) | 
 | 
How Much Ceremony Do You Want? | 
 
 
 | 
 | 
60 | (1) | 
 | 
What Kind of RUP Configuration Meets Your Process Needs? | 
 
 
 | 
 | 
61 | (1) | 
 | 
Project Deimos: Team of One | 
 
 
 | 
 | 
61 | (1) | 
 | 
Project Ganymede: Small Project with Tight Timeline | 
 
 
 | 
 | 
61 | (1) | 
 | 
Project Mars: Average-Size Project without Iterative Development Experience | 
 
 
 | 
 | 
62 | (1) | 
 | 
Project Jupiter: Large Distributed Project | 
 
 
 | 
 | 
62 | (2) | 
| 
 | 
 | 
64 | (3) | 
 | 
Chapter 4 The RUP for a Team of One: Project Deimos | 
 
 
 | 
 | 
67 | (18) | 
 | 
A Solo Software Project: Project Deimos | 
 
 
 | 
 | 
68 | (1) | 
 | 
The Seminal Idea (Saturday Night) | 
 
 
 | 
 | 
68 | (1) | 
 | 
The Proposal (Monday Morning) | 
 
 
 | 
 | 
69 | (1) | 
| 
 | 
 | 
69 | (1) | 
| 
 | 
 | 
71 | (1) | 
| 
 | 
 | 
73 | (1) | 
| 
 | 
 | 
73 | (1) | 
| 
 | 
 | 
74 | (1) | 
 | 
The Commitment (Monday Lunch) | 
 
 
 | 
 | 
75 | (1) | 
| 
 | 
 | 
75 | (1) | 
| 
 | 
 | 
75 | (1) | 
| 
 | 
 | 
76 | (1) | 
 | 
The Business Case, Take Two | 
 
 
 | 
 | 
76 | (1) | 
 | 
Digging In (Later Monday) | 
 
 
 | 
 | 
77 | (1) | 
| 
 | 
 | 
78 | (2) | 
 | 
More Progress, More Changes (Wednesday) | 
 
 
 | 
 | 
80 | (1) | 
 | 
Nearing Completion (Thursday) | 
 
 
 | 
 | 
80 | (1) | 
| 
 | 
 | 
81 | (1) | 
| 
 | 
 | 
81 | (4) | 
| 
 | 
 | 
 | 
THE LIFECYCLE OF A RATIONAL UNIFIED PROCESS PROJECT | 
 
 
 | 
 | 
85 | (92) | 
 | 
Chapter 5 Going Through the Four Phases | 
 
 
 | 
 | 
87 | (6) | 
| 
 | 
 | 
87 | (1) | 
| 
 | 
 | 
88 | (1) | 
| 
 | 
 | 
89 | (1) | 
| 
 | 
 | 
90 | (2) | 
| 
 | 
 | 
92 | (1) | 
 | 
Chapter 6 The Inception Phase | 
 
 
 | 
 | 
93 | (20) | 
 | 
Objectives of the Inception Phase | 
 
 
 | 
 | 
94 | (1) | 
| 
 | 
 | 
95 | (1) | 
 | 
Objective 1: Understand What to Build | 
 
 
 | 
 | 
96 | (1) | 
 | 
Produce a Vision Document | 
 
 
 | 
 | 
97 | (1) | 
 | 
Generate a "Mile-Wide, Inch-Deep" Description | 
 
 
 | 
 | 
98 | (1) | 
 | 
Hold a Workshop or Brainstorming Session | 
 
 
 | 
 | 
98 | (1) | 
 | 
Detail Key Actors and Use Cases | 
 
 
 | 
 | 
101 | (1) | 
 | 
Objective 2: Identify Key System Functionality | 
 
 
 | 
 | 
102 | (3) | 
 | 
Objective 3: Determine at Least One Possible Solution | 
 
 
 | 
 | 
105 | (2) | 
 | 
Objective 4: Understand the Costs, Schedule, and Risks Associated with the Project | 
 
 
 | 
 | 
107 | (1) | 
 | 
Objective 5: Decide What Process to Follow and What Tools to Use | 
 
 
 | 
 | 
108 | (2) | 
 | 
Project Review: Lifecycle Objective Milestone | 
 
 
 | 
 | 
110 | (1) | 
| 
 | 
 | 
111 | (2) | 
 | 
Chapter 7 The Elaboration Phase | 
 
 
 | 
 | 
113 | (26) | 
 | 
Objectives of the Elaboration Phase | 
 
 
 | 
 | 
114 | (2) | 
 | 
Elaboration and Iterations | 
 
 
 | 
 | 
116 | (1) | 
 | 
First Iteration in Elaboration | 
 
 
 | 
 | 
117 | (1) | 
 | 
Second Iteration in Elaboration | 
 
 
 | 
 | 
117 | (1) | 
 | 
Objective 1: Get a More Detailed Understanding of the Requirements | 
 
 
 | 
 | 
118 | (2) | 
 | 
Objective 2: Design, Implement, Validate, and Baseline the Architecture | 
 
 
 | 
 | 
120 | (1) | 
 | 
Architecture: Defining Subsystems, Key Components, and Their Interfaces | 
 
 
 | 
 | 
122 | (1) | 
 | 
Use Architecturally Significant Use Cases to Drive the Architecture | 
 
 
 | 
 | 
123 | (1) | 
 | 
Design Critical Use Cases | 
 
 
 | 
 | 
125 | (1) | 
 | 
Consolidate and Package Identified Classes | 
 
 
 | 
 | 
127 | (1) | 
 | 
Ensure Architectural Coverage | 
 
 
 | 
 | 
128 | (1) | 
| 
 | 
 | 
129 | (1) | 
 | 
Outline Concurrency, Processes, Threads, and Physical Distribution | 
 
 
 | 
 | 
130 | (1) | 
 | 
Identify Architectural Mechanisms | 
 
 
 | 
 | 
130 | (1) | 
 | 
Implement Critical Scenarios | 
 
 
 | 
 | 
131 | (1) | 
| 
 | 
 | 
131 | (1) | 
| 
 | 
 | 
132 | (1) | 
| 
 | 
 | 
133 | (1) | 
 | 
Objective 3: Mitigate Essential Risks, and Produce Accurate Schedule and Cost Estimates | 
 
 
 | 
 | 
134 | (1) | 
 | 
Plan the Project and Estimate Costs | 
 
 
 | 
 | 
134 | (2) | 
 | 
Objective 4: Refine the Development Case, and Put the Development Environment in Place | 
 
 
 | 
 | 
136 | (1) | 
 | 
Project Review: Lifecycle Architecture Milestone | 
 
 
 | 
 | 
137 | (1) | 
| 
 | 
 | 
138 | (1) | 
 | 
Chapter 8 The Construction Phase | 
 
 
 | 
 | 
139 | (22) | 
 | 
Objectives of the Construction Phase | 
 
 
 | 
 | 
141 | (1) | 
 | 
Construction and Its Iterations | 
 
 
 | 
 | 
142 | (3) | 
 | 
Objective 1: Minimize Development Costs and Achieve Some Degree of Parallelism | 
 
 
 | 
 | 
145 | (1) | 
 | 
Organize Around Architecture | 
 
 
 | 
 | 
145 | (1) | 
| 
 | 
 | 
147 | (1) | 
| 
 | 
 | 
148 | (1) | 
 | 
Ensure Continual Progress | 
 
 
 | 
 | 
150 | (1) | 
 | 
Objective 2: Iteratively Develop a Complete Product That Is Ready to Transition to Its User Community | 
 
 
 | 
 | 
151 | (1) | 
 | 
Describe the Remaining Use Cases and Other Requirements | 
 
 
 | 
 | 
151 | (1) | 
| 
 | 
 | 
152 | (1) | 
| 
 | 
 | 
153 | (1) | 
 | 
Implement and Unit-Test Code | 
 
 
 | 
 | 
153 | (1) | 
 | 
Do Integration and System Testing | 
 
 
 | 
 | 
154 | (1) | 
 | 
Early Deployments and Feedback Loops | 
 
 
 | 
 | 
155 | (1) | 
 | 
Prepare for Beta Deployment | 
 
 
 | 
 | 
157 | (1) | 
 | 
Prepare for Final Deployment | 
 
 
 | 
 | 
157 | (2) | 
 | 
Project Review: Initial Operational Capability Milestone | 
 
 
 | 
 | 
159 | (1) | 
| 
 | 
 | 
159 | (2) | 
 | 
Chapter 9 The Transition Phase | 
 
 
 | 
 | 
161 | (16) | 
 | 
Objectives of the Transition Phase | 
 
 
 | 
 | 
162 | (1) | 
 | 
Transition Iterations and Development Cycles | 
 
 
 | 
 | 
163 | (1) | 
 | 
Transition and Iterations | 
 
 
 | 
 | 
163 | (1) | 
 | 
Transition and Development Cycles | 
 
 
 | 
 | 
165 | (2) | 
 | 
Objective 1: Beta Test to Validate That User Expectations Are Met | 
 
 
 | 
 | 
167 | (1) | 
 | 
Capturing, Analyzing, and Implementing Change Requests | 
 
 
 | 
 | 
167 | (1) | 
| 
 | 
 | 
168 | (1) | 
 | 
Patch Releases and Additional Beta Releases | 
 
 
 | 
 | 
169 | (1) | 
 | 
Metrics for Understanding When Transition Will Be Complete | 
 
 
 | 
 | 
169 | (2) | 
 | 
Objective 2: Train Users and Maintainers to Achieve User Self-Reliability | 
 
 
 | 
 | 
171 | (1) | 
 | 
Objective 3: Prepare Deployment Site and Convert Operational Databases | 
 
 
 | 
 | 
172 | (1) | 
 | 
Objective 4: Prepare for Launch: Packaging, Production, and Marketing Rollout | 
 
 
 | 
 | 
172 | (1) | 
 | 
Packaging, Bill of Materials, and Production | 
 
 
 | 
 | 
172 | (1) | 
| 
 | 
 | 
173 | (1) | 
 | 
Objective 5: Achieve Stakeholder Concurrence That Deployment Is Complete | 
 
 
 | 
 | 
173 | (1) | 
| 
 | 
 | 
173 | (2) | 
 | 
Objective 6: Improve Future Project Performance Through Lessons Learned | 
 
 
 | 
 | 
175 | (1) | 
 | 
Project Review: Product Release Milestone | 
 
 
 | 
 | 
175 | (1) | 
| 
 | 
 | 
176 | (1) | 
| 
 | 
 | 
 | 
ADOPTING THE RATIONAL UNIFIED PROCESS | 
 
 
 | 
 | 
177 | (94) | 
 | 
Chapter 10 Configuring, Instantiating, and Customizing the Rational Unified Process | 
 
 
 | 
 | 
179 | (18) | 
| 
 | 
 | 
180 | (1) | 
 | 
Producing a RUP Process Configuration | 
 
 
 | 
 | 
180 | (1) | 
| 
 | 
 | 
182 | (1) | 
 | 
Customizing RUP Templates | 
 
 
 | 
 | 
184 | (1) | 
 | 
Instantiating the RUP in a Project | 
 
 
 | 
 | 
184 | (1) | 
| 
 | 
 | 
184 | (1) | 
| 
 | 
 | 
187 | (1) | 
 | 
Alternatives to Producing a Development Case | 
 
 
 | 
 | 
189 | (1) | 
| 
 | 
 | 
189 | (1) | 
 | 
Rational Process Workbench and Process Engineering Process | 
 
 
 | 
 | 
190 | (1) | 
 | 
Creating Thin RUP Plug-Ins Using RUP Organizer | 
 
 
 | 
 | 
191 | (1) | 
 | 
Creating Structural RUP Plug-his Using RUP Modeler and RUP Organizer | 
 
 
 | 
 | 
192 | (4) | 
| 
 | 
 | 
196 | (1) | 
 | 
Chapter 11 Adopting the Rational Unified Process | 
 
 
 | 
 | 
197 | (26) | 
 | 
Adopting the RUP in a Project | 
 
 
 | 
 | 
198 | (1) | 
| 
 | 
 | 
199 | (1) | 
| 
 | 
 | 
200 | (1) | 
| 
 | 
 | 
203 | (1) | 
| 
 | 
 | 
205 | (1) | 
| 
 | 
 | 
206 | (1) | 
 | 
Adopting the RUP in Small Projects | 
 
 
 | 
 | 
207 | (1) | 
 | 
Adopting the RUP in a Large Organization | 
 
 
 | 
 | 
208 | (1) | 
 | 
Process and Tool Enhancement Projects (PTEP) | 
 
 
 | 
 | 
210 | (1) | 
| 
 | 
 | 
213 | (1) | 
 | 
Software Development Projects | 
 
 
 | 
 | 
214 | (1) | 
 | 
A Typical Program for Moderate Change | 
 
 
 | 
 | 
215 | (2) | 
 | 
A Typical Program for Major Change | 
 
 
 | 
 | 
217 | (2) | 
 | 
An Aggressive Program for Major Change | 
 
 
 | 
 | 
219 | (3) | 
| 
 | 
 | 
222 | (1) | 
 | 
Chapter 12 Planning an Iterative Project | 
 
 
 | 
 | 
223 | (20) | 
| 
 | 
 | 
223 | (1) | 
| 
 | 
 | 
224 | (1) | 
| 
 | 
 | 
224 | (1) | 
| 
 | 
 | 
224 | (1) | 
| 
 | 
 | 
225 | (1) | 
| 
 | 
 | 
225 | (1) | 
| 
 | 
 | 
225 | (1) | 
 | 
Coarse-Grain and Fine-Grain Plans: Project Plans and Iteration Plans | 
 
 
 | 
 | 
226 | (1) | 
| 
 | 
 | 
226 | (1) | 
| 
 | 
 | 
227 | (1) | 
| 
 | 
 | 
228 | (1) | 
 | 
Determining the Number of Iterations | 
 
 
 | 
 | 
232 | (1) | 
| 
 | 
 | 
234 | (1) | 
| 
 | 
 | 
235 | (1) | 
| 
 | 
 | 
236 | (1) | 
 | 
Inception and Elaboration | 
 
 
 | 
 | 
237 | (1) | 
 | 
Construction and Transition | 
 
 
 | 
 | 
237 | (1) | 
| 
 | 
 | 
238 | (1) | 
| 
 | 
 | 
239 | (1) | 
 | 
An Iterative Estimation Technique: Wideband Modified Delphi | 
 
 
 | 
 | 
240 | (1) | 
 | 
Optimizing the Project Plan | 
 
 
 | 
 | 
241 | (1) | 
| 
 | 
 | 
241 | (1) | 
| 
 | 
 | 
242 | (1) | 
| 
 | 
 | 
242 | (1) | 
 | 
Chapter 13 Common Mistakes When Adopting and Using the RUP ... and How to Avoid Them | 
 
 
 | 
 | 
243 | (28) | 
 | 
Mistakes When Adopting the RUP | 
 
 
 | 
 | 
243 | (1) | 
 | 
Adopting Too Much of What Is in the RUP | 
 
 
 | 
 | 
244 | (1) | 
 | 
Adopting Everything at Once, Rather Than Incrementally | 
 
 
 | 
 | 
246 | (1) | 
 | 
Not Planning the Implementation of the RUP | 
 
 
 | 
 | 
249 | (1) | 
 | 
Not Coupling Process Improvement with Business Results | 
 
 
 | 
 | 
250 | (1) | 
 | 
Customizing Too Much of the RUP Too Early | 
 
 
 | 
 | 
251 | (1) | 
 | 
Paying Lip Service to the RUP | 
 
 
 | 
 | 
251 | (2) | 
 | 
Mistakes When Managing Iterative Development | 
 
 
 | 
 | 
253 | (1) | 
 | 
Having a Functional, Specialized Organization | 
 
 
 | 
 | 
253 | (1) | 
 | 
Not Setting the Right Stakeholder Expectations or Using an Old-Fashioned Acquisition Model | 
 
 
 | 
 | 
254 | (1) | 
 | 
Too Many Developers at Project Start | 
 
 
 | 
 | 
255 | (1) | 
 | 
Solving the Easy Stuff First | 
 
 
 | 
 | 
257 | (1) | 
 | 
Having an Extended Initial Iteration | 
 
 
 | 
 | 
258 | (1) | 
 | 
Having Overlapping Iterations | 
 
 
 | 
 | 
259 | (1) | 
 | 
Allowing Too Many Changes Late in the Project | 
 
 
 | 
 | 
260 | (1) | 
 | 
Mistakes in Analysis, Architecture, Design, Implementation, and Testing | 
 
 
 | 
 | 
261 | (1) | 
 | 
Creating Too Many Use Cases | 
 
 
 | 
 | 
262 | (1) | 
 | 
Having Analysis-Paralysis | 
 
 
 | 
 | 
264 | (1) | 
 | 
Including Design Decisions in Your Requirements | 
 
 
 | 
 | 
264 | (1) | 
 | 
Not Having Stakeholder Buy-In on Requirements | 
 
 
 | 
 | 
265 | (1) | 
 | 
"Not Invented Here" Mentality | 
 
 
 | 
 | 
265 | (1) | 
 | 
Ending Elaboration Before the Architecture Is Sufficiently Stable | 
 
 
 | 
 | 
267 | (1) | 
 | 
Focusing on Inspections Instead of Assessing Executable Software | 
 
 
 | 
 | 
269 | (1) | 
| 
 | 
 | 
270 | (1) | 
| 
 | 
 | 
 | 
A ROLE-BASED GUIDE TO THE RATIONAL UNIFIED PROCESS | 
 
 
 | 
 | 
271 | (112) | 
 | 
Chapter 14 A Project Manager's Guide to the RUP | 
 
 
 | 
 | 
273 | (14) | 
 | 
The Mission of a Project Manager | 
 
 
 | 
 | 
273 | (1) | 
| 
 | 
 | 
274 | (1) | 
| 
 | 
 | 
275 | (1) | 
| 
 | 
 | 
276 | (1) | 
 | 
Scope of the Project Management Discipline in the RUP | 
 
 
 | 
 | 
277 | (1) | 
 | 
Software Development Plan (SDP) | 
 
 
 | 
 | 
278 | (1) | 
| 
 | 
 | 
279 | (1) | 
| 
 | 
 | 
279 | (1) | 
| 
 | 
 | 
280 | (1) | 
 | 
Activities of a Project Manager | 
 
 
 | 
 | 
280 | (1) | 
| 
 | 
 | 
281 | (1) | 
 | 
Developing the Software Development Plan | 
 
 
 | 
 | 
281 | (1) | 
 | 
Starting and Closing Phases and Iteration | 
 
 
 | 
 | 
281 | (1) | 
| 
 | 
 | 
282 | (1) | 
 | 
Finding Your Way in the RUP | 
 
 
 | 
 | 
282 | (1) | 
| 
 | 
 | 
283 | (2) | 
 | 
Resources for the Project Manager | 
 
 
 | 
 | 
285 | (1) | 
| 
 | 
 | 
285 | (1) | 
| 
 | 
 | 
285 | (1) | 
| 
 | 
 | 
286 | (1) | 
 | 
Chapter 15 An Analyst's Guide to the RUP | 
 
 
 | 
 | 
287 | (24) | 
 | 
Your Mission as an Analyst | 
 
 
 | 
 | 
287 | (2) | 
| 
 | 
 | 
289 | (1) | 
 | 
Understand How Your Business Should Operate | 
 
 
 | 
 | 
289 | (3) | 
 | 
Understand Stakeholder Needs | 
 
 
 | 
 | 
292 | (1) | 
| 
 | 
 | 
293 | (1) | 
| 
 | 
 | 
294 | (1) | 
| 
 | 
 | 
294 | (2) | 
 | 
Develop a Use-Case Model and Glossary | 
 
 
 | 
 | 
296 | (1) | 
 | 
Describe Requirements "Mile-Wide, Inch-Deep" | 
 
 
 | 
 | 
297 | (1) | 
 | 
Detail Actors and Use Cases | 
 
 
 | 
 | 
299 | (3) | 
 | 
Example: Use-Case Specification for Register for Courses | 
 
 
 | 
 | 
302 | (2) | 
| 
 | 
 | 
304 | (1) | 
 | 
Develop User-Interface Prototypes | 
 
 
 | 
 | 
304 | (1) | 
 | 
Develop Use-Case Storyboard or Prototype | 
 
 
 | 
 | 
305 | (1) | 
 | 
Capture Nonfunctional Requirements | 
 
 
 | 
 | 
307 | (1) | 
 | 
Update and Refine Requirements | 
 
 
 | 
 | 
308 | (1) | 
 | 
Ensure That the Requirements Are Delivered and Tested | 
 
 
 | 
 | 
309 | (1) | 
 | 
The Analyst's Role in the Rational Unified Process | 
 
 
 | 
 | 
309 | (1) | 
| 
 | 
 | 
310 | (1) | 
| 
 | 
 | 
310 | (1) | 
| 
 | 
 | 
310 | (1) | 
 | 
Chapter 16 An Architect's Guide to the RUP | 
 
 
 | 
 | 
311 | (22) | 
 | 
The Mission of an Architect | 
 
 
 | 
 | 
311 | (1) | 
| 
 | 
 | 
311 | (1) | 
| 
 | 
 | 
313 | (1) | 
 | 
A Vertex of Communication | 
 
 
 | 
 | 
313 | (1) | 
| 
 | 
 | 
314 | (1) | 
| 
 | 
 | 
315 | (1) | 
| 
 | 
 | 
315 | (1) | 
 | 
Software Architecture Document | 
 
 
 | 
 | 
317 | (1) | 
 | 
Executable Architectural Prototype | 
 
 
 | 
 | 
318 | (1) | 
| 
 | 
 | 
318 | (1) | 
| 
 | 
 | 
318 | (1) | 
| 
 | 
 | 
319 | (1) | 
| 
 | 
 | 
320 | (1) | 
| 
 | 
 | 
320 | (1) | 
| 
 | 
 | 
321 | (1) | 
| 
 | 
 | 
322 | (1) | 
| 
 | 
 | 
322 | (1) | 
| 
 | 
 | 
322 | (1) | 
 | 
The Architect's Activities in the RUP | 
 
 
 | 
 | 
323 | (1) | 
 | 
Working with the Requirements and Project Management | 
 
 
 | 
 | 
323 | (1) | 
 | 
Refining the Architecture | 
 
 
 | 
 | 
325 | (1) | 
 | 
Maintaining Architectural Integrity | 
 
 
 | 
 | 
327 | (1) | 
 | 
The Architect's Roles in the RUP | 
 
 
 | 
 | 
328 | (1) | 
 | 
Finding Your Way in the RUP Product | 
 
 
 | 
 | 
329 | (1) | 
 | 
Resources for the Architect | 
 
 
 | 
 | 
329 | (1) | 
| 
 | 
 | 
329 | (1) | 
| 
 | 
 | 
331 | (2) | 
 | 
Chapter 17 A Developer's Guide to the RUP | 
 
 
 | 
 | 
333 | (26) | 
 | 
Your Mission as a Developer | 
 
 
 | 
 | 
333 | (2) | 
 | 
Overview of the Developer's Tasks | 
 
 
 | 
 | 
335 | (1) | 
 | 
Understand the Requirements and Design Constraints | 
 
 
 | 
 | 
336 | (2) | 
 | 
Design, Implement, and Test Use Cases and Components | 
 
 
 | 
 | 
338 | (1) | 
 | 
Design Use-Case Realizations and Components | 
 
 
 | 
 | 
338 | (1) | 
 | 
Implement Use Cases and Components | 
 
 
 | 
 | 
347 | (1) | 
| 
 | 
 | 
347 | (2) | 
 | 
Design, Implement, and Test Any Necessary Databases | 
 
 
 | 
 | 
349 | (1) | 
 | 
Frequently Integrate Your Application with the Work of Other Developers | 
 
 
 | 
 | 
350 | (1) | 
 | 
Configuration Management Workspaces | 
 
 
 | 
 | 
352 | (1) | 
| 
 | 
 | 
352 | (1) | 
| 
 | 
 | 
353 | (1) | 
| 
 | 
 | 
354 | (1) | 
| 
 | 
 | 
354 | (1) | 
 | 
Refactor Your Code and Design | 
 
 
 | 
 | 
355 | (1) | 
 | 
Use Patterns, Architectural Mechanisms, and Other Reusable Assets | 
 
 
 | 
 | 
355 | (1) | 
| 
 | 
 | 
356 | (1) | 
| 
 | 
 | 
356 | (1) | 
 | 
The Developer Role in the Rational Unified Process | 
 
 
 | 
 | 
357 | (1) | 
 | 
Available Resources for Developers | 
 
 
 | 
 | 
358 | (1) | 
| 
 | 
 | 
358 | (1) | 
| 
 | 
 | 
358 | (1) | 
 | 
Chapter 18 A Tester's Guide to the RUP | 
 
 
 | 
 | 
359 | (24) | 
 | 
The Mission of the Tester | 
 
 
 | 
 | 
359 | (1) | 
 | 
The Concept of Product Quality in the RUP | 
 
 
 | 
 | 
360 | (1) | 
 | 
Paradigms of "Good Enough" | 
 
 
 | 
 | 
361 | (1) | 
| 
 | 
 | 
362 | (1) | 
 | 
Wouldn't Quantification Help? | 
 
 
 | 
 | 
363 | (1) | 
| 
 | 
 | 
364 | (1) | 
| 
 | 
 | 
365 | (2) | 
 | 
The RUP Testing Philosophy | 
 
 
 | 
 | 
367 | (1) | 
| 
 | 
 | 
369 | (1) | 
| 
 | 
 | 
370 | (1) | 
 | 
The Test Discipline in the RUP Product | 
 
 
 | 
 | 
370 | (1) | 
 | 
Various Roles Related to Test in the RUP | 
 
 
 | 
 | 
370 | (1) | 
| 
 | 
 | 
371 | (2) | 
| 
 | 
 | 
373 | (1) | 
| 
 | 
 | 
375 | (1) | 
| 
 | 
 | 
376 | (1) | 
 | 
Validate Build Stability (Smoke Test) | 
 
 
 | 
 | 
376 | (1) | 
| 
 | 
 | 
377 | (1) | 
 | 
Achieve an Acceptable Mission | 
 
 
 | 
 | 
378 | (1) | 
| 
 | 
 | 
378 | (1) | 
| 
 | 
 | 
379 | (1) | 
| 
 | 
 | 
379 | (1) | 
| 
 | 
 | 
380 | (1) | 
| 
 | 
 | 
380 | (1) | 
| 
 | 
 | 
381 | (2) | 
| Glossary | 
 | 
383 | (6) | 
| Bibliography | 
 | 
389 | (10) | 
| Index | 
 | 
399 |  |