The unified software development process
By: Ivar Jacobson, Grady Booch, James Rumbaugh.
Contributors: Booch, Grady.; Rumbaugh, James.
Series: The Addison-Wesley object technology series
Publisher: Addison-Wesley
Published: 1999
Place of publication: Reading, Mass
Language: eng
Number of pages: 463
Subjects: Computer software -- Development; UML (Computer science)
Description: The Unified Process is the result of a merger and refinement of popular object-oriented methods, following on from the success of UML.
Notes: Includes bibliographical references and index.
Table of contents: title: Preface
pagenum: xvii; label: Part I
title: The Unified Software Development Process
pagenum: 1; label: Chapter 1
title: The Unified Process: Use-Case Driven, Architecture-Centric, Iterative, and Incremental
pagenum: 3; label: 1.1
title: The Unified Process in a Nutshell
pagenum: 4; label: 1.2
title: The Unified Process Is Use-Case Driven
pagenum: 5; label: 1.3
title: The Unified Process Is Architecture-Centric
pagenum: 6; label: 1.4
title: The Unified Process Is Iterative and Incremental
pagenum: 7; label: 1.5
title: The Life of the Unified Process
pagenum: 8; label: 1.5.1
title: The Product
pagenum: 9; label: 1.5.2
title: Phases within a Cycle
pagenum: 11; label: 1.6
title: An Integrated Process
pagenum: 13; label: Chapter 2
title: The Four Ps: People, Project, Product, and Process in Software Development
pagenum: 15; label: 2.1
title: People Are Crucial
pagenum: 16; label: 2.1.1
title: Development Processes Affect People
pagenum: 16; label: 2.1.2
title: Roles Will Change
pagenum: 17; label: 2.1.3
title: Turning "Resources" into "Workers"
pagenum: 18; label: 2.2
title: Projects Make the Product
pagenum: 19; label: 2.3
title: Product Is More Than Code
pagenum: 20; label: 2.3.1
title: What Is a Software System?
pagenum: 20; label: 2.3.2
title: Artifacts
pagenum: 21; label: 2.3.3
title: A System Has a Collection of Models
pagenum: 21; label: 2.3.4
title: What Is a Model?
pagenum: 22; label: 2.3.5
title: Each Model Is a Self-Contained View of the System
pagenum: 22; label: 2.3.6
title: Inside a Model
pagenum: 23; label: 2.3.7
title: Relationships between Models
pagenum: 23; label: 2.4
title: Process Directs Projects
pagenum: 24; label: 2.4.1
title: Process: A Template
pagenum: 24; label: 2.4.2
title: Related Activities Make Up Workflows
pagenum: 25; label: 2.4.3
title: Specializing Process
pagenum: 26; label: 2.4.4
title: Merits of Process
pagenum: 27; label: 2.5
title: Tools Are Integral to Process
pagenum: 28; label: 2.5.1
title: Tools Impact Process
pagenum: 28; label: 2.5.2
title: Process Drives Tools
pagenum: 28; label: 2.5.3
title: Balance Process and Tools
pagenum: 29; label: 2.5.4
title: Visual Modeling Supports UML
pagenum: 29; label: 2.5.5
title: Tools Support the Whole Life Cycle
pagenum: 30; label: 2.6
title: References
pagenum: 31; label: Chapter 3
title: A Use-Case-Driven Process
pagenum: 33; label: 3.1
title: Use-Case-Driven Development in Brief
pagenum: 35; label: 3.2
title: Why Use Cases?
pagenum: 37; label: 3.2.1
title: To Capture the Value Adding Requirements
pagenum: 37; label: 3.2.2
title: To Drive the Process
pagenum: 38; label: 3.2.3
title: To Devise the Architecture and More...
pagenum: 39; label: 3.3
title: Capturing the Use Cases
pagenum: 40; label: 3.3.1
title: The Use-Case Model Represents the Functional Requirements
pagenum: 40; label: 3.3.2
title: Actors Are the Environment of the System
pagenum: 41; label: 3.3.3
title: Use Cases Specify the System
pagenum: 41; label: 3.4
title: Analysis, Design, and Implementation to Realize the Use Cases
pagenum: 42; label: 3.4.1
title: Creating the Analysis Model from the Use Cases
pagenum: 43; label: 3.4.2
title: Each Class Must Fulfill All Its Collaboration Roles
pagenum: 48; label: 3.4.3
title: Creating the Design Model from the Analysis Model
pagenum: 48; label: 3.4.4
title: Subsystems Group Classes
pagenum: 51; label: 3.4.5
title: Creating the Implementation Model from the Design Model
pagenum: 53; label: 3.5
title: Testing the Use Cases
pagenum: 55; label: 3.6
title: Summing Up
pagenum: 57; label: 3.7
title: References
pagenum: 57; label: Chapter 4
title: An Architecture-Centric Process
pagenum: 59; label: 4.1
title: Architecture in Brief
pagenum: 60; label: 4.2
title: Why We Need Architecture
pagenum: 62; label: 4.2.1
title: Understanding the System
pagenum: 62; label: 4.2.2
title: Organizing Development
pagenum: 63; label: 4.2.3
title: Fostering Reuse
pagenum: 63; label: 4.2.4
title: Evolving the System
pagenum: 64; label: 4.3
title: Use Cases and Architecture
pagenum: 65; label: 4.4
title: The Steps to an Architecture
pagenum: 69; label: 4.4.1
title: The Architecture Baseline Is a "Small, Skinny" System
pagenum: 69; label: 4.4.2
title: Using Architecture Patterns
pagenum: 71; label: 4.4.3
title: Describing Architecture
pagenum: 74; label: 4.4.4
title: The Architect Creates the Architecture
pagenum: 76; label: 4.5
title: Finally, an Architecture Description!
pagenum: 77; label: 4.5.1
title: The Architectural View of the Use-Case Model
pagenum: 78; label: 4.5.2
title: The Architectural View of the Design Model
pagenum: 78; label: 4.5.3
title: The Architectural View of the Deployment Model
pagenum: 81; label: 4.5.4
title: The Architectural View of the Implementation Model
pagenum: 83; label: 4.6
title: Three Interesting Concepts
pagenum: 83; label: 4.6.1
title: What Is Architecture?
pagenum: 83; label: 4.6.2
title: How Is It Obtained?
pagenum: 83; label: 4.6.3
title: How Is It Described?
pagenum: 83; label: 4.7
title: References
pagenum: 84; label: Chapter 5
title: An Iterative and Incremental Process
pagenum: 85; label: 5.1
title: Iterative and Incremental in Brief
pagenum: 86; label: 5.1.1
title: Develop in Small Steps
pagenum: 87; label: 5.1.2
title: What Iteration Is Not
pagenum: 88; label: 5.2
title: Why Iterative and Incremental Development?
pagenum: 89; label: 5.2.1
title: Mitigating Risks
pagenum: 89; label: 5.2.2
title: Getting a Robust Architecture
pagenum: 91; label: 5.2.3
title: Handling Changing Requirements
pagenum: 91; label: 5.2.4
title: Allowing for Tactical Changes
pagenum: 92; label: 5.2.5
title: Achieving Continuous Integration
pagenum: 92; label: 5.2.6
title: Attaining Early Learning
pagenum: 93; label: 5.3
title: The Iterative Approach Is Risk-Driven
pagenum: 94; label: 5.3.1
title: Iterations Alleviate Technical Risks
pagenum: 95; label: 5.3.2
title: Management Is Responsible for Nontechnical Risks
pagenum: 97; label: 5.3.3
title: Dealing with Risks
pagenum: 97; label: 5.4
title: The Generic Iteration
pagenum: 98; label: 5.4.1
title: What an Iteration Is
pagenum: 98; label: 5.4.2
title: Planning the Iterations
pagenum: 100; label: 5.4.3
title: Sequencing the Iterations
pagenum: 100; label: 5.5
title: The Result of an Iteration Is an Increment
pagenum: 101; label: 5.6
title: Iterations over the Life Cycle
pagenum: 102; label: 5.7
title: Models Evolve from Iterations
pagenum: 105; label: 5.8
title: Iterations Challenge the Organization
pagenum: 106; label: 5.9
title: References
pagenum: 106; label: Part II
title: The Core Workflows
pagenum: 109; label: Chapter 6
title: Requirements Capture: From Vision to Requirements
pagenum: 111; label: 6.1
title: Why Requirements Capture Is Difficult
pagenum: 112; label: 6.2
title: The Purpose of the Requirements Workflow
pagenum: 113; label: 6.3
title: Overview of Requirements Capture
pagenum: 113; label: 6.4
title: The Role of Requirements in the Software Life Cycle
pagenum: 118; label: 6.5
title: Understanding the System Context Using a Domain Model
pagenum: 119; label: 6.5.1
title: What Is a Domain Model?
pagenum: 119; label: 6.5.2
title: Developing a Domain Model
pagenum: 121; label: 6.5.3
title: Use of the Domain Model
pagenum: 121; label: 6.6
title: Understanding the System Context Using a Business Model
pagenum: 122; label: 6.6.1
title: What Is a Business Model?
pagenum: 122; label: 6.6.2
title: How to Develop a Business Model
pagenum: 124; label: 6.6.3
title: Find Use Cases from a Business Model
pagenum: 126; label: 6.7
title: Supplementary Requirements
pagenum: 128; label: 6.8
title: Summary
pagenum: 130; label: 6.9
title: References
pagenum: 130; label: Chapter 7
title: Capturing the Requirements as Use Cases
pagenum: 131; label: 7.1
title: Introduction
pagenum: 131; label: 7.2
title: Artifacts
pagenum: 133; label: 7.2.1
title: Artifact: Use-Case Model
pagenum: 133; label: 7.2.2
title: Artifact: Actor
pagenum: 134; label: 7.2.3
title: Use Case
pagenum: 135; label: 7.2.4
title: Artifact: Architecture Description (View of the Use-Case Model)
pagenum: 139; label: 7.2.5
title: Artifact: Glossary
pagenum: 139; label: 7.2.6
title: Artifact: User-Interface Prototype
pagenum: 140; label: 7.3
title: Workers
pagenum: 140; label: 7.3.1
title: Worker: System Analyst
pagenum: 140; label: 7.3.2
title: Worker: Use-Case Specifier
pagenum: 141; label: 7.3.3
title: User-Interface Designer
pagenum: 142; label: 7.3.4
title: Worker: Architect
pagenum: 142; label: 7.4
title: Workflow
pagenum: 143; label: 7.4.1
title: Activity: Find Actors and Use Cases
pagenum: 144; label: 7.4.2
title: Activity: Prioritize Use Cases
pagenum: 153; label: 7.4.3
title: Activity: Detail a Use Case
pagenum: 153; label: 7.4.4
title: Activity: Prototype User Interface
pagenum: 160; label: 7.4.5
title: Activity: Structure the Use-Case Model
pagenum: 166; label: 7.5
title: Summary of the Requirements Workflow
pagenum: 171; label: 7.6
title: References
pagenum: 172; label: Chapter 8
title: Analysis
pagenum: 173; label: 8.1
title: Introduction
pagenum: 173; label: 8.2
title: Analysis in Brief
pagenum: 176; label: 8.2.1
title: Why Analysis Is not Design or Implementation
pagenum: 176; label: 8.2.2
title: The Purpose of Analysis: Summary
pagenum: 177; label: 8.2.3
title: Concrete Examples of When to Employ Analysis
pagenum: 178; label: 8.3
title: The Role of Analysis in the Software Life Cycle
pagenum: 179; label: 8.4
title: Artifacts
pagenum: 181; label: 8.4.1
title: Artifact: Analysis Model
pagenum: 181; label: 8.4.2
title: Artifact: Analysis Class
pagenum: 181; label: 8.4.3
title: Artifact: Use-Case Realization—Analysis
pagenum: 186; label: 8.4.4
title: Artifact: Analysis Package
pagenum: 190; label: 8.4.5
title: Artifact: Architecture Description (View of the Analysis Model)
pagenum: 193; label: 8.5
title: Workers
pagenum: 194; label: 8.5.1
title: Worker: Architect
pagenum: 194; label: 8.5.2
title: Worker: Use-Case Engineer
pagenum: 194; label: 8.5.3
title: Worker: Component Engineer
pagenum: 195; label: 8.6
title: Workflow
pagenum: 196; label: 8.6.1
title: Activity: Architectural Analysis
pagenum: 196; label: 8.6.2
title: Activity: Analyze a Use Case
pagenum: 203; label: 8.6.3
title: Activity: Analyze a Class
pagenum: 207; label: 8.6.4
title: Activity: Analyze a Package
pagenum: 211; label: 8.7
title: Summary of Analysis
pagenum: 213; label: 8.8
title: References
pagenum: 214; label: Chapter 9
title: Design
pagenum: 215; label: 9.1
title: Introduction
pagenum: 215; label: 9.2
title: The Role of Design in the Software Life Cycle
pagenum: 216; label: 9.3
title: Artifacts
pagenum: 217; label: 9.3.1
title: Artifact: Design Model
pagenum: 217; label: 9.3.2
title: Artifact: Design Class
pagenum: 218; label: 9.3.3
title: Artifact: Use-Case Realization—Design
pagenum: 221; label: 9.3.4
title: Artifact: Design Subsystem
pagenum: 224; label: 9.3.5
title: Artifact: Interface
pagenum: 226; label: 9.3.6
title: Artifact: Architecture Description (View of the Design Model)
pagenum: 226; label: 9.3.7
title: Artifact: Deployment Model
pagenum: 227; label: 9.3.8
title: Artifact: Architecture Description (View of the Deployment Model)
pagenum: 228; label: 9.4
title: Workers
pagenum: 229; label: 9.4.1
title: Worker: Architect
pagenum: 229; label: 9.4.2
title: Worker: Use-Case Engineer
pagenum: 230; label: 9.4.3
title: Worker: Component Engineer
pagenum: 230; label: 9.5
title: Workflow
pagenum: 231; label: 9.5.1
title: Activity: Architectural Design
pagenum: 232; label: 9.5.2
title: Activity: Design a Use Case
pagenum: 249; label: 9.5.3
title: Activity: Design a Class
pagenum: 255; label: 9.5.4
title: Activity: Design a Subsystem
pagenum: 263; label: 9.6
title: Summary of Design
pagenum: 265; label: 9.7
title: References
pagenum: 266; label: Chapter 10
title: Implementation
pagenum: 267; label: 10.1
title: Introduction
pagenum: 267; label: 10.2
title: The Role of Implementation in the Software Life Cycle
pagenum: 268; label: 10.3
title: Artifacts
pagenum: 269; label: 10.3.1
title: Artifact: Implementation Model
pagenum: 269; label: 10.3.2
title: Artifact: Component
pagenum: 269; label: 10.3.3
title: Artifact: Implementation Subsystem
pagenum: 272; label: 10.3.4
title: Artifact: Interface
pagenum: 274; label: 10.3.5
title: Artifact: Architecture Description (View of the Implementation Model)
pagenum: 275; label: 10.3.6
title: Artifact: Integration Build Plan
pagenum: 276; label: 10.4
title: Workers
pagenum: 277; label: 10.4.1
title: Worker: Architect
pagenum: 277; label: 10.4.2
title: Worker: Component Engineer
pagenum: 277; label: 10.4.3
title: Worker: System Integrator
pagenum: 279; label: 10.5
title: Workflow
pagenum: 279; label: 10.5.1
title: Activity: Architectural Implementation
pagenum: 280; label: 10.5.2
title: Activity: Integrate System
pagenum: 283; label: 10.5.3
title: Activity: Implement a Subsystem
pagenum: 285; label: 10.5.4
title: Activity: Implement a Class
pagenum: 288; label: 10.5.5
title: Activity: Perform Unit Test
pagenum: 289; label: 10.6
title: Summary of Implementation
pagenum: 293; label: 10.7
title: References
pagenum: 293; label: Chapter 11
title: Test
pagenum: 295; label: 11.1
title: Introduction
pagenum: 295; label: 11.2
title: The Role of Testing in the Software Life Cycle
pagenum: 296; label: 11.3
title: Artifacts
pagenum: 297; label: 11.3.1
title: Artifact: Test Model
pagenum: 297; label: 11.3.2
title: Artifact: Test Case
pagenum: 297; label: 11.3.3
title: Artifact: Test Procedure
pagenum: 300; label: 11.3.4
title: Artifact: Test Component
pagenum: 302; label: 11.3.5
title: Artifact: Plan Test
pagenum: 302; label: 11.3.6
title: Artifact: Defect
pagenum: 302; label: 11.3.7
title: Artifact: Evaluate Test
pagenum: 302; label: 11.4
title: Workers
pagenum: 303; label: 11.4.1
title: Worker: Test Designer
pagenum: 303; label: 11.4.2
title: Worker: Component Engineer
pagenum: 303; label: 11.4.3
title: Worker: Integration Tester
pagenum: 303; label: 11.4.4
title: Worker: System Tester
pagenum: 304; label: 11.5
title: Workflow
pagenum: 304; label: 11.5.1
title: Activity: Plan Test
pagenum: 305; label: 11.5.2
title: Activity: Design Test
pagenum: 306; label: 11.5.3
title: Activity: Implement Test
pagenum: 309; label: 11.5.4
title: Activity: Perform Integration Test
pagenum: 310; label: 11.5.5
title: Activity: Perform System Test
pagenum: 311; label: 11.5.6
title: Activity: Evaluate Test
pagenum: 311; label: 11.6
title: Summary of Testing
pagenum: 313; label: 11.7
title: References
pagenum: 313; label: Part III
title: Iterative and Incremental Development
pagenum: 315; label: Chapter 12
title: The Generic Iteration Workflow
pagenum: 317; label: 12.1
title: The Need for Balance
pagenum: 318; label: 12.2
title: The Phases Are the First Division of Work
pagenum: 319; label: 12.2.1
title: Inception Phase Establishes Feasibility
pagenum: 319; label: 12.2.2
title: Elaboration Phase Focuses on "Do-Ability"
pagenum: 320; label: 12.2.3
title: Construction Phase Builds the System
pagenum: 321; label: 12.2.4
title: Transition Phase Moves into the User Environment
pagenum: 322; label: 12.3
title: The Generic Iteration Revisited
pagenum: 322; label: 12.3.1
title: Core Workflows Repeat in Each Iteration
pagenum: 322; label: 12.3.2
title: Workers Participate in the Workflows
pagenum: 323; label: 12.4
title: Planning Precedes Doing
pagenum: 324; label: 12.4.1
title: Plan the Four Phases
pagenum: 325; label: 12.4.2
title: Plan the Iterations
pagenum: 326; label: 12.4.3
title: Think Long Term
pagenum: 327; label: 12.4.4
title: Plan the Evaluation Criteria
pagenum: 327; label: 12.5
title: Risks Affect Project Planning
pagenum: 328; label: 12.5.1
title: Manage a Risk List
pagenum: 328; label: 12.5.2
title: Risks Affect the Iteration Plan
pagenum: 329; label: 12.5.3
title: Schedule Risk Action
pagenum: 329; label: 12.6
title: Use-Case Prioritization
pagenum: 330; label: 12.6.1
title: Risks Specific to a Particular Product
pagenum: 331; label: 12.6.2
title: Risk of Not Getting the Architecture Right
pagenum: 331; label: 12.6.3
title: Risk of Not Getting Requirements Right
pagenum: 332; label: 12.7
title: Resources Needed
pagenum: 333; label: 12.7.1
title: Projects Differ Widely
pagenum: 334; label: 12.7.2
title: A Typical Project Looks Like This
pagenum: 335; label: 12.7.3
title: Complex Projects Have Greater Needs
pagenum: 335; label: 12.7.4
title: New Product Line Calls for Experience
pagenum: 336; label: 12.7.5
title: Paying the Cost of the Resources Used
pagenum: 337; label: 12.8
title: Assess the Iterations and Phases
pagenum: 338; label: 12.8.1
title: Criteria Not Achieved
pagenum: 338; label: 12.8.2
title: The Criteria Themselves
pagenum: 339; label: 12.8.3
title: The Next Iteration
pagenum: 339; label: 12.8.4
title: Evolution of the Model Set
pagenum: 340; label: Chapter 13
title: Inception Launches the Project
pagenum: 341; label: 13.1
title: The Inception Phase in Brief
pagenum: 341; label: 13.2
title: Early in the Inception Phase
pagenum: 342; label: 13.2.1
title: Before the Inception Phase Begins
pagenum: 342; label: 13.2.2
title: Planning the Inception Phase
pagenum: 343; label: 13.2.3
title: Expanding the System Vision
pagenum: 344; label: 13.2.4
title: Setting the Evaluation Criteria
pagenum: 344; label: 13.3
title: The Archetypal Inception Iteration Workflow
pagenum: 346; label: 13.3.1
title: Introduction to the Five Core Workflows
pagenum: 346; label: 13.3.2
title: Fitting the Project into the Development Environment
pagenum: 348; label: 13.3.3
title: Finding Critical Risks
pagenum: 348; label: 13.4
title: Execute the Core Workflows, Requirements to Test
pagenum: 348; label: 13.4.1
title: Capture the Requirements
pagenum: 350; label: 13.4.2
title: Analysis
pagenum: 352; label: 13.4.3
title: Design
pagenum: 353; label: 13.4.5
title: Test
pagenum: 354; label: 13.5
title: Make the Initial Business Case
pagenum: 354; label: 13.5.1
title: Outline Business Bid
pagenum: 354; label: 13.5.2
title: Estimate Return on Investment
pagenum: 356; label: 13.6
title: Assess the Iteration(s) in the Inception Phase
pagenum: 356; label: 13.7
title: Planning the Elaboration Phase
pagenum: 357; label: 13.8
title: The Deliverables for the Inception Phase
pagenum: 358; label: Chapter 14
title: The Elaboration Phase Makes the Architectural Baseline
pagenum: 359; label: 14.1
title: The Elaboration Phase in Brief
pagenum: 359; label: 14.2
title: Early in the Elaboration Phase
pagenum: 360; label: 14.2.1
title: Planning the Elaboration Phase
pagenum: 360; label: 14.2.2
title: Building the Team
pagenum: 361; label: 14.2.3
title: Modifying the Development Environment
pagenum: 361; label: 14.2.4
title: Setting Evaluation Criteria
pagenum: 361; label: 14.3
title: The Archetypal Elaboration Iteration Workflow
pagenum: 362; label: 14.3.1
title: Capture and Refine Most of the Requirements
pagenum: 363; label: 14.3.2
title: Develop the Architectural Baseline
pagenum: 364; label: 14.3.3
title: Iterate While the Team Is Small
pagenum: 364; label: 14.4
title: Execute the Core Workflows—Requirements to Test
pagenum: 364; label: 14.4.1
title: Capture the Requirements
pagenum: 365; label: 14.4.2
title: Analysis
pagenum: 367; label: 14.4.3
title: Design
pagenum: 372; label: 14.4.4
title: Implementation
pagenum: 374; label: 14.4.5
title: Test
pagenum: 376; label: 14.5
title: Make the Business Case
pagenum: 377; label: 14.5.1
title: Prepare the Business Bid
pagenum: 378; label: 14.5.2
title: Update Return on Investment
pagenum: 378; label: 14.6
title: Assess the Iterations in the Elaboration Phase
pagenum: 378; label: 14.7
title: Planning the Construction Phase
pagenum: 379; label: 14.8
title: The Key Deliverables
pagenum: 380; label: Chapter 15
title: Construction Leads to Initial Operational Capability
pagenum: 381; label: 15.1
title: The Construction Phase in Brief
pagenum: 382; label: 15.2
title: Early in the Construction Phase
pagenum: 382; label: 15.2.1
title: Staffing the Phase
pagenum: 383; label: 15.2.2
title: Setting the Evaluation Criteria
pagenum: 383; label: 15.3
title: The Archetypal Construction Iteration Workflow
pagenum: 384; label: 15.4
title: Execute the Core Workflows—Requirements to Testing
pagenum: 385; label: 15.4.1
title: Requirements
pagenum: 387; label: 15.4.2
title: Analysis
pagenum: 388; label: 15.4.3
title: Design
pagenum: 389; label: 15.4.4
title: Implementation
pagenum: 390; label: 15.4.5
title: Test
pagenum: 391; label: 15.5
title: Controlling the Business Case
pagenum: 393; label: 15.6
title: Assess the Iterations and the Construction Phase
pagenum: 393; label: 15.7
title: Planning the Transition Phase
pagenum: 393; label: 15.8
title: The Key Deliverables
pagenum: 394; label: Chapter 16
title: Transition Completes Product Release
pagenum: 395; label: 16.1
title: The Transition Phase in Brief
pagenum: 396; label: 16.2
title: Early in the Transition Phase
pagenum: 397; label: 16.2.1
title: Planning the Transition Phase
pagenum: 397; label: 16.2.2
title: Staffing the Transition Phase
pagenum: 399; label: 16.2.3
title: Setting the Evaluation Criteria
pagenum: 399; label: 16.3
title: The Core Workflows Play a Small Role in this Phase
pagenum: 400; label: 16.4
title: What We Do in the Transition Phase
pagenum: 401; label: 16.4.1
title: Getting the Beta Release Out
pagenum: 401; label: 16.4.2
title: Installing the Beta Release
pagenum: 402; label: 16.4.3
title: Responding to the Test Results
pagenum: 402; label: 16.4.4
title: Adapting the Product to Varied User Environments
pagenum: 403; label: 16.4.5
title: Completing the Artifacts
pagenum: 404; label: 16.4.6
title: When Does the Project End?
pagenum: 404; label: 16.5
title: Completing the Business Case
pagenum: 405; label: 16.5.1
title: Controlling Progress
pagenum: 405; label: 16.5.2
title: Review of the Business Plan
pagenum: 405; label: 16.6
title: Assess the Transition Phase
pagenum: 406; label: 16.6.1
title: Assess the Iterations and the Phase
pagenum: 406; label: 16.6.2
title: Postmortem of the Project
pagenum: 407; label: 16.7
title: Planning the Next Release or Generation
pagenum: 407; label: 16.8
title: The Key Deliverables
pagenum: 407; label: Chapter 17
title: Making the Unified Process Work
pagenum: 409; label: 17.1
title: The Unified Process Helps You Deal with Complexity
pagenum: 409; label: 17.1.1
title: The Life Cycle Objectives
pagenum: 410; label: 17.1.2
title: The Life Cycle Architecture
pagenum: 410; label: 17.1.3
title: Initial Operational Capability
pagenum: 411; label: 17.1.4
title: Product Release
pagenum: 411; label: 17.2
title: The Major Themes
pagenum: 411; label: 17.3
title: Management Leads Conversion to Unified Process
pagenum: 412; label: 17.3.1
title: The Case for Action
pagenum: 413; label: 17.3.2
title: The Reengineering Directive Persuades
pagenum: 413; label: 17.3.3
title: Implementing the Transition
pagenum: 414; label: 17.4
title: Specializing the Unified Process
pagenum: 416; label: 17.4.1
title: Tailoring the Process
pagenum: 416; label: 17.4.2
title: Filling in the Process Framework
pagenum: 417; label: 17.5
title: Relate to the Broader Community
pagenum: 418; label: 17.6
title: Get the Benefits of the Unified Process
pagenum: 418; label: 17.7
title: References
pagenum: 419; label: Appendix A
title: Overview of the UML
pagenum: 421; label: A.1
title: Introduction
pagenum: 421; label: A.1.1
title: Vocabulary
pagenum: 422; label: A.1.2
title: Extensibility Mechanisms
pagenum: 422; label: A.2
title: Graphical Notation
pagenum: 423; label: A.2.1
title: Structural Things
pagenum: 423; label: A.2.2
title: Behavioral Things
pagenum: 424; label: A.2.3
title: Grouping Things
pagenum: 425; label: A.2.4
title: Annotational Things
pagenum: 425; label: A.2.5
title: Dependency Relationships
pagenum: 425; label: A.2.6
title: Association Relationships
pagenum: 425; label: A.2.7
title: Generalization Relationships
pagenum: 426; label: A.2.8
title: Extensibility Mechanisms
pagenum: 426; label: A.3
title: Glossary of Terms
pagenum: 426; label: A.4
title: References
pagenum: 433; label: Appendix B
title: The Unified Process–Specific Extensions of the UML
pagenum: 435; label: B.1
title: Introduction
pagenum: 435; label: B.2
title: Stereotypes
pagenum: 435; label: B.3
title: Tagged Values
pagenum: 438; label: B.4
title: Graphical Notation
pagenum: 439; label: B.5
title: References
pagenum: 439; label: Appendix C
title: General Glossary
pagenum: 441; label: C.1
title: Introduction
pagenum: 441; label: C.2
title: Terms
pagenum: 441; title: Index
pagenum: 451