The Unified Process Explained / Edition 1 by Kendall Scott | 9780201742046 | Paperback | Barnes & Noble
The Unified Process Explained / Edition 1

The Unified Process Explained / Edition 1

by Kendall Scott
     
 

ISBN-10: 0201742047

ISBN-13: 9780201742046

Pub. Date: 11/28/2001

Publisher: Addison-Wesley

The Rational Unified Process (RUP) has been widely adopted across the software industry. However, many software developers and managers--especially those working in medium-to-small development organizations--are hesitant to delve into this seemingly complex and time-consuming topic.

The Unified Process Explained is a concise, accessible, and

Overview

The Rational Unified Process (RUP) has been widely adopted across the software industry. However, many software developers and managers--especially those working in medium-to-small development organizations--are hesitant to delve into this seemingly complex and time-consuming topic.

The Unified Process Explained is a concise, accessible, and practical guide that's meant to help significantly shorten the learning curve for practitioners unfamiliar with this methodology. It explains the essentials of the Unified Process (the RUP's core elements), guides you through the process step-by-step, and shows how you can put the methodology to work on your next project.

The book starts with a useful overview of the history, motivation, key concepts, and terminology of the Unified Process. The author then details the five pillars of development: requirements, analysis, design, implementation, and test workflows. In addition, the book enumerates the four phases of Unified Process development: inception, elaboration, construction, and transition; and it shows how the workflows are integrated into these phases. In laying out the details of this integration, the book illustrates the Unified Process's most useful feature--its iterative nature.

With this book as your guide, you will gain an understanding of important concepts and activities such as:

  • Iterations and increments
  • Business and domain modeling
  • Identifying actors and use cases
  • Prototyping the user interface
  • Robustness analysis
  • Design and deployment models
  • Statechart and activity diagrams
  • Implementation models

A large-scale example of an Internet bookstore runs throughout the book to illustrate concepts and techniques. The industry-standard Unified Modeling Language is used to express structure and function. The Unified Process Explained demystifies this valuable methodology and will lead you on your way to successfully applying the Rational Unified Process.

0201742047B11142001

Product Details

ISBN-13:
9780201742046
Publisher:
Addison-Wesley
Publication date:
11/28/2001
Edition description:
New Edition
Pages:
208
Product dimensions:
7.20(w) x 9.20(h) x 0.50(d)

Table of Contents

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

Customer Reviews

Average Review:

Write a Review

and post it to your social network

     

Most Helpful Customer Reviews

See all customer reviews >