Clause 6.2.3.6: Manage the business or mission analysis
Two tasks close the process.
What clause 6.2.3.6 asks
Two tasks close the process. The first is to maintain traceability from the business or mission needs and requirements to the problems and opportunities, the preferred solution classes and the stakeholder needs. The second is to provide the key artefacts and information items selected for baselines: the preliminary life cycle concepts, the trade study reports and the supporting analysis. The traceability has to survive the life of the system, not only the study.
Why it matters
Traceability at this level is what lets a later reviewer see why the project exists. Without it, the requirements work starts from an undocumented decision. The baseline artefacts are the ones the next process will use, so they need configuration control like any other requirement information.
No clause level change is public for this unit; the DIS keeps the title and scope, and the requirement text is not released.
What good looks like
Put the problem, the classes, the decision and the concepts into one baselined pack. Give it an identifier and a version. Link it to the project authorization and to the first stakeholder requirements.
Evidence an assessor asks for
The assessor will follow a stakeholder requirement back to the mission need. If the chain breaks at the project charter, the analysis is not traceable.
- Baselined analysis pack The problem, classes, decision, concepts and supporting analysis, with an identifier and version
- Traceability matrix The links from the mission need to the classes and to the first stakeholder needs
- Trade study record The studies used in the assessment, with their assumptions and results
- Configuration record The approval and change history of the pack
Where it commonly fails
- The analysis pack lives in a shared folder with no version or owner
- Traceability stops at the project charter, which has no problem statement
- The trade study is cited but cannot be found
What to do before the revision
Give the pack an identifier on the cover and reference it from every later requirement. A single identifier is enough to make the chain visible.
Read across
- 6.2.1 Purpose: business or mission analysis
- 6.2.3.5 Evaluate alternative solution classes
- 6.3.3.7 Manage stakeholder needs and requirements
- 6.6.2.2.2 Configuration identification
← 6.2.3.5 Evaluate alternative solution classes 6.3.1 Purpose: stakeholder needs and requirements definition →
Source for clause 6.2.3.6: ISO/IEC/IEEE 29148:2018, Clause 6.2.3.6, retrieved 19 October 2026. The revision note rests on ISO page 94091. The requirement, evidence and gaps are written from our record. Every source.