The Rational Unified Process: An Introduction, 3/e (Paperback)
暫譯: 理性統一流程：入門，第3版 (平裝本)

Summary

The Rational Unified Process, Third Edition, is a concise introduction to IBM's Web-enabled software engineering process. Rational Unified Process®, or RUP®, Lead Architect Philippe Kruchten quickly and clearly describes the concepts, structure, content, and motivation that are central to the RUP. Readers will learn how this approach to software development can be used to produce high-quality software, on schedule and on budget, using the Unified Modeling Language (UML), software automation, and other industry best practices.

The RUP unifies the entire software development team and optimizes the productivity of each team member by bringing them the experience of industry leaders and lessons learned from thousands of projects. It provides detailed and practical guidance through all phases of the software development life cycle, but it is not inflexible. The RUP can be tailored to suit a wide variety of projects and organizations.

This new edition has been updated to reflect all the changes integrated into the latest version of the Rational Unified Process--RUP 2003. It includes a four-color poster that lists key RUP elements: disciplines, workflows, artifacts, phases, and milestones.

RUP 2003 also offers

The RUP Builder with enhanced configurability, process views, and three base configurations.

MyRUP, enabling personalized views of the RUP configuration.

Additions to the Rational Process Workbench, used to define process components, perform modifications to the RUP, and create process plugins.

The introduction of a separate Process Engineering Process offering guidance on adapting the RUP, creating plugins, and deploying the RUP.

The Rational Unified Process, Third Edition, is a reliable introduction to the Rational Unified Process that will serve project managers and software professionals alike. 

Table of Contents

Preface.

I. THE PROCESS.

1. Software Development Best Practices.

The Value of Software.

Symptoms and Root Causes of Software Development Problems.

Software Best Practices.

Develop Software Iteratively.

Manage Requirements.

Use Component-Based Architectures.

Visually Model Software.

Continuously Verify Software Quality.

Control Changes to Software.

The Rational Unified Process.

2. The Rational Unified Process.

What Is the Rational Unified Process?

The Rational Unified Process as a Product.

Software Best Practices in the Rational Unified Process.

Other Key Features of the Rational Unified Process.

A Brief History of the Rational Unified Process.

3. Static Structure: Process Description.

A Model of the Rational Unified Process.

Roles.

Activities.

Artifacts.

Disciplines.

Workflows.

Additional Process Elements.

A Process Framework.

4. Dynamic Structure: Iterative Development.

The Sequential Process.

Overcoming Difficulties: Iterate!

Gaining Control: Phases and Milestones.

A Shifting Focus across the Cycle.

Phases Revisited.

Benefits of an Iterative Approach.

5. An Architecture-Centric Process.

The Importance of Models.

Architecture.

The Importance of Architecture.

A Definition of Architecture.

Architecture Representation.

An Architecture-Centric Process.

The Purpose of Architecture.

Component-Based Development.

Other Architectural Concepts.

6. A Use-Case-Driven Process.

Definitions.

Identifying Use Cases.

Evolving Use Cases.

Organizing Use Cases.

Use Cases in the Process.

II. PROCESS DISCIPLINES.

7. The Project Management Discipline.

Purpose.

Planning an Iterative Project.

The Concept of Risk.

The Concept of Measurement.

Roles and Artifacts.

Workflow.

Building an Iteration Plan.

8. The Business Modeling Discipline.

Purpose.

Why Business Modeling?

Using Software Engineering Techniques for Business Modeling.

Business Modeling Scenarios.

Roles and Artifacts.

Workflow.

From the Business Models to the Systems.

Modeling the Software Development Business.

Tool Support.

9. The Requirements Discipline.

Purpose.

What Is a Requirement?

Types of Requirements.

Capturing and Managing Requirements.

Requirements Workflow.

Roles in Requirements.

Artifacts Used in Requirements.

Tool Support.

10. The Analysis and Design Discipline.

Purpose.

Analysis versus Design.

How Far Must Design Go?

Roles and Artifacts.

Designing a User-Centered Interface.

The Design Model.

The Analysis Model.

The Role of Interfaces.

Artifacts for Real-Time Systems.

Component-Based Design.

Workflow.

Tool Support.

11. The Implementation Discipline.

Purpose.

Builds.

Integration.

Prototypes.

Roles and Artifacts.

Workflow.

Tool Support.

12. The Test Discipline.

Purpose.

Testing in the Iterative Lifecycle.

Dimensions of Testing.

Roles and Artifacts.

Workflow.

Tool Support.

13. The Configuration and Change Management Discipline.

Purpose.

The CCM Cube.

Roles and Artifacts.

Workflow.

Tool Support.

14. The Environment Discipline.

Purpose.

Process Engineering Process.

Roles and Artifacts.

Workflow.

Tool Support.

15. The Deployment Discipline.

Purpose.

Roles and Artifacts.

Workflow.

16. Typical Iteration Plans.

Defining the Product Vision and the Business Case.

Building an Architectural Prototype.

Implementing the System.

17. Implementing the Rational Unified Process.

Introduction.

The Effect of Implementing a Process.

Implementing the Rational Unified Process Step by Step.

Implementing a Process Is a Project.

Appendix A: Summary of Roles.

Appendix B: Summary of Artifacts.

Appendix C: Acronyms.

Glossary.

Bibliography.

Index.