The Rational Unified Process: An Introduction, 2/e(Paperback)
Philippe Kruchten
- 出版商: Addison Wesley
- 出版日期: 2000-03-14
- 售價: $1,500
- 貴賓價: 9.5 折 $1,425
- 語言: 英文
- 頁數: 320
- 裝訂: Paperback
- ISBN: 0201707101
- ISBN-13: 9780201707106
-
其他版本:
The Rational Unified Process: An Introduction, 3/e (Paperback)
買這商品的人也買了...
-
$1,200$1,176 -
$640$608 -
$1,032The Unified Process Elaboration Phase: Best Practices in Implementing the UP
-
$1,032The Unified Process Construction Phase: Best Practices in Implementing the UP
-
$2,600$2,470 -
$2,800$2,660 -
$1,032The Unified Process Inception Phase: Best Practices for Completing the Unified
-
$980$774 -
$970Introduction to Algorithms, 2/e
-
$1,150$1,127 -
$399The Unified Process Transition and Production Phases
-
$580$458 -
$1,274Computer Architecture: A Quantitative Approach, 3/e(精裝本)
-
$1,029Operating System Concepts, 6/e (Windows XP Update)
-
$1,850$1,758 -
$1,650$1,568 -
$650$553 -
$760$600 -
$590$466 -
$620$527 -
$690$538 -
$720$569 -
$750$675 -
$1,500Mastering the Requirements Process, 2/e (Hardcover)
-
$650$507
相關主題
商品描述
Description
The concise, 100% authoritative guide to Rational Unified Process 2000 -- by its Lead Architect!
- Simply the fastest way to get up-and-running with RUP 2000.
- New: Coverage of business engineering, non-functional requirements, and multi-tier distributed systems.
- New: Detailed process roadmaps, checklists, and guidelines.
Philippe Kruchten, Lead Architect of the Rational Unified Process, drove the effort to merge the methods of Booch, Jacobson, and Rumbaugh, and to create a saleable product from the resulting methodology. He has more than 25 years experience in developing large, software-intensive systems in telecommunications, defense, aerospace, transportation, and the software development industry.
Table Of Contents
Preface.Goals of This Book.
Who Should Read This Book?
How to Use This Book.
Organization and Special Features.
For More Information.
Second Edition.
Acknowledgments.
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.
Summary.
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.
Summary.
2. The Rational Unified Process.
What Is the Rational Unified Process?
The Rational Unified Process as a Product.
Process Structure: Two Dimensions.
Software Best Practices in the Rational Unified Process.
Other Key Features of the Rational Unified Process.
A Brief History of the Rational Unified Process.
Summary.
The Rational Unified Process as a Product.
Process Structure: Two Dimensions.
Software Best Practices in the Rational Unified Process.
Other Key Features of the Rational Unified Process.
A Brief History of the Rational Unified Process.
Summary.
3. Static Structure: Process Description.
A Model of the Rational Unified Process.
Workers.
Activities.
Artifacts.
Workflows.
Additional Process Elements.
A Process Framework.
Summary.
Workers.
Activities.
Artifacts.
Workflows.
Additional Process Elements.
A Process Framework.
Summary.
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.
Summary.
Overcoming Difficulties: Iterate!
Gaining Control: Phases and Milestones.
A Shifting Focus across the Cycle.
Phases Revisited.
Benefits of an Iterative Approach.
Summary.
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.
Summary.
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.
Summary.
6. A Use-Case-Driven Process.
Definitions.
Identifying Use Cases.
Evolving Use Cases.
Organizing Use Cases.
Use Cases in the Process.
Summary.
Identifying Use Cases.
Evolving Use Cases.
Organizing Use Cases.
Use Cases in the Process.
Summary.
II. PROCESS WORKFLOWS.
7. The Project Management Workflow.
Purpose.
Planning an Iterative Project.
The Concept of Risk.
The Concept of Metrics.
What Is a Metric?
Workers and Artifacts.
Workflow.
Building an Iteration Plan.
Summary.
Planning an Iterative Project.
The Concept of Risk.
The Concept of Metrics.
What Is a Metric?
Workers and Artifacts.
Workflow.
Building an Iteration Plan.
Summary.
8. The Business Modeling Workflow.
Purpose.
Why Business Modeling?
Using Software Modeling Techniques for Business Modeling.
Business Modeling Scenarios.
Workers and Artifacts.
Workflow.
From the Business Models to the Systems.
Modeling the Software Development Business.
Tool Support.
Summary.
Why Business Modeling?
Using Software Modeling Techniques for Business Modeling.
Business Modeling Scenarios.
Workers and Artifacts.
Workflow.
From the Business Models to the Systems.
Modeling the Software Development Business.
Tool Support.
Summary.
9. The Requirements Workflow.
Purpose.
What Is a Requirement?
Types of Requirements.
Capturing and Managing Requirements.
Designing a User-Centered Interface.
Requirements Workflow.
Workers in Requirements.
Artifacts Used in Requirements.
Tool Support.
Summary.
What Is a Requirement?
Types of Requirements.
Capturing and Managing Requirements.
Designing a User-Centered Interface.
Requirements Workflow.
Workers in Requirements.
Artifacts Used in Requirements.
Tool Support.
Summary.
10. The Analysis and Design Workflow.
Purpose.
Analysis versus Design.
How Far Must Design Go?
Workers and Artifacts.
The Design Model.
The Analysis Model.
The Role of Interfaces.
Artifacts for Real-Time Systems.
Component-Based Design.
Workflow.
Tool Support.
Summary.
Analysis versus Design.
How Far Must Design Go?
Workers and Artifacts.
The Design Model.
The Analysis Model.
The Role of Interfaces.
Artifacts for Real-Time Systems.
Component-Based Design.
Workflow.
Tool Support.
Summary.
11. The Implementation Workflow.
Purpose.
Builds.
Integration.
Prototypes.
Workers and Artifacts.
Workflow.
Tool Support.
Summary.
Builds.
Integration.
Prototypes.
Workers and Artifacts.
Workflow.
Tool Support.
Summary.
12. The Test Workflow.
Purpose.
Quality.
Testing in the Iterative Lifecycle.
Dimensions of Testing.
The Test Model.
Workers and Artifacts.
Workflow.
Tool Support.
Summary.
Quality.
Testing in the Iterative Lifecycle.
Dimensions of Testing.
The Test Model.
Workers and Artifacts.
Workflow.
Tool Support.
Summary.
13. The Configuration and Change Management Workflow.
Purpose.
The CCM Cube.
Workers and Artifacts.
Workflow.
Tool Support.
Summary.
The CCM Cube.
Workers and Artifacts.
Workflow.
Tool Support.
Summary.
14. The Environment Workflow.
Purpose.
Workers and Artifacts.
Workflow.
Summary.
Workers and Artifacts.
Workflow.
Summary.
15. The Deployment Workflow.
Purpose.
Workers and Artifacts.
Workflow.
Summary.
Workers and Artifacts.
Workflow.
Summary.
16. Typical Iteration Plans.
Purpose.
Defining the Product Vision and the Business Case.
Building an Architectural Prototype.
Implementing the System.
Summary.
Defining the Product Vision and the Business Case.
Building an Architectural Prototype.
Implementing the System.
Summary.
17. Configuring and Implementing the Rational Unified Process.
Introduction.
The Effect of Implementing a Process.
Implementing the Rational Unified Process Step by Step.
Configuring the Process.
Implementing a Process Is a Project.
Summary.
The Effect of Implementing a Process.
Implementing the Rational Unified Process Step by Step.
Configuring the Process.
Implementing a Process Is a Project.
Summary.
Appendix A: Summary of Workers.
Appendix B: Summary of Artifacts.
Acronyms.
Glossary.
Bibliography.
Index. 0201707101T04062001