System Life Cycle Processes Flashcards
6 cards from real ASEP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 System Life Cycle Processes flashcards as text
What is the relationship between the technical processes and technical management processes in ISO/IEC/IEEE 15288?
Answer: Technical management processes plan, assess, and control the execution of technical processes
Technical management processes (planning, risk management, configuration management, etc.) plan, monitor, and control the execution of the technical processes that perform the actual engineering work.
What distinguishes the Validation process from the Verification process in the system life cycle?
Answer: Verification confirms the system meets its specified requirements; validation confirms the system fulfills its intended use in the operational environment
Verification confirms conformance to specified requirements ('built right'); validation confirms the system satisfies its intended use and stakeholder needs ('built the right thing').
How does a spiral life cycle model manage risk compared to a waterfall model?
Answer: The spiral model explicitly incorporates risk analysis at each iteration, using risk assessment to drive planning for the next cycle
The spiral model uniquely incorporates explicit risk analysis at each iteration, using risk assessment results to guide the scope and focus of subsequent development cycles.
What is the purpose of the Business or Mission Analysis process in ISO/IEC/IEEE 15288?
Answer: To define the problem space, identify stakeholder needs at the business/mission level, and establish the justification for a new or modified system
Business/Mission Analysis defines the problem or opportunity, characterizes the solution space, and establishes the strategic justification for developing or modifying a system.
Why is it important to define life cycle concepts (operational concept, support concept, disposal concept) early in development?
Answer: Early concept definition shapes requirements, architecture, and design decisions that are costly to change later
Life cycle concepts defined early shape downstream requirements and design decisions; deferring them leads to systems that are difficult to operate, maintain, or dispose of.
What is concurrent engineering and how does it relate to the system life cycle?
Answer: It is the parallel execution of life cycle activities with cross-functional collaboration to reduce development time and improve design quality
Concurrent engineering overlaps life cycle activities and uses cross-functional teams to reduce development time, improve quality, and catch downstream issues early.