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

Programme or Project Team Responsibilities

What are the responsibilities of the IPT Leader ?

The responsibilities of the IPT leader through the IPT are to:

Area	Responsibilities
Requirements	Sponsor and own an SRD for a new operational capability, or for an upgrade or update to an existing operational capability. Evolve the SRD and its associated Statement of Requirement or Equipment Contract Specification(s), and any related Terms and Conditions needed within the contract. Ensure cohesiveness across project boundaries where compatibility or interoperability is an issue. Assist the Sponsor in obtaining approval to proceed into Assessment and Demonstration. Ensure that the Requirements and Acceptance strategy is pragmatic from an acquisition perspective, and maintained through life as part of the revision of the TLMP or RAMP. Negotiate and agree the CSAs with the Sponsor. Host the Requirements Manager and ensure appropriate project management support for that role. Establish the necessary SLAs with interdependent projects or IPTs. Secure necessary involvement of potential suppliers and external assistance.
ITEA	Assist the capability Acceptance Authority (AA) in formulating the acceptance strategy and developing the Integrated Test, Evaluation and Acceptance Plan (ITEAP). Act as the Acceptance Authority for Contract Acceptance. Project-manage the conduct of Validation and Verification activities, including collecting and presenting validation evidence to the Acceptance Authority. Deliver the verified lead DLoD into the validation programme (for an equipment acquisition this is the Equipment DLoD). (including training solution and support equipment) Engineer and document the Validation and Verification programme within the ITEAP, ensuring its cohesiveness with the Acceptance Strategy, its achievability and affordability. Monitor delivery (in accordance with the CSAs) of the non-equipment DLoD into the validation programme through the TLCM process in conjunction with the lead Sponsor.
Acceptance	Project-manage the validation programme including the management of provisos. Collect and submit validation test evidence to the AA for evaluation, and respond to AA requests for remedial action, including resolution of provisos. Ensure cohesiveness of Supplier test plans with the project ITEAP and any other Test and Evaluation activity. Reflect the agreed ITEAP in the prime equipment or system contract, and other facilitating contracts as required. Project-manage the implementation of the ITEAP, ensuring availability of resources including test articles and GFA to testers. Project-manage remedial action extending beyond the prime contractor's responsibility, and its implications on capability cost and time. Collate, evaluate and manage test evidence, and recommend System Acceptance to the AA when evidence permits. Decide when contract acceptance is achieved, and inform key stakeholders when it is achieved.

What are the responsibilities of the Requirements Manager ?

The role of Requirements Manager is pivotal in the delivery of the capability across the DLoDs, acting as the Sponsor’s officer within the IPT. The following table details the responsibilities - some of the functions may be carried out by a dedicated Acceptance Manager for a large project.

The responsibilities of the Requirements Manager are to:

Area	Responsibilities
Planning	Act as the Sponsor’s representative for acceptance in the IPT. Conduct requirements management planning and requirements management on behalf of the Sponsor and IPTL.
Requirements	Manage the evolution of the URD through-life on behalf of the Sponsor. Manage the evolution of the SRD through-life on behalf of the IPTL. Ensure cohesiveness across SRD boundaries where compatibility or interoperability is an issue. Determine the Verification Criteria applied to each candidate System Requirement to enable the validation of the User requirements - in practice the Requirements Manager may substantially assist the Sponsor in setting validation criteria.
Acceptance	Sit on the Programme or Project Boards and CMG or CPGs as appropriate to give acceptance lead through the delivery of ITEA. Ensure that every atomised candidate System Requirement is testable. Determine the Verification Criteria applied to each candidate System Requirement. Endeavour - with the IPTL - to resolve any conflicts between Verification Criteria and the budget and time available to satisfy them. Refers – with the IPTL - any un-resolvable conflicts to the Sponsor.

Change History

Change History