The Unified Process Explained
Published on 6. December 2001
Book
Paperback/Softback
208 pages
978-0-201-74204-6 (ISBN)
Description
For software developers seeking a more effective approach to design and analysis, the Rational Unified Process (RUP) combines the best ideas from several market-leading analysis and design methodologies, together with best practices proven in real-world enterprise projects. However, many developers and managers find RUP overwhelming when they first encounter it. In this book, Kendall Scott simplifies RUP, scaling it down and organizing it into bite-size chunks that are easy to understand -- and use. The author begins with an overview of RUP, presenting a nutshell description, history, major themes, and key terminology. Next, he introduces each of RUP's five workflows -- Requirements, Analysis, Design, Implementation, and Test -- covering goals, roles, activities, artifacts, and more. Each Activity is illuminated with a diagram clearly explaining its nonlinear nature. Scott details the Inception, Elaboration, and Construction phases of the RUP process, culminating in a description of the Transition phase, in which the project team rolls out its system to customers. From start to finish, Scott relies on the same Internet Bookstore case study that he has used successfully in his best-selling UML Explained. For all software engineers, developers, analysts, architects, project and IT managers seeking to optimize their software development processes; and for every IT professional using or considering RUP.
More details
Person
Kendall Scott is a UML trainer and consultant. With more than sixteen years of experience as a technical writer, he is skilled in converting complex, technical material into understandable and easy-to-use manuals.
Content
1. Overview.
Introduction.
History.
Use Case Driven.
Architecture-Centric.
Understanding the Big Picture.
Organizing the Development Effort.
Facilitating the Possibilities for Reuse.
Evolving the System.
Guiding the Use Cases.
Iterative and Incremental.
Logical Progress Toward a Robust Architecture.
Dealing With Ongoing Changes in Requirements.
Greater Flexibility to Change the Plan.
Continuous Integration.
Early Understanding.
Ongoing Focus on Risk.
The Four Phases.
Inception.
Elaboration.
Construction.
Transition.
The Five Workflows.
Requirements.
Analysis.
Design.
Implementation.
Test.
Iterations and Increments.
Artifacts, Workers, and Activities.
Artifacts.
Workers.
Activities.
2. The Requirements Workflow.
Introduction.
Reach Agreement on the System Context.
List Candidate Requirements.
Identify and Negotiate Functional Requirements.
Specify Nonfunctional Requirements.
Artifacts.
Domain Model.
Business Model.
Glossary.
Actor.
Use Case 24.
User-Interface Prototype.
Use Case Model.
Architecture Description (View of the Use Case Model).
Supplementary Requirements.
Workers.
System Analyst.
Use Case Specifier.
User-Interface Designer.
Architect.
Activities.
Build the Domain Model.
Build the Business Model.
Find Actors and Use Cases.
Prototype the User Interface.
Prioritize the Use Cases.
Detail a Use Case.
Structure the Use Case Model.
3. The Analysis Workflow.
Introduction.
Artifacts.
Analysis Class.
Use Case Realization-Analysis.
Analysis Package.
Analysis Model.
Architecture Description (View of the Analysis Model).
Workers.
Architect.
Use Case Engineer.
Component Engineer.
Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Analyze a Class.
Analyze a Package.
4. The Design Workflow.
Introduction.
Artifacts.
Design Class.
Use Case Realization-Design.
Interface.
Design Subsystem.
Design Model.
Architecture Description (View of the Design Model).
Deployment Model.
Architecture Description (View of the Deployment Model).
Workers.
Architect.
Use Case Engineer.
Component Engineer.
Activities.
Perform Architectural Design.
Design a Use Case
Design a Class.
Design a Subsystem.
5. The Implementation Workflow.
Introduction.
Artifacts.
Component.
Interface.
Implementation Subsystem.
Implementation Model.
Architecture Description (View of the Implementation Model).
Integration Build Plan.
Workers.
Architect.
Component Engineer.
System Integrator.
Activities.
Perform Architectural Implementation.
Implement a Class.
Perform Unit Test.
Implement a Subsystem.
Integrate the System.
6. The Test Workflow.
Introduction.
Artifacts.
Test Case.
Test Procedure.
Test Component.
Test Model.
Test Plan.
Defect.
Test Evaluation.
Workers.
Test Engineer.
Component Engineer.
Integration Tester.
System Tester.
Activities.
Plan Test.
Design Test.
Implement Test.
Perform Integration Test.
Perform System Test.
Evaluate Test.
7. The Inception Phase.
Introduction.
Getting Started.
Plan the Inception Phase.
Expand the System Vision.
Establish the Evaluation Criteria.
Requirements Activities.
Build the Domain Model.
Build the Business Model.
Find Actors and Use Cases.
Prioritize the Use Cases.
Detail a Use Case.
Analysis Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Design Activities.
Perform Architectural Design.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Make the Initial Business Case.
Do Initial Planning for the Elaboration Phase.
8. Elaboration Phase.
Introduction.
Getting Started.
Plan the Elaboration Phase.
Establish the Evaluation Criteria.
Requirements Activities.
Build the Domain Model.
Build the Business Model.
Find Actors and Use Cases.
Prototype the User Interface.
Prioritize the Use Cases.
Detail a Use Case.
Structure the Use Case Model.
Analysis Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Analyze a Class.
Analyze a Package.
Design Activities.
Perform Architectural Design.
Design a Use Case.
Design a Class.
Design a Subsystem.
Implementation Activities.
Perform Architectural Implementation.
Implement a Class.
Perform Unit Test.
Implement a Subsystem.
Integrate the System.
Test Activities.
Plan Test.
Design Test.
Implement Test.
Perform Integration Test.
Perform System Test.
Evaluate Test.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Make the Full Business Case.
Do Initial Planning for the Construction Phase.
9. The Construction Phase.
Introduction.
Getting Started.
Plan the Construction Phase.
Establish the Evaluation Criteria.
Requirements Activities.
Find Actors and Use Cases.
Prototype the User Interface.
Prioritize the Use Cases.
Detail a Use Case.
Structure the Use Case Model.
Analysis Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Analyze a Class.
Analyze a Package.
Design Activities.
Perform Architectural Design.
Design a Use Case.
Design a Class.
Design a Subsystem.
Implementation Activities.
Implement a Class.
Perform Unit Test.
Implement a Subsystem.
Integrate the System.
Test Activities.
Plan Test.
Design Test.
Implement Test.
Perform Integration Test.
Perform System Test.
Evaluate Test.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Do Initial Planning for the Transition Phase.
10. The Transition Phase.
Introduction.
Getting Started.
Plan the Transition Phase.
Establish the Evaluation Criteria.
Activities.
Get the Beta Release Out.
Install the Beta Release.
Respond to Test Results.
Adapt the Product to Varied User Environments.
Complete the Artifacts.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Complete the Business Case.
Do a Postmortem for the Project.
Plan the Next Release or Generation.
Appendix A. The Rational Unified Process.
Workflows.
Project Management.
Business Modeling.
Requirements.
Analysis and Design.
Implementation.
Test.
Configuration and Change Management.
Environment.
Deployment.
Artifact Sets.
Workers.
Appendix B. Extreme Programming and the RUP.
A High-Level View of XP.
Values.
Fundamental Principles.
Development Practices.
XP and the RUP: Common Ground.
XP and the RUP: Key Differences.
So, Is XP an Instance of the RUP Or Not?
Appendix C. The ICONIX Process.
Bibliography.
Glossary.
Index. 0201742047T08212001
Introduction.
History.
Use Case Driven.
Architecture-Centric.
Understanding the Big Picture.
Organizing the Development Effort.
Facilitating the Possibilities for Reuse.
Evolving the System.
Guiding the Use Cases.
Iterative and Incremental.
Logical Progress Toward a Robust Architecture.
Dealing With Ongoing Changes in Requirements.
Greater Flexibility to Change the Plan.
Continuous Integration.
Early Understanding.
Ongoing Focus on Risk.
The Four Phases.
Inception.
Elaboration.
Construction.
Transition.
The Five Workflows.
Requirements.
Analysis.
Design.
Implementation.
Test.
Iterations and Increments.
Artifacts, Workers, and Activities.
Artifacts.
Workers.
Activities.
2. The Requirements Workflow.
Introduction.
Reach Agreement on the System Context.
List Candidate Requirements.
Identify and Negotiate Functional Requirements.
Specify Nonfunctional Requirements.
Artifacts.
Domain Model.
Business Model.
Glossary.
Actor.
Use Case 24.
User-Interface Prototype.
Use Case Model.
Architecture Description (View of the Use Case Model).
Supplementary Requirements.
Workers.
System Analyst.
Use Case Specifier.
User-Interface Designer.
Architect.
Activities.
Build the Domain Model.
Build the Business Model.
Find Actors and Use Cases.
Prototype the User Interface.
Prioritize the Use Cases.
Detail a Use Case.
Structure the Use Case Model.
3. The Analysis Workflow.
Introduction.
Artifacts.
Analysis Class.
Use Case Realization-Analysis.
Analysis Package.
Analysis Model.
Architecture Description (View of the Analysis Model).
Workers.
Architect.
Use Case Engineer.
Component Engineer.
Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Analyze a Class.
Analyze a Package.
4. The Design Workflow.
Introduction.
Artifacts.
Design Class.
Use Case Realization-Design.
Interface.
Design Subsystem.
Design Model.
Architecture Description (View of the Design Model).
Deployment Model.
Architecture Description (View of the Deployment Model).
Workers.
Architect.
Use Case Engineer.
Component Engineer.
Activities.
Perform Architectural Design.
Design a Use Case
Design a Class.
Design a Subsystem.
5. The Implementation Workflow.
Introduction.
Artifacts.
Component.
Interface.
Implementation Subsystem.
Implementation Model.
Architecture Description (View of the Implementation Model).
Integration Build Plan.
Workers.
Architect.
Component Engineer.
System Integrator.
Activities.
Perform Architectural Implementation.
Implement a Class.
Perform Unit Test.
Implement a Subsystem.
Integrate the System.
6. The Test Workflow.
Introduction.
Artifacts.
Test Case.
Test Procedure.
Test Component.
Test Model.
Test Plan.
Defect.
Test Evaluation.
Workers.
Test Engineer.
Component Engineer.
Integration Tester.
System Tester.
Activities.
Plan Test.
Design Test.
Implement Test.
Perform Integration Test.
Perform System Test.
Evaluate Test.
7. The Inception Phase.
Introduction.
Getting Started.
Plan the Inception Phase.
Expand the System Vision.
Establish the Evaluation Criteria.
Requirements Activities.
Build the Domain Model.
Build the Business Model.
Find Actors and Use Cases.
Prioritize the Use Cases.
Detail a Use Case.
Analysis Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Design Activities.
Perform Architectural Design.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Make the Initial Business Case.
Do Initial Planning for the Elaboration Phase.
8. Elaboration Phase.
Introduction.
Getting Started.
Plan the Elaboration Phase.
Establish the Evaluation Criteria.
Requirements Activities.
Build the Domain Model.
Build the Business Model.
Find Actors and Use Cases.
Prototype the User Interface.
Prioritize the Use Cases.
Detail a Use Case.
Structure the Use Case Model.
Analysis Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Analyze a Class.
Analyze a Package.
Design Activities.
Perform Architectural Design.
Design a Use Case.
Design a Class.
Design a Subsystem.
Implementation Activities.
Perform Architectural Implementation.
Implement a Class.
Perform Unit Test.
Implement a Subsystem.
Integrate the System.
Test Activities.
Plan Test.
Design Test.
Implement Test.
Perform Integration Test.
Perform System Test.
Evaluate Test.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Make the Full Business Case.
Do Initial Planning for the Construction Phase.
9. The Construction Phase.
Introduction.
Getting Started.
Plan the Construction Phase.
Establish the Evaluation Criteria.
Requirements Activities.
Find Actors and Use Cases.
Prototype the User Interface.
Prioritize the Use Cases.
Detail a Use Case.
Structure the Use Case Model.
Analysis Activities.
Perform Architectural Analysis.
Analyze a Use Case.
Analyze a Class.
Analyze a Package.
Design Activities.
Perform Architectural Design.
Design a Use Case.
Design a Class.
Design a Subsystem.
Implementation Activities.
Implement a Class.
Perform Unit Test.
Implement a Subsystem.
Integrate the System.
Test Activities.
Plan Test.
Design Test.
Implement Test.
Perform Integration Test.
Perform System Test.
Evaluate Test.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Do Initial Planning for the Transition Phase.
10. The Transition Phase.
Introduction.
Getting Started.
Plan the Transition Phase.
Establish the Evaluation Criteria.
Activities.
Get the Beta Release Out.
Install the Beta Release.
Respond to Test Results.
Adapt the Product to Varied User Environments.
Complete the Artifacts.
Taking Stock.
Assess Each Iteration.
Assess the Phase as a Whole.
Looking Ahead.
Complete the Business Case.
Do a Postmortem for the Project.
Plan the Next Release or Generation.
Appendix A. The Rational Unified Process.
Workflows.
Project Management.
Business Modeling.
Requirements.
Analysis and Design.
Implementation.
Test.
Configuration and Change Management.
Environment.
Deployment.
Artifact Sets.
Workers.
Appendix B. Extreme Programming and the RUP.
A High-Level View of XP.
Values.
Fundamental Principles.
Development Practices.
XP and the RUP: Common Ground.
XP and the RUP: Key Differences.
So, Is XP an Instance of the RUP Or Not?
Appendix C. The ICONIX Process.
Bibliography.
Glossary.
Index. 0201742047T08212001