Explorer

• Introduction to Requirements and Acceptance
• Organisations, Roles and Responsibilities
  • Organisations and Groups
  • Sponsor and User Responsibilities
  • Programme or Project Responsibilities
  • Stakeholder Responsibilities
• Principles
  • Requirements Management Principles
  • The Requirement and Acceptance Management Plan (RAMP)
    • RAMP: Requirements and Acceptance Strategies
    • RAMP: Management Aspects
  • User Requirements Principles
    • Key User Requirements (KUR) Principles
    • User Requirements Document (URD) Principles
  • System Requirements Principles
    • System Requirements Document (SRD) Principles
  • Effectiveness Envelope
  • Test, Evaluation and Acceptance Principles
    • Test and Evaluation Principles
    • Acceptance Principles
    • Integrated Test, Evaluation and Acceptance (ITEA) Principles
    • Verification and Validation
• Processes
  • Requirements Management Tasks
  • User Requirements Definition
    • Defining User Requirements: the Six Tasks
    • User Requirements Capture: Areas to Consider
    • User Requirements: Review Checks
  • System Requirements Definition
    • Defining System Requirements: the Six Tasks
    • System Requirements: Define Constraints
    • System Requirements: Review Checks
    • Do's and Don'ts when Defining System Requirements
  • Requirements and Acceptance Evolution
    • Stage 1: Project Initiation to Mid Concept
    • Stage 2: Mid to End of Concept
    • Stage 3: Initial gate to End of Concept
    • Stage 4: Start to Mid Assessment
    • Stage 5: Mid Assessment to Start of Demonstration
    • Stage 6: Start to End of Demonstration
    • Stage 7: End of Demonstration
    • Stage 8: Start of in-service to FOC
    • Stage 9: In Service (FOC)
  • Integrated Test, Evaluation and Acceptance (ITEA) Process
    • ITEA Process: the Six Tasks
• Products
  • Requirements and Acceptance Management Plan (RAMP)
  • User Requirements Document (URD)
    • URD Part 1: General Description
    • URD Part 2: Key User Requirements
    • URD Part 3: Individual Capability Requirements and Constraints
    • URD Parts 4 and 5: Context Documents and Glossary
    • User Requirements: Recommended Core Attributes
  • System Requirements Document (SRD)
    • SRD Part 1: General Description
    • SRD Part 2: Key System Requirements
    • SRD Part 3: Individual System Requirements and Constraints
    • SRD Parts 4 and 5: Context Documents and Glossary
    • System Requirements: Recommended Core Attributes
  • Integrated Test, Evaluation and Acceptance Plan (ITEAP)
    • ITEAP Schedule
    • Verification and Validation Requirements Matrix (VVRM)
• Resources
  • Acronyms
  • Glossary

Content

Requirements and Acceptance Management Plan (RAMP) Structure

A Requirements and Acceptance Management Plan (RAMP) covers:

• Introduction and overview
• Planning for Requirements
• Planning for Acceptance
• Requirements and Acceptance Process
• Products:
  • User Requirements Document (URD)
  • Systems Requirements Document (SRD)
  • Integrated Test Evaluation and Acceptance Plan (ITEAP) .

Introduction and overview

This should set out the principles of how the requirements and acceptance activities are going to be completed. Reasons for why a project does not comply with the guidance should be highlighted.

Planning for Requirements

• Who will carry out the process of identifying the Requirements?
• Will there need to be any third party or specialist contractor involvement? If so, describe what contractual mechanism will be used to enable this.
• How will the identified Requirements be prioritised, and what role will stakeholders play in agreeing this?
• Who will confirm that the Measures of Effectiveness (MoEs) and Measures of Performance (MoPs) reflect planning assumptions and capability need?

Planning for Acceptance

• Who will carry out the process of Acceptance, and what contractual mechanism will be used to enable this?
• Has the scope and type of the evidence to be collected been agreed with key stakeholders, and confirmed with relevant technical experts as sufficient?
• When will the testing be completed, and will this be representative of the final product?
• Will all products be tested, or will this be limited to a percentage of products or factory tests of component performance?
• How will pass / fail criteria be established as part of any test plan, and how will successful testing be planned and scheduled to inform the acceptance process?

Requirement and Acceptance Process

This section should set out the process to follow from requirements to acceptance:

• Scoping of Requirement
• Requirements elicitation (Systems Engineering, Expert Panel)
• Requirements prioritisation
• Requirements testing
• Acceptance case construction
• Process of acceptance agreement
• Final acceptance.

Products

The RAMP should identify what products will be produced to support the Requirements and Acceptance process.

As a minimum they should include:

• User Requirements Document (URD)
• System Requirements Document (SRD)
• Integrated Test, Evaluation and Acceptance Plan (ITEAP)
• Verification and Validation Requirements Matrix.

Change History

Change History