Software Lifecycle Models

Lecture 3 of CS605 Software Engineering - II presents a systematic comparative evaluation of prescriptive software lifecycle models. The lecture begins with the classic Linear Sequential Model, commonly designated the Waterfall Model, examining its sequential progression through requirements analysis, system design, implementation, testing, and post-deployment maintenance. Students analyze the advantages and severe real-world limitations of the waterfall approach, particularly its assumption of stable, upfront requirements, rigid milestone gating, and the late emergence of a working program that creates a catastrophic blocking state when fundamental design flaws surface late. The V-Model is explored as a direct extension that explicitly pairs each upstream development phase with an associated verification and validation testing activity, such as unit testing against detailed design and acceptance testing against system requirements. Prototyping lifecycle models are examined as powerful communication tools when customers have fuzzy or evolving expectations, demonstrating how rapid mockups clarify user interfaces and operational workflows. Software quality assurance audits and formal technical reviews are presented as indispensable instruments for defect detection and process compliance. Organizational structures, including democratic decentralized, controlled decentralized, and controlled centralized teams, are contrasted regarding productivity. Team dynamics and collaborative leadership styles are analyzed to overcome communication bottlenecks and foster high-performing development cultures. The curriculum traces the evolutionary transition from traditional waterfall lifecycles to iterative and risk-driven development paradigms. Practical considerations for statistical software quality assurance, error tracking, and Pareto analysis provide rigorous quantitative decision support. Scholars examine how mistake-proofing mechanisms such as Poka-Yoke can be adapted to software design to eliminate defect injection at the source. System maintenance challenges in legacy enterprise environments are evaluated alongside forward engineering and reverse engineering workflows. The lesson explores Martin Fowler refactoring patterns, demonstrating how code smells are methodically removed while preserving observable behavior. Extract method, move method, and replace temp with query are examined through concrete code refactoring demonstrations. Students study process maturity assessment frameworks, distinguishing between staged and continuous CMMI representations. Key process areas spanning requirements management, project planning, and quantitative process management are systematically demystified.