ISO / IEC / IEEE 15288 — System lifecycle
Understand the common system lifecycle process framework and use it to organise disciplined work from stakeholder needs through operation, maintenance and disposal.
After this module, you should be able to:
- Describe the purpose of a lifecycle process framework
- Distinguish agreement, organisational, technical-management and technical processes
- Tailor processes to product context and risk
- Connect lifecycle information items to real engineering decisions
15288 provides a process vocabulary, not a single development model.
ISO / IEC / IEEE 15288 defines processes for the lifecycle of human-made systems. It spans acquisition and supply, organisational support, technical management and technical processes from business analysis and stakeholder needs through design, transition, operation, maintenance and disposal.
The processes can be used with iterative, incremental, sequential or hybrid lifecycles. Tailoring selects appropriate outcomes, activities and information items for the system, organisation, risk and contractual context; it should be explicit and justified.
Translate the framework into controlled engineering work.
| Area | Question | Typical evidence |
|---|---|---|
| Agreement processes | How are acquisition, supply and acceptance governed? | Agreements, statements of work and acceptance criteria |
| Organisational enablement | Which infrastructure, competence, quality and knowledge are needed? | Organisational plans and resources |
| Technical management | How are planning, decisions, risk, configuration and information controlled? | Management records and baselines |
| Technical processes | How are needs transformed, realised, verified and validated? | Engineering artefacts and results |
| Tailoring | Which outcomes apply and how will they be achieved? | Tailoring record |
Apply the current controlled source
This module is an orientation. Confirm the applicable edition, amendments, adopted regional version, contractual commitments and sector-specific interpretations before defining compliance.
Use a risk-based application sequence.
- 1. Define the system of interest, lifecycle stages, stakeholders and enabling systems
- 2. Select and tailor applicable processes and expected outcomes
- 3. Plan decision, risk, configuration, information and measurement controls
- 4. Transform stakeholder needs into system requirements and architecture
- 5. Integrate, verify, transition and validate the system in its operational context
- 6. Operate, maintain and dispose while feeding experience into change
Worked application: industrial monitoring platform
The system includes sensors, gateways, cloud services, installer tools and support operations. Lifecycle planning exposes needs for device identity, calibration, fleet updates, spare parts and data migration. These become architecture and verification concerns rather than surprises after product launch.
Build evidence that explains the reasoning.
Stages, decision points, feedback and release concept.
Applicable processes, outcomes and rationale.
Users, operators, maintainers and acquirers.
Functions, interfaces, enabling systems and allocations.
Risk, decisions, configuration and information control.
Deployment, operation, maintenance and disposal readiness.
Common failure patterns
Processes are treated as a mandated one-pass sequence.
Titles are matched while outcomes remain unachieved.
Manufacturing, service and operational systems are omitted.
Activities disappear without risk-based rationale.
Further learning
- ISO / IEC / IEEE 15288:2023Official ISO entry for system lifecycle processes.
- TEA-101 · Embedded systems architectureSystem boundaries, allocations, interfaces and decisions.
Use the standard to strengthen decisions, not decorate them.
Make scope, tailoring, responsibilities, technical reasoning and objective evidence explicit—and always work from the current authorised text.