Content
Stage 1: Project Initiation to Mid Concept
What should be achieved ?
- Through Life Capability Management (TLCM) outputs reviewed.
- Stakeholder identified.
- Requirements and Acceptance documents created.
- Requirements and Acceptance Management Plan (RAMP) drafted.
- Requirements captured.
- Risks Management in place.
Pre-requisites
Several pre-requisites should exist at this stage formed from the TLCM process. The Sponsor will have identified a ‘Capability Gap’ and put in place actions to correct it.
The pre-requisites are:
- A Concept of Employment (CONEMP).
- A documented Single Statement of Need (SSON).
- A Concept of Analysis that identifies options to evaluate in the concept stage.
- A project team or within DE&S an IPT identified or the Future Business Group (FBG) tasked to initiate a project.
- MODAF Models or similar architectures.
- DLoD Management plan.
What steps should be performed ?
Within the project team the Sponsor allocates the Requirements Manager role including project managers with requirements responsibilities. The task of meeting the needs of the Sponsor then starts, introducing the necessary changes to meet the identified capability gap.
The following activities need performing:
- Assess the fitness-for-purpose of the source documents.
- Identify key capability users and stakeholders, with evidence of engagement and agreement of the intended approach.
- Document or reference the Requirements and Acceptance Management Plan (RAMP) within the Through Life Management Plan (TLMP) to define the approach to managing requirements and acceptance. Do this within the context of a System Engineering Strategy if appropriate.
- Initiate the user requirements documentation, if not already completed as part of TLCM.
- Research and populate Part 1 of the User Requirements Document (URD).
- Qualify and clarify assumptions and record in the Master Data and Assumption List (MDAL).
- Conduct the first iteration of the User Requirements Definition Process. The focus should be on bounding and defining the context of the capability gap.
- Capture requirements, analyse for relevance and clarity, and engineer into the URD Part 3.
- Identify and capture the user’s operational needs and express as effect-based, technology independent requirements.
- Prioritise individual user requirements.
- Add justification and validation criteria.
- Reconcile user requirements to the Acquisition and Acceptance Strategies.
- Identify any requirements that could act as constraints on incremental acquisition.
- Establish a change process for evaluating the overall impact on the deliverables and use it to decide on appropriate updates to the requirements documentation - rather than updates being sporadic responses to new requests.
Notes
The capability gap investigations may have included development of an architecture or model to aid in the elicitation of requirements - MODAF models may reveal interfaces that need to be considered.
This stage establishes how capability requirements are captured and refined throughout the project lifecycle but the process is iterative with requirements being refined and reviewed in subsequent stages.
