Read more
Figures. Tables. Foreword. Preface. I. INTRODUCING THE RATIONAL UNIFIED PROCESS. 1. Introducing the Rational Unified Process. What Is the Rational Unified Process? The RUP-The Approach. Underlying Principles of the RUP Approach. The RUP and Iterative Development. The RUP--A Well-Defined Software Engineering Process. The Dynamic Structure of the Rational Unified Process. The Static Structure of the Rational Unified Process. The RUP-A Customizable Process Product. Configuration and Process Authoring Tools. Process Delivery Tools. Who Uses the RUP Product? Conclusion. 2. The Spirit of the RUP: Guidelines for Success. Attack Major Risks Early and Continuously, or They Will Attack You. Summary. Ensure That You Deliver Value to Your Customer. Summary. Stay Focused on Executable Software. Summary. Accommodate Change Early in the Project. Summary. Baseline an Executable Architecture Early On. Summary. Build Your System with Components. Summary. Work Together as One Team. Summary. Make Quality a Way of Life, Not an Afterthought. Summary. Conclusion. 3. Comparing Processes: The RUP, Agile Methods, and Heavyweight Government Standards. How Can We Compare Processes? Agile Development: Low-Ceremony, Iterative Approaches. SEI CMM, SEI CMMI, ISO/IEC, DOD-STD, MIL-STD: High Ceremony Striving for Higher Predictability. SEI CMM: Process Assessment Framework. SEI CMMI: Process Assessment Framework. ISO/IEC 15504: Process Assessment Framework. DOD-STD and MIL-STD: High-Ceremony Processes. The RUP: An Iterative Approach with an Adaptable Level of Ceremony. How Iterative Do You Want to Be? How Much Ceremony Do You Want? What Kind of RUP Configuration Meets Your Process Needs? Project Deimos: Team of One. Project Ganymede: Small Project with Tight Timeline. Project Mars: Average-Size Project without Iterative Development Experience. Project Jupiter: Large Distributed Project. Conclusion. 4. The RUP for a Team of One: Project Deimos. A Solo Software Project: Project Deimos. The Seminal Idea (Saturday Night). The Proposal (Monday Morning). The Vision. The Plan. The Risk List. The Business Case. The Architecture. The Commitment (Monday Lunch). The Vision, Take Two. The Plan, Take Two. The Risk List, Take Two. The Business Case, Take Two. Digging In (Later Monday). Pressing On (Tuesday). More Progress, More Changes (Wednesday). Nearing Completion (Thursday). Beta and Ship (Friday). Conclusion. II. THE LIFECYCLE OF A RATIONAL UNIFIED PROCESS PROJECT. 5. Going Through the Four Phases. A Major Misconception. Major Milestones. No Fixed Workflows. No Frozen Artifacts. Three Types of Projects. 6. The Inception Phase. Objectives of the Inception Phase. Inception and Iterations. Objective 1: Understand What to Build. Produce a Vision Document. Generate a “Mile-Wide, Inch-Deep” Description. Hold a Workshop or Brainstorming Session...
