ASEP System Life Cycle Processes 2 — Questions and Answers
Question 1: According to ISO/IEC/IEEE 15288, what are the four process groups that organize system life cycle processes?
- Design, Build, Test, Deploy
- Agreement, Organizational Project-Enabling, Technical Management, Technical (Correct answer)
- Planning, Execution, Monitoring, Closing
- Requirements, Architecture, Implementation, Maintenance
Correct answer: Agreement, Organizational Project-Enabling, Technical Management, Technical
ISO/IEC/IEEE 15288 organizes system life cycle processes into four groups: Agreement, Organizational Project-Enabling, Technical Management, and Technical processes.
ISO/IEC/IEEE 15288 defines 30 processes organized into four groups. Agreement processes handle acquisition and supply relationships. Organizational Project-Enabling processes provide resources and infrastructure (life cycle model management, infrastructure management, portfolio management, human resource management, quality management, knowledge management). Technical Management processes manage the technical effort (project planning, project assessment and control, decision management, risk management, configuration management, information management, measurement, quality assurance). Technical processes perform the engineering work (business/mission analysis, stakeholder needs definition, requirements analysis, architecture definition, design definition, system analysis, implementation, integration, verification, validation, operation, maintenance, disposal).
Question 2: What is the primary difference between a sequential (waterfall) life cycle model and an iterative life cycle model?
- Sequential models are always faster
- Sequential models complete each phase once before moving to the next; iterative models revisit phases in repeated cycles to refine the system progressively (Correct answer)
- Iterative models skip the requirements phase
- There is no meaningful difference
Correct answer: Sequential models complete each phase once before moving to the next; iterative models revisit phases in repeated cycles to refine the system progressively
Sequential models progress through phases linearly, while iterative models revisit phases in repeated cycles, each cycle producing a more refined version of the system.
In a sequential (waterfall) life cycle model, each phase (requirements, design, implementation, test) is completed before the next begins, with minimal backtracking. This works well for well-understood systems with stable requirements. In an iterative model, the system is developed through repeated cycles, each passing through requirements, design, implementation, and evaluation to produce progressively refined versions. Iteration allows early feedback, accommodates evolving requirements, and reduces risk by validating design decisions early. The choice between models depends on requirements stability, technical risk, stakeholder availability for feedback, and system complexity.
Question 3: What is the purpose of the Disposal process in the system life cycle?
- To archive project documents
- To systematically deactivate, disassemble, and remove a system from operation while managing environmental, safety, and data concerns (Correct answer)
- To transfer the system to a new owner
- To conduct final acceptance testing
Correct answer: To systematically deactivate, disassemble, and remove a system from operation while managing environmental, safety, and data concerns
The Disposal process systematically deactivates and removes a system from operation, addressing environmental, safety, security, and data sanitization concerns.
The Disposal process addresses the end of a system's operational life, encompassing deactivation, disassembly, removal, and disposition of system elements. It must address environmental concerns (hazardous materials, recycling requirements), safety (de-energizing, removing hazardous components), security (data sanitization, classified material destruction), regulatory compliance (environmental regulations, export controls), and resource recovery (reuse of components, recycling of materials). Disposal planning should begin during system design to ensure the system can be safely and economically disposed of. Neglecting disposal considerations during design can result in extremely costly end-of-life activities.
Question 4: In the context of life cycle processes, what does 'tailoring' refer to?
- Customizing user interfaces
- Adapting standard life cycle processes to fit the specific needs, constraints, and context of a particular project (Correct answer)
- Reducing the project team size
- Eliminating quality assurance activities
Correct answer: Adapting standard life cycle processes to fit the specific needs, constraints, and context of a particular project
Tailoring adapts standard life cycle processes to the specific context of a project based on its size, complexity, risk, and domain requirements.
Tailoring is the systematic adaptation of standard life cycle processes to suit the specific characteristics of a project. Factors driving tailoring include system complexity, project size, technical risk level, domain regulatory requirements, organizational maturity, stakeholder expectations, and available resources. Tailoring may add activities (for safety-critical systems), remove activities (for low-risk commercial products), modify artifacts, or adjust the sequence of activities. ISO/IEC/IEEE 15288 explicitly supports tailoring but requires that tailoring decisions be documented and justified. The key principle is that tailoring should be deliberate and risk-informed, not arbitrary—removing a process step without understanding its purpose can introduce unmanaged risk.
Question 5: What role does the Maintenance process play after a system enters operational service?
- It only addresses hardware repairs
- It sustains system capability through corrective, adaptive, perfective, and preventive actions throughout the operational phase (Correct answer)
- It replaces the need for configuration management
- It is only required for military systems
Correct answer: It sustains system capability through corrective, adaptive, perfective, and preventive actions throughout the operational phase
The Maintenance process sustains system capability through corrective (fixing defects), adaptive (responding to environment changes), perfective (enhancing performance), and preventive (avoiding future problems) actions.
The Maintenance process sustains system capability throughout the operational phase through four categories of action. Corrective maintenance fixes discovered defects. Adaptive maintenance modifies the system to accommodate changes in its operating environment (new regulations, updated interfaces, technology refresh). Perfective maintenance enhances performance or adds capabilities requested by users. Preventive maintenance proactively addresses potential future problems (replacing aging components before failure, updating security patches). Effective maintenance requires configuration management, impact analysis, regression testing, and documentation updates—essentially applying the full systems engineering discipline to modifications of an operational system.
Question 6: Why is stakeholder involvement throughout the life cycle considered critical rather than optional?
- It is only important during requirements definition
- Continuous stakeholder involvement ensures the evolving system remains aligned with actual needs and enables early detection of misalignment (Correct answer)
- It slows down the development process and is discouraged
- It is only required for government contracts
Correct answer: Continuous stakeholder involvement ensures the evolving system remains aligned with actual needs and enables early detection of misalignment
Continuous stakeholder involvement throughout all life cycle phases ensures the system remains aligned with evolving needs and catches misalignment before it becomes costly to correct.
Stakeholder involvement throughout the life cycle is critical because needs evolve, understanding deepens, and early misalignment detection saves orders of magnitude in correction cost. During concept development, stakeholders clarify needs. During design reviews, they validate that the design addresses their concerns. During integration and testing, they confirm that the emerging system matches their expectations. During operations, they provide feedback for maintenance and future upgrades. Programs that limit stakeholder involvement to early requirements gathering frequently deliver systems that technically meet documented requirements but fail to satisfy actual user needs—a costly form of project failure that continuous engagement prevents.
ASEP System Life Cycle Processes 2
According to ISO/IEC/IEEE 15288, what are the four process groups that organize system life cycle processes?