Lifecycle Management
Domain 8 tests lifecycle management: planning across stages, using decision gates, controlling configuration, and transitioning the system into operation and support.
Core rules and concepts
- ISO/IEC/IEEE 15288 describes life cycle stages from concept through retirement. Stages are decision points with evidence, not bureaucratic calendar phases.
- Technical management processes include planning, measurement, risk, configuration, information, and decision management.
- Configuration management maintains consistency among requirements, design, and evidence as changes occur.
- Transition and operation require support concepts: training, spares, maintenance, disposal, and feedback into the next increment.
Worked example
At a preliminary design gate, the team has a design but no verified interface control documents and an open safety risk. The gate decision is "conditional continue" with actions and a re-review date. Reasoning: the gate assesses evidence and risk, not presentation quality. Continuing unconditionally would carry an unowned interface and an unaccepted hazard into detailed design.
Traps that cost marks
- Treating gates as calendar milestones rather than evidence reviews.
- Ignoring through-life cost and support.
- Letting configuration drift after design freeze.
- Confusing a project schedule with a life cycle model.
- Planning transition without training, spares, or maintenance.
Key points
- Stages are evidence-based decisions.
- Technical management spans the lifecycle.
- Configuration control preserves consistency.
- Transition needs support concepts.
- Gates assess risk, not slides.