MOD Crest
AOF Requirements and Acceptance

Policy, information and guidance on the Requirements and Acceptance aspects of UK MOD Defence Acquisition

version 1.0.2 - July 2010

Content

Stage 2: Mid to End of Concept

What should be achieved ?

  • Stakeholder analysis updated.
  • Requirements and Acceptance Management Plan (RAMP) completed.
  • Measures of Effectiveness (MoE) added to User Requirements Document (URD).
  • Initial ‘within solution’ trading carried out.
  • System Requirements Document (SRD) outline drafted.
  • Candidates for Key User Requirements (KUR) identified.
  • Validation criteria added to URD.
  • URD Parts 4 and 5 drafted.
  • Time and cost boundaries set.

What steps should be performed ?

Stakeholders
  • If new stakeholders emerge or withdraw amend the stakeholder matrix as requirements capture matures.
User Requirements
  • Develop the RAMP.
  • Draft Part 4 and 5 of the URD.
  • Identify an 'owner' and 'user' for every requirement.
  • Start to identify candidates for Key User Requirements from Part 3 of the URD, using these to draft Part 2 of the URD.
  • Agree a plan for maturing them and the associated doctrine and Concepts of Use (CONUSE).
  • Develop the URD to include objective MOEs, setting threshold and objective values to allow for ‘within solution / DLoD’ trading and acceptance activities.
  • Perform initial ‘within solution / DLoD’ trading.
  • Further develop the validation criteria for inclusion in the URD.
  • Repeat the process of defining the URD.
  • Co-ordinate requirements updates agreed through meetings of the sponsor and customer.
  • Develop the URD to include mandatory requirements and constraints. There should be evidence of engagement of Subject Matter Experts (SMEs) in formulating these requirements.
  • Identify mandatory interoperability requirements (JSP 600External link to Ministry of Defence Intranet content) for projects with CIS content in the URD and manage across platforms.
System Requirements
  • Start developing and drafting the System Requirements Document (SRD) - include the main areas for meeting the user requirements and other lines of development.
  • Carry out initial studies of available outcomes, if not already completed by the DEC in the capability planning stages – ensure these are non-solution dependant.
  • Complete concept studies to validate the decision to proceed with the capability requirement.
  • Complete the Combined Operational Effectiveness and Investment Appraisal (COEIA) or balance of investment study to ensure there is adequate evidence available for discounting options.
  • Identify and evaluate potential solutions for Initial Gate.
Project
  • Establish time and cost boundaries for the project as a whole.
  • Allocate the Acceptance Manager role or if appropriate allocate Acceptance responsibilities as secondary duties to the Project or Requirements Management staff.
  • Initiate the Initial Gate Business Case with the Project Management staff.
  • Establish initial engagement of Industry to identify and select options.
  • Review the DLoD management plan.

Notes

There should be evidence of appropriate engagement with stakeholders.

The URD should be traceable from Parts 1-3 to the Capability Audit, Operational Analysis (OA), Concept of Employment (CONEMP) and supporting documents.

Use the context of a Systems Engineering Strategy if appropriate.

MOEs are used in the ‘within solution’ trade off process and the Acceptance process, so it is important that they are measurable, that they have direct units of measure and that they do not rely on subjective assessment.

Change History

Change History