| |
| |
| 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 | |
| |
| |
| |
| The Process | |
| |
| |
| |
| 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 | |
| |
| |
| |
| 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 | |
| |
| |
| |
| Static Structure: Process Description | |
| |
| |
| A Model of the Rational Unified Process | |
| |
| |
| Workers | |
| |
| |
| Activities | |
| |
| |
| Artifacts | |
| |
| |
| Workflows | |
| |
| |
| Additional Process Elements | |
| |
| |
| A Process Framework | |
| |
| |
| Summary | |
| |
| |
| |
| 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 | |
| |
| |
| |
| 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 | |
| |
| |
| |
| A Use-Case-Driven Process | |
| |
| |
| Definitions | |
| |
| |
| Identifying Use Cases | |
| |
| |
| Evolving Use Cases | |
| |
| |
| Organizing Use Cases | |
| |
| |
| Use Cases in the Process | |
| |
| |
| Summary | |
| |
| |
| |
| Process Workflows | |
| |
| |
| |
| 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 Interation Plan | |
| |
| |
| Summary | |
| |
| |
| |
| 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 | |
| |
| |
| |
| 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 | |
| |
| |
| |
| 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 | |
| |
| |
| |
| The Implementation Workflow | |
| |
| |
| Purpose | |
| |
| |
| Builds | |
| |
| |
| Integration | |
| |
| |
| Prototypes | |
| |
| |
| Workers and Artifacts | |
| |
| |
| Workflow | |
| |
| |
| Tool Support | |
| |
| |
| Summary | |
| |
| |
| |
| The Test Workflow | |
| |
| |
| Purpose | |
| |
| |
| Quality | |
| |
| |
| Testing in the Iterative Lifecycle | |
| |
| |
| Dimensions of Testing | |
| |
| |
| The Test Model | |
| |
| |
| Workers and Artifacts | |
| |
| |
| Workflow | |
| |
| |
| Tool Support | |
| |
| |
| Summary | |
| |
| |
| |
| The Configuration and Change Management Workflow | |
| |
| |
| Purpose | |
| |
| |
| The CCM Cube | |
| |
| |
| Workers and Artifacts | |
| |
| |
| Workflow | |
| |
| |
| Tool Support | |
| |
| |
| Summary | |
| |
| |
| |
| The Environment Workflow | |
| |
| |
| Purpose | |
| |
| |
| Workers and Artifacts | |
| |
| |
| Workflow | |
| |
| |
| Summary | |
| |
| |
| |
| The Deployment Workflow | |
| |
| |
| Purpose | |
| |
| |
| Workers and Artifacts | |
| |
| |
| Workflow | |
| |
| |
| Summary | |
| |
| |
| |
| Typical Iteration Plans | |
| |
| |
| Purpose | |
| |
| |
| Defining the Product Vision and the Business Case | |
| |
| |
| Building an Architectural Prototype | |
| |
| |
| Implementing the System | |
| |
| |
| Summary | |
| |
| |
| |
| 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 | |
| |
| |
| |
| Summary of Workers | |
| |
| |
| |
| Summary of Artifacts | |
| |
| |
| Acronyms | |
| |
| |
| Glossary | |
| |
| |
| Bibliography | |
| |
| |
| Index | |