Software Engineering Process and Lifecycle Models
What the domain covers
This domain tests lifecycle models and process improvement. Expect waterfall, V-model, incremental, spiral, agile Scrum, Kanban, DevOps, and process maturity concepts. Questions often ask which model fits a project’s risk and regulatory context.
Core rules
- Waterfall suits stable, well-understood requirements with sequential gates.
- The V-model pairs each development level with a verification level, such as requirements with acceptance testing and design with integration testing.
- Incremental delivery ships usable increments; iterative delivery revisits and refines work.
- Spiral is risk-driven and combines iterative development with explicit risk analysis.
- Agile favors frequent feedback and working software, but does not forbid documentation or Architecture.
Worked example
A medical device with strict regulatory traceability needs predictable verification and documented evidence. A pure agile Scrum team with undocumented changes creates audit risk. A better fit is an incremental lifecycle with formal requirements traceability, stage gates, and disciplined verification, while allowing short internal iterations. Reasoning: the model must satisfy both feedback needs and regulatory evidence requirements.
Traps
- Claiming agile means no documentation or no planning.
- Confusing iteration with increment.
- Forgetting that the V-model’s right side mirrors the left side.
- Treating CMMI as a prescriptive process rather than a maturity framework.
Exam focus
Match lifecycle choice to requirement stability, risk, regulation, and delivery cadence.