• Introduction to OpenUP
  • Core Principles
    • Balance competing priorities to maximize stakeholder value
    • Collaborate to align interests and share understanding
    • Focus on the architecture early to minimize risks and organize development
    • Evolve to continuously obtain feedback and improve
  • Minimal, Complete, and Extensible
  • Iteration Lifecycle
  • Micro-Increments
  • Project Lifecycle
  • The OpenUP Family
  • Who Should Use OpenUP
• Getting Started
  • OpenUP Roadmap
  • Resources for Modifying Methods
  • Resources for Contributing to OpenUP
• OpenUP Disciplines
  • Architecture
    • Tasks
      • Envision the Architecture
      • Evolve the Architecture
  • Development
    • Tasks
      • Design the Solution
      • Implement Developer Tests
      • Implement Solution
      • Integrate and Create Build
      • Run Developer Tests
  • Project Management
    • Tasks
      • Assess Results
      • Manage Iteration
      • Plan Iteration
      • Plan Project
      • Request Change
  • Requirements
    • Tasks
      • Detail System-Wide Requirements
      • Detail Use-Case Scenarios
      • Develop Technical Vision
      • Identify and Outline Requirements
  • Test
    • Tasks
      • Create Test Cases
      • Implement Tests
      • Run Tests
• OpenUP Work Products
  • Architecture
    • Architecture Notebook
      • Responsible Role
        • Architect
      • Containing Work Product
        • [Technical Architecture]
      • Input to
        • Evolve the Architecture
      • Output from
        • Envision the Architecture
        • Evolve the Architecture
      • Guidance
        • Architecture Notebook
        • Software Architecture
        • Modeling the Architecture
        • Architecture Notebook
  • Development
    • Build
      • Responsible Role
        • Developer
      • Output from
        • Integrate and Create Build
      • Guidance
        • Continuous Integration
        • Continuous Integration
    • Design
      • Responsible Role
        • Developer
      • Containing Work Product
        • [Software Design]
      • Input to
        • Design the Solution
      • Output from
        • Design the Solution
      • Guidance
        • Design
        • Design
        • Designing Visually
        • Design
    • Developer Test
      • Responsible Role
        • Developer
      • Input to
        • Run Developer Tests
        • Implement Solution
      • Output from
        • Implement Developer Tests
      • Guidance
        • Test Driven Development
    • Implementation
      • Responsible Role
        • Developer
  • Project Management
    • Iteration Plan
      • Responsible Role
        • Project Manager
      • Containing Work Product
        • [Project Work]
      • Input to
        • Assess Results
        • Manage Iteration
        • Plan Iteration
      • Output from
        • Plan Iteration
        • Assess Results
        • Manage Iteration
      • Guidance
        • Iteration
        • Iteration Burndown Report
        • Iteration Plan
        • Iteration Burndown
        • Iteration Plan
    • Project Plan
      • Responsible Role
        • Project Manager
      • Containing Work Product
        • [Project Definition and Scope]
      • Output from
        • Plan Project
      • Guidance
        • Project Burndown Report
        • Project Plan
        • Project Burndown
        • Project Plan
    • Risk List
      • Responsible Role
        • Project Manager
      • Input to
        • Manage Iteration
        • Plan Iteration
      • Output from
        • Manage Iteration
        • Plan Iteration
      • Guidance
        • Risk List
        • Risk
        • Risk List
    • Work Items List
      • Responsible Role
        • Project Manager
      • Input to
        • Assess Results
        • Manage Iteration
        • Plan Iteration
      • Output from
        • Assess Results
        • Manage Iteration
        • Plan Iteration
      • Guidance
        • Work Items List
        • Work Items List
  • Requirements
    • Glossary
      • Responsible Role
        • Analyst
      • Output from
        • Detail System-Wide Requirements
        • Detail Use-Case Scenarios
        • Identify and Outline Requirements
    • System-Wide Requirements
      • Responsible Role
        • Analyst
      • Input to
        • Detail System-Wide Requirements
      • Output from
        • Detail System-Wide Requirements
        • Identify and Outline Requirements
      • Guidance
        • Writing Requirements Statements
        • System-Wide Requirements Specification
    • Use Case
      • Responsible Role
        • Analyst
      • Input to
        • Detail Use-Case Scenarios
        • Detail System-Wide Requirements
      • Output from
        • Detail Use-Case Scenarios
        • Identify and Outline Requirements
      • Guidance
        • Use Case
        • Use Case
        • Use-Case Specification
    • Use-Case Model
      • Responsible Role
        • Analyst
      • Contained Work Products
        • Use Case
          • Use Case
          • Use Case
          • Use-Case Specification
      • Output from
        • Detail Use-Case Scenarios
        • Identify and Outline Requirements
      • Guidance
        • Use-Case Model
        • Use Case
        • Use-Case Model
        • Actor
    • Vision
      • Responsible Role
        • Analyst
      • Input to
        • Develop Technical Vision
      • Output from
        • Develop Technical Vision
      • Guidance
        • Vision
        • Vision
  • Test
    • Test Case
      • Responsible Role
        • Tester
      • Input to
        • Implement Tests
        • Create Test Cases
      • Output from
        • Create Test Cases
      • Guidance
        • Test Case
        • Types of Test
        • Test Case
    • Test Log
      • Responsible Role
        • Tester
      • Output from
        • Run Tests
    • Test Script
      • Responsible Role
        • Tester
      • Input to
        • Run Tests
        • Integrate and Create Build
        • Implement Tests
      • Output from
        • Implement Tests
      • Guidance
        • Test Data
        • Test Script
        • Test Suite
        • Programming Automated Tests
        • Maintaining Automated Test Suite
        • Test Script
• OpenUP Roles
  • Analyst
    • Primarily Performs
      • Develop Technical Vision
      • Detail System-Wide Requirements
      • Detail Use-Case Scenarios
      • Identify and Outline Requirements
    • Additionally Performs
      • Assess Results
      • Manage Iteration
      • Plan Iteration
      • Plan Project
      • Create Test Cases
      • Implement Tests
      • Envision the Architecture
      • Design the Solution
    • Responsible For
      • Glossary
      • System-Wide Requirements
        • Writing Requirements Statements
        • System-Wide Requirements Specification
      • Use-Case Model
        • Use Case
          • Use Case
          • Use Case
          • Use-Case Specification
        • Use-Case Model
        • Use Case
        • Use-Case Model
        • Actor
      • Use Case
        • Use Case
        • Use Case
        • Use-Case Specification
      • Vision
        • Vision
        • Vision
    • Modifies
      • Vision
        • Vision
        • Vision
      • System-Wide Requirements
        • Writing Requirements Statements
        • System-Wide Requirements Specification
      • Glossary
      • Use Case
        • Use Case
        • Use Case
        • Use-Case Specification
      • Use-Case Model
        • Use Case
          • Use Case
          • Use Case
          • Use-Case Specification
        • Use-Case Model
        • Use Case
        • Use-Case Model
        • Actor
  • Any Role
    • Primarily Performs
      • Request Change
  • Architect
    • Primarily Performs
      • Envision the Architecture
      • Evolve the Architecture
    • Additionally Performs
      • Assess Results
      • Manage Iteration
      • Plan Iteration
      • Plan Project
      • Design the Solution
      • Develop Technical Vision
      • Detail System-Wide Requirements
      • Detail Use-Case Scenarios
      • Identify and Outline Requirements
    • Responsible For
      • Architecture Notebook
        • Architecture Notebook
        • Software Architecture
        • Modeling the Architecture
        • Architecture Notebook
    • Modifies
      • Architecture Notebook
        • Architecture Notebook
        • Software Architecture
        • Modeling the Architecture
        • Architecture Notebook
  • Developer
    • Primarily Performs
      • Integrate and Create Build
      • Design the Solution
      • Implement Developer Tests
      • Implement Solution
      • Run Developer Tests
    • Additionally Performs
      • Assess Results
      • Manage Iteration
      • Plan Iteration
      • Plan Project
      • Create Test Cases
      • Implement Tests
      • Envision the Architecture
      • Evolve the Architecture
      • Detail System-Wide Requirements
      • Detail Use-Case Scenarios
      • Identify and Outline Requirements
    • Responsible For
      • Implementation
      • Build
        • Continuous Integration
        • Continuous Integration
      • Design
        • Design
        • Design
        • Designing Visually
        • Design
      • Developer Test
        • Test Driven Development
    • Modifies
      • Build
        • Continuous Integration
        • Continuous Integration
      • Design
        • Design
        • Design
        • Designing Visually
        • Design
      • Developer Test
        • Test Driven Development
      • [Software Implementation]
        • Implementation
        • Build
          • Continuous Integration
          • Continuous Integration
      • [Technical Specification]
        • [Requirements]
          • Use Case
            • Use Case
            • Use Case
            • Use-Case Specification
          • System-Wide Requirements
            • Writing Requirements Statements
            • System-Wide Requirements Specification
          • Use-Case Model
            • Use Case
              • Use Case
              • Use Case
              • Use-Case Specification
            • Use-Case Model
            • Use Case
            • Use-Case Model
            • Actor
        • Glossary
        • Vision
          • Vision
          • Vision
      • [Technical Test Results]
        • Test Log
  • Project Manager
    • Primarily Performs
      • Assess Results
      • Manage Iteration
      • Plan Iteration
      • Plan Project
    • Additionally Performs
      • Envision the Architecture
      • Evolve the Architecture
      • Develop Technical Vision
    • Responsible For
      • Risk List
        • Risk List
        • Risk
        • Risk List
      • Iteration Plan
        • Iteration
        • Iteration Burndown Report
        • Iteration Plan
        • Iteration Burndown
        • Iteration Plan
      • Work Items List
        • Work Items List
        • Work Items List
      • Project Plan
        • Project Burndown Report
        • Project Plan
        • Project Burndown
        • Project Plan
    • Modifies
      • Iteration Plan
        • Iteration
        • Iteration Burndown Report
        • Iteration Plan
        • Iteration Burndown
        • Iteration Plan
      • Work Items List
        • Work Items List
        • Work Items List
      • Risk List
        • Risk List
        • Risk
        • Risk List
      • Project Plan
        • Project Burndown Report
        • Project Plan
        • Project Burndown
        • Project Plan
  • Stakeholder
    • Additionally Performs
      • Assess Results
      • Manage Iteration
      • Plan Iteration
      • Plan Project
      • Create Test Cases
      • Implement Tests
      • Envision the Architecture
      • Design the Solution
      • Develop Technical Vision
      • Implement Solution
      • Detail System-Wide Requirements
      • Detail Use-Case Scenarios
      • Identify and Outline Requirements
  • Tester
    • Primarily Performs
      • Create Test Cases
      • Implement Tests
      • Run Tests
    • Additionally Performs
      • Assess Results
      • Manage Iteration
      • Plan Iteration
      • Plan Project
      • Design the Solution
      • Implement Developer Tests
      • Implement Solution
      • Detail System-Wide Requirements
      • Detail Use-Case Scenarios
      • Identify and Outline Requirements
    • Responsible For
      • Test Case
        • Test Case
        • Types of Test
        • Test Case
      • Test Log
      • Test Script
        • Test Data
        • Test Script
        • Test Suite
        • Programming Automated Tests
        • Maintaining Automated Test Suite
        • Test Script
    • Modifies
      • Test Case
        • Test Case
        • Types of Test
        • Test Case
      • Test Script
        • Test Data
        • Test Script
        • Test Suite
        • Programming Automated Tests
        • Maintaining Automated Test Suite
        • Test Script
      • Test Log
• OpenUP Lifecycle
  • Inception Phase Iteration [1..n]
    • Initiate Project
    • Plan and Manage Iteration
    • Identify and Refine Requirements
    • Agree on Technical Approach
  • Lifecycle Objectives Milestone
  • Elaboration Phase Iteration [1..n]
    • Plan and Manage Iteration
    • Identify and Refine Requirements
    • Develop the Architecture
      • Develop Solution Increment
    • Develop Solution Increment
    • Test Solution
    • Ongoing Tasks
  • Lifecycle Architecture Milestone
  • Construction Phase Iteration [1..n]
    • Plan and Manage Iteration
    • Identify and Refine Requirements
    • Develop Solution Increment
    • Test Solution
    • Ongoing Tasks
  • Initial Operational Capability Milestone
  • Transition Phase Iteration [1..n]
    • Plan and Manage Iteration
    • Develop Solution Increment
    • Test Solution
    • Ongoing Tasks
  • Product Release Milestone
• Guidance
  • Checklists
    • Actor
    • Architecture Notebook
    • Design
    • General Requirements
    • Implementation
    • Iteration Plan
    • Project Plan
    • Risk List
    • System-Wide Requirements
    • Test Case
    • Test Data
    • Test Script
    • Use Case
    • Use-Case Model
    • Vision
    • Work Items List
  • Concepts
    • Actor
    • Analysis Mechanism
    • Architectural Constraints
    • Architectural Goals
    • Architectural Mechanism
    • Architectural Views and Viewpoints
    • Architecturally Significant Requirements
    • Balance competing priorities to maximize stakeholder value
    • Business Pattern
    • Change Requests
    • Change Set
    • Coding Standard
    • Collaborate to align interests and share understanding
    • Collective Code Ownership
    • Component
    • Construction Phase
    • Continuous Integration
    • Design
    • Design Mechanism
    • Developer Testing
    • Elaboration Phase
    • Evolve to continuously obtain feedback and improve
    • Executable Architecture
    • Failure Analysis and Report Creation
    • Focus on the architecture early to minimize risks and organize development
    • Implementation Mechanism
    • Inception Phase
    • Iteration
    • Iteration Lifecycle
    • Key Abstractions
    • Metrics
    • Micro-Increments
    • Pattern
    • Phase
    • Phase Milestones
    • Project Lifecycle
    • Refactoring
    • Requirement Attributes
    • Requirements
    • Retrospective
    • Risk
    • Software Architecture
    • System-Wide Requirements [needs wording work]
    • Test Driven Development
    • Test Ideas
    • Traceability
    • Transition Phase
    • Types of Test
    • Use Case
    • Use-Case Model
    • Visual Modeling
    • Workspace
  • Examples
    • 4+1 Views of Software Architecture
    • Architectural Mechanism Attributes
    • Architectural Mechanisms
    • Evolution of the Use-Case Model
    • Iteration Burndown Report
    • Iteration Plan
    • Project Burndown Report
    • Project Plan
    • Use-Case Specification
    • Using the TDD Practice in Context
    • Work Items List
  • Guidelines
    • Abstract Away Complexity
    • Agile Estimation
    • Analyze the Design
    • Assign Changes to an Iteration
    • Conduct Project Retrospective
    • Continuous Integration
    • Daily Meetings
    • Deploying the Solution
    • Designing Visually
    • Detail Use Cases and Scenarios
    • Developer Testing
    • Developing System-Wide Requirements Specification
    • Effective Requirement Reviews
    • Entity-Control-Boundary Pattern
    • Evolve the Design
    • Example: Design Mechanisms
    • Identify and Outline Actors and Use Cases
    • Implementation Refactoring
    • Iteration Assessment
    • Iteration Planning
    • Layering
    • Maintain a Sustainable Pace
    • Maintaining Automated Test Suite
    • Managing Risks
    • Managing Work Items
    • Mapping from Design to Code
    • Modeling the Architecture
    • Prioritizing Work Items
    • Programming Automated Tests
    • Promoting Builds
    • Refactoring
    • Representing Interfaces to External Systems
    • Requirement Pitfalls
    • Requirements Gathering Techniques
    • Self-Organize Work Assignments
    • Software Reuse
    • Staffing a Project
    • Test Driven Development
    • Test Ideas
    • Test Suite
    • Transforming design into implementation
    • Use Case Formats
    • Use-Case Model
    • Use-Cases Realizations
    • Using Visual Modeling
    • Writing Requirements Statements
  • Practices
    • Change Management
      • How to Adopt This Practice
      • Request Change
        • Performing Roles
          • Any Role
        • Guidance
          • Submitting Change Requests
      • Submitting Change Requests
    • Continuous Integration
      • Integrate and Create Build
        • Performing Roles
          • Developer
        • Input Work Products
          • Test Script
          • [Software Implementation]
        • Output Work Products
          • Build
        • Guidance
          • Change Set
          • Workspace
          • Continuous Integration
          • Continuous Integration
          • Promoting Builds
      • Build
        • Responsible Role
          • Developer
        • Output from
          • Integrate and Create Build
        • Guidance
          • Continuous Integration
          • Continuous Integration
      • Change Requests
      • Change Set
      • Continuous Integration
      • Workspace
      • Continuous Integration
      • Promoting Builds
    • Evolutionary Architecture
      • How to Adopt This Practice
      • Key Concepts
        • Software Architecture
        • Architectural Mechanism
        • Architectural Views and Viewpoints
      • Work Products
        • Architecture Notebook
          • Responsible Role
            • Architect
          • Containing Work Product
            • [Technical Architecture]
          • Input to
            • Evolve the Architecture
          • Output from
            • Envision the Architecture
            • Evolve the Architecture
          • Guidance
            • Architecture Notebook
            • Software Architecture
            • Modeling the Architecture
            • Architecture Notebook
      • Tasks
        • Envision the Architecture
          • Performing Roles
            • Architect
            • Analyst
            • Developer
            • Project Manager
            • Stakeholder
          • Input Work Products
            • [Technical Specification]
          • Output Work Products
            • Architecture Notebook
          • Guidance
            • Architecturally Significant Requirements
            • Architectural Mechanism
            • Architectural Goals
            • Architectural Constraints
            • Key Abstractions
            • Layering
            • Software Reuse
            • Abstract Away Complexity
            • Modeling the Architecture
        • Evolve the Architecture
          • Performing Roles
            • Architect
            • Developer
            • Project Manager
          • Input Work Products
            • [Technical Specification]
            • Architecture Notebook
            • [Software Design]
            • [Software Implementation]
          • Output Work Products
            • Architecture Notebook
          • Guidance
            • Architectural Mechanism
            • Architecturally Significant Requirements
            • Executable Architecture
            • Architectural Goals
            • Key Abstractions
            • Component
            • Architectural Constraints
            • Software Reuse
            • Representing Interfaces to External Systems
            • Abstract Away Complexity
            • Modeling the Architecture
      • Guidance
        • Guidelines
          • Abstract Away Complexity
          • Modeling the Architecture
          • Software Reuse
        • Checklists
          • Architecture Notebook
        • Templates
          • Architecture Notebook
        • Examples
          • Architectural Mechanism Attributes
          • Architectural Mechanisms
          • 4+1 Views of Software Architecture
      • Evolutionary Architecture Practice
    • Evolutionary Design
      • How to Adopt This Practice
      • Enablement
      • Design the Solution
        • Performing Roles
          • Developer
          • Analyst
          • Architect
          • Stakeholder
          • Tester
        • Input Work Products
          • [Technical Architecture]
          • [Technical Specification]
          • Design
        • Output Work Products
          • Design
        • Guidance
          • Architectural Mechanism
          • Design
          • Design Mechanism
          • Implementation Mechanism
          • Pattern
          • Entity-Control-Boundary Pattern
          • Analyze the Design
          • Evolve the Design
          • Software Reuse
          • Designing Visually
          • [Design Guidance]
      • Design
        • Responsible Role
          • Developer
        • Containing Work Product
          • [Software Design]
        • Input to
          • Design the Solution
        • Output from
          • Design the Solution
        • Guidance
          • Design
          • Design
          • Designing Visually
          • Design
      • Guidance
        • Design
        • Design
        • Analyze the Design
        • Evolve the Design
        • Refactoring
        • Design
    • Independent Testing
      • Tasks
        • Create Test Cases
          • Performing Roles
            • Tester
            • Analyst
            • Developer
            • Stakeholder
          • Input Work Products
            • [Technical Specification]
            • Test Case
          • Output Work Products
            • Test Case
          • Guidance
            • Test Ideas
        • Implement Tests
          • Performing Roles
            • Tester
            • Analyst
            • Developer
            • Stakeholder
          • Input Work Products
            • Test Case
            • Test Script
            • [Software Implementation]
          • Output Work Products
            • Test Script
          • Guidance
            • Test Ideas
            • Maintaining Automated Test Suite
            • Programming Automated Tests
            • Test Ideas
        • Run Tests
          • Performing Roles
            • Tester
          • Input Work Products
            • Test Script
            • [Software Implementation]
          • Output Work Products
            • Test Log
          • Guidance
            • Maintaining Automated Test Suite
            • Programming Automated Tests
            • Test Suite
      • Work Products
        • Test Case
          • Responsible Role
            • Tester
          • Input to
            • Implement Tests
            • Create Test Cases
          • Output from
            • Create Test Cases
          • Guidance
            • Test Case
            • Types of Test
            • Test Case
        • Test Log
          • Responsible Role
            • Tester
          • Output from
            • Run Tests
        • Test Script
          • Responsible Role
            • Tester
          • Input to
            • Run Tests
            • Integrate and Create Build
            • Implement Tests
          • Output from
            • Implement Tests
          • Guidance
            • Test Data
            • Test Script
            • Test Suite
            • Programming Automated Tests
            • Maintaining Automated Test Suite
            • Test Script
      • Guidance
        • Test Ideas
        • Types of Test
        • Test Case
        • Test Data
        • Test Script
        • Maintaining Automated Test Suite
        • Programming Automated Tests
        • Test Ideas
        • Test Suite
    • Iterative Development
      • How to Adopt This Practice
      • Tasks
        • Assess Results
          • Performing Roles
            • Project Manager
            • Analyst
            • Architect
            • Developer
            • Stakeholder
            • Tester
          • Input Work Products
            • Iteration Plan
            • Work Items List
            • [Technical Specification]
            • [Technical Test Results]
            • [Project Definition and Scope]
          • Output Work Products
            • Iteration Plan
            • Work Items List
          • Guidance
            • Retrospective
            • Phase Milestones
            • Conduct Project Retrospective
            • Iteration Assessment
            • Deploying the Solution
            • Use Method Composer to Update the Process
        • Manage Iteration
          • Performing Roles
            • Project Manager
            • Analyst
            • Architect
            • Developer
            • Stakeholder
            • Tester
          • Input Work Products
            • Iteration Plan
            • Risk List
            • Work Items List
            • [Project Definition and Scope]
          • Output Work Products
            • Iteration Plan
            • Risk List
            • Work Items List
          • Guidance
            • Risk
            • Iteration Lifecycle
            • Micro-Increments
            • Metrics
            • Assign Changes to an Iteration
            • [Collaboration Guidance]
            • [Work Assignment Guidance]
        • Plan Iteration
          • Performing Roles
            • Project Manager
            • Analyst
            • Architect
            • Developer
            • Stakeholder
            • Tester
          • Input Work Products
            • Work Items List
            • [Project Definition and Scope]
            • [Technical Architecture]
            • [Technical Specification]
            • Risk List
            • Iteration Plan
          • Output Work Products
            • Risk List
            • Iteration Plan
            • Work Items List
          • Guidance
            • Iteration
            • Micro-Increments
            • Iteration Lifecycle
            • Managing Work Items
            • Agile Estimation
            • Assign Changes to an Iteration
            • Iteration Planning
            • Managing Risks
            • [Project Planning Guidance]
            • Deploying the Solution
      • Work Products
        • Iteration Plan
          • Responsible Role
            • Project Manager
          • Containing Work Product
            • [Project Work]
          • Input to
            • Assess Results
            • Manage Iteration
            • Plan Iteration
          • Output from
            • Plan Iteration
            • Assess Results
            • Manage Iteration
          • Guidance
            • Iteration
            • Iteration Burndown Report
            • Iteration Plan
            • Iteration Burndown
            • Iteration Plan
        • Work Items List
          • Responsible Role
            • Project Manager
          • Input to
            • Assess Results
            • Manage Iteration
            • Plan Iteration
          • Output from
            • Assess Results
            • Manage Iteration
            • Plan Iteration
          • Guidance
            • Work Items List
            • Work Items List
        • Risk List
          • Responsible Role
            • Project Manager
          • Input to
            • Manage Iteration
            • Plan Iteration
          • Output from
            • Manage Iteration
            • Plan Iteration
          • Guidance
            • Risk List
            • Risk
            • Risk List
      • Guidance
        • Iteration Lifecycle
        • Micro-Increments
        • Retrospective
        • Iteration Plan
        • Risk List
        • Work Items List
        • Iteration Burndown Report
        • Iteration Plan
        • Work Items List
        • Agile Estimation
        • Assign Changes to an Iteration
        • Conduct Project Retrospective
        • Iteration Assessment
        • Iteration Planning
        • Managing Risks
        • Managing Work Items
        • Prioritizing Work Items
        • Iteration Burndown
        • Iteration Plan
        • Risk List
        • Work Items List
    • Risk-Value Lifecycle
      • How to Adopt This Practice
      • Risk-Value Lifecycle Phases
        • Inception Iteration [1..n]
        • Lifecycle Objectives Milestone
        • Elaboration Iteration [1..n]
        • Lifecycle Architecture Milestone
        • Construction Iteration [1..n]
        • Initial Operational Capability
        • Transition Iteration [1..n]
        • Product Release Milestone
      • Guidances
        • Balance competing priorities to maximize stakeholder value
        • Collaborate to align interests and share understanding
        • Construction Phase
        • Elaboration Phase
        • Evolve to continuously obtain feedback and improve
        • Focus on the architecture early to minimize risks and organize development
        • Inception Phase
        • Phase
        • Phase Milestones
        • Project Lifecycle
        • Transition Phase
        • Project Burndown Report
        • Project Plan
        • Deploying the Solution
        • Project Burndown
        • Project Plan
    • Shared Vision
      • Develop Technical Vision
        • Performing Roles
          • Analyst
          • Architect
          • Project Manager
          • Stakeholder
        • Input Work Products
          • Vision
        • Output Work Products
          • Vision
        • Guidance
          • Effective Requirement Reviews
          • Requirements Gathering Techniques
      • Vision
        • Responsible Role
          • Analyst
        • Input to
          • Develop Technical Vision
        • Output from
          • Develop Technical Vision
        • Guidance
          • Vision
          • Vision
      • Requirements Gathering Techniques
    • Test-Driven Development
      • How to Adopt this Practice
      • Enablement
      • Using the TDD Practice in Context
      • Tasks
        • Implement Developer Tests
          • Performing Roles
            • Developer
            • Tester
          • Input Work Products
            • [Software Implementation]
            • [Software Design]
          • Output Work Products
            • Developer Test
          • Guidance
            • Developer Testing
        • Run Developer Tests
          • Performing Roles
            • Developer
          • Input Work Products
            • [Software Implementation]
            • Developer Test
          • Output Work Products
            • [Technical Test Results]
          • Guidance
            • Developer Testing
        • Implement Solution
          • Performing Roles
            • Developer
            • Stakeholder
            • Tester
          • Input Work Products
            • [Software Design]
            • [Technical Specification]
            • [Software Implementation]
            • Developer Test
          • Output Work Products
            • [Software Implementation]
            • [Technical Specification]
          • Guidance
            • Refactoring
            • Mapping from Design to Code
      • Work Products
        • Developer Test
          • Responsible Role
            • Developer
          • Input to
            • Run Developer Tests
            • Implement Solution
          • Output from
            • Implement Developer Tests
          • Guidance
            • Test Driven Development
        • Implementation
          • Responsible Role
            • Developer
      • Guidance
        • Coding Standard
        • Collective Code Ownership
        • Developer Testing
        • Refactoring
        • Test Driven Development
        • Implementation
        • Developer Testing
        • Implementation Refactoring
        • Mapping from Design to Code
        • Test Driven Development
        • Transforming design into implementation
        • Test Driven Development
        • How to Adopt this Practice
    • Two-Level Project Planning
      • How to Adopt This Practice
      • Plan Project
        • Performing Roles
          • Project Manager
          • Analyst
          • Architect
          • Developer
          • Stakeholder
          • Tester
        • Input Work Products
          • [Technical Specification]
        • Output Work Products
          • Project Plan
        • Guidance
          • Iteration
          • Risk
          • Phase Milestones
          • Staffing a Project
          • Agile Estimation
          • Managing Risks
          • [Project Planning Guidance]
      • Project Plan
        • Responsible Role
          • Project Manager
        • Containing Work Product
          • [Project Definition and Scope]
        • Output from
          • Plan Project
        • Guidance
          • Project Burndown Report
          • Project Plan
          • Project Burndown
          • Project Plan
      • Guidance
        • Metrics
        • Project Plan
        • Staffing a Project
    • Use-Case Driven Development
      • How to Adopt this Practice
      • Enablement
      • Key Concepts
        • Requirements
        • Use Case
        • Actor
        • Use-Case Model
      • Work Products
        • Use Case
          • Responsible Role
            • Analyst
          • Input to
            • Detail Use-Case Scenarios
            • Detail System-Wide Requirements
          • Output from
            • Detail Use-Case Scenarios
            • Identify and Outline Requirements
          • Guidance
            • Use Case
            • Use Case
            • Use-Case Specification
        • Use-Case Model
          • Responsible Role
            • Analyst
          • Contained Work Products
            • Use Case
              • Use Case
              • Use Case
              • Use-Case Specification
          • Output from
            • Detail Use-Case Scenarios
            • Identify and Outline Requirements
          • Guidance
            • Use-Case Model
            • Use Case
            • Use-Case Model
            • Actor
        • System-Wide Requirements
          • Responsible Role
            • Analyst
          • Input to
            • Detail System-Wide Requirements
          • Output from
            • Detail System-Wide Requirements
            • Identify and Outline Requirements
          • Guidance
            • Writing Requirements Statements
            • System-Wide Requirements Specification
      • Tasks
        • Identify and Outline Requirements
          • Performing Roles
            • Analyst
            • Architect
            • Developer
            • Stakeholder
            • Tester
          • Input Work Products
            • [Technical Specification]
          • Output Work Products
            • System-Wide Requirements
            • Use Case
            • Glossary
            • Use-Case Model
          • Guidance
            • Requirements
            • System-Wide Requirements [needs wording work]
            • Identify and Outline Actors and Use Cases
            • Developing System-Wide Requirements Specification
            • Requirements Gathering Techniques
            • Effective Requirement Reviews
        • Detail Use-Case Scenarios
          • Performing Roles
            • Analyst
            • Architect
            • Developer
            • Stakeholder
            • Tester
          • Input Work Products
            • Use Case
          • Output Work Products
            • Use Case
            • Glossary
            • Use-Case Model
          • Guidance
            • Detail Use Cases and Scenarios
            • Use Case Formats
            • Effective Requirement Reviews
        • Detail System-Wide Requirements
          • Performing Roles
            • Analyst
            • Architect
            • Developer
            • Stakeholder
            • Tester
          • Input Work Products
            • System-Wide Requirements
            • Use Case
          • Output Work Products
            • System-Wide Requirements
            • Glossary
          • Guidance
            • Developing System-Wide Requirements Specification
            • Effective Requirement Reviews
      • Guidance
        • Detail Use Cases and Scenarios
        • Identify and Outline Actors and Use Cases
        • Developing System-Wide Requirements Specification
        • Use Case Formats
        • Use-Cases Realizations
    • Whole Team
      • How to Adopt This Practice
      • Guidance
        • Daily Meetings
        • Maintain a Sustainable Pace
        • Self-Organize Work Assignments
  • Reports
    • Iteration Burndown
    • Project Burndown
  • Roadmaps
    • How to Adopt this Practice
    • How to Adopt this Practice
    • How to Adopt This Practice
    • How to Adopt This Practice
    • How to Adopt This Practice
    • How to Adopt This Practice
    • How to Adopt This Practice
    • How to Adopt This Practice
  • Templates
    • Architecture Notebook
    • Design
    • Iteration Plan
    • Project Plan
    • Risk List
    • System-Wide Requirements Specification
    • Use-Case Specification
    • Vision
    • Work Items List
  • Tools
    • Method Composer
      • Use Method Composer to Update the Process
  • White Papers
    • Test Driven Development
• About
  • About OpenUP
• OpenUP Copyright