Life Cycle Characteristics
Describes the main characteristics of system life cycles, including stages, decision gates, iteration, recursion, tailoring, and technical baselines.
Life Cycle Characteristics
A system life cycle has several important characteristics. These characteristics help teams understand how systems mature, how decisions are made, and how Systems Engineering activities are applied across time.
Life Cycles Are Stage-Based
A life cycle is usually described as a sequence of stages.
A generic sequence is:
- Concept
- Development
- Production
- Utilization
- Support
- Retirement
These stages help structure work, but they should not be interpreted as perfectly isolated blocks. Activities often overlap, repeat, or continue across several stages.
Life Cycles Are Decision-Oriented
Life cycles usually include decision points, gates, or reviews.
These decision points help determine whether the system is ready to proceed.
Typical questions include:
- Is the need understood?
- Are stakeholder requirements mature enough?
- Is the architecture feasible?
- Are risks acceptable?
- Is the design ready for implementation?
- Is the system ready for integration?
- Is the system ready for verification?
- Is the system ready for operational use?
- Is the system ready for retirement?
Decision points provide control without eliminating the need for technical judgment.
Life Cycles Are Iterative
Although life-cycle stages are often shown in sequence, real systems usually require iteration.
Iteration occurs when teams revisit earlier decisions based on new information.
Examples include:
- Requirements are updated after stakeholder feedback.
- Architecture changes after analysis reveals a risk.
- Design changes after integration testing.
- Support concepts change after operational experience.
- Retirement plans change because of regulatory or environmental constraints.
Iteration is not automatically a failure. It is often necessary for learning and risk reduction.
Life Cycles Are Recursive
Systems Engineering is recursive across system hierarchy.
The same life-cycle thinking can be applied to:
- The system of interest
- Subsystems
- Components
- Software elements
- Services
- Enabling systems
For example, a subsystem may have its own concept, development, production, utilization, support, and retirement considerations within the broader system life cycle.
For more detail, see:
Hierarchy within a System
Life Cycles Are Tailored
No single life-cycle model fits every system.
Life cycles should be tailored based on:
- System complexity
- Degree of innovation
- Safety criticality
- Security criticality
- Regulatory environment
- Stakeholder uncertainty
- Technology maturity
- Supplier structure
- Contracting approach
- Operational urgency
- Organizational capability
- Risk tolerance
A simple internal tool may not need the same life-cycle rigor as a safety-critical aerospace, medical, transportation, nuclear, or defense system.
Life Cycles Include Technical Baselines
A technical baseline is an agreed description of the system at a point in time.
Baselines may include:
- Stakeholder needs
- System requirements
- Architecture
- Interface definitions
- Design descriptions
- Verification plans
- Validation plans
- Configuration items
- Operational concepts
- Support concepts
Baselines support communication, control, traceability, and change management.
Life Cycles Involve Maturity Growth
As the system progresses through the life cycle, information should mature.
Examples of maturity growth include:
| Area | Early Life Cycle | Later Life Cycle |
|---|---|---|
| Need | Problem or opportunity | Validated stakeholder need |
| Requirements | Draft expectations | Approved and verified requirements |
| Architecture | Candidate concepts | Defined and controlled architecture |
| Design | Alternative solutions | Implemented design |
| Interfaces | Assumptions | Controlled interface definitions |
| Risk | Uncertainty | Retired, accepted, or managed risks |
| Verification | Strategy | Evidence of requirement satisfaction |
| Validation | Planned scenarios | Evidence of stakeholder need satisfaction |
Maturity does not mean all uncertainty disappears. It means the team has sufficient evidence to make responsible decisions.
Life Cycles Manage Risk
Risk management is active across all life-cycle stages.
Examples include:
- Concept risks related to unclear needs
- Development risks related to immature technology
- Production risks related to manufacturability
- Utilization risks related to operational performance
- Support risks related to reliability and maintainability
- Retirement risks related to safety, data, disposal, and environmental compliance
The goal is not to eliminate all risk, but to understand, reduce, transfer, accept, or control risk appropriately.
Life Cycles Include Verification and Validation
Verification and validation are not limited to the end of development.
They should be planned early and performed throughout the life cycle.
Verification asks:
Did we build the system correctly?
Validation asks:
Did we build the right system?
Both questions matter.
A system can pass verification and still fail validation if it satisfies written requirements but does not meet real stakeholder needs.
Life Cycles Include Feedback
Operational and support experience should feed back into the system life cycle.
Feedback may lead to:
- Corrective maintenance
- Product improvements
- Software updates
- New requirements
- Architecture changes
- Training improvements
- Safety mitigations
- Next-generation system concepts
This is especially important for long-lived systems, software-intensive systems, and systems of systems.
Life Cycles Are Connected to Value
The life cycle is ultimately about value.
A system should deliver value not only when it is first deployed, but throughout its operational life.
Life-cycle value depends on:
- Fitness for purpose
- Affordability
- Availability
- Reliability
- Safety
- Security
- Maintainability
- Usability
- Adaptability
- Supportability
- Sustainability
- Retirement responsibility
Key Takeaway
A life cycle is not just a schedule. It is a structured way to manage system maturity, decisions, risks, evidence, stakeholders, and value over time.
Introduction
Introduces the system life cycle and explains why life cycle thinking is central to Systems Engineering.
Generic Life Cycle Stages
Describes the generic system life cycle stages: Concept, Development, Production, Utilization, Support, and Retirement, with mention of domain-specific variants such as NASA life-cycle phases.