Describe System Development Life Cycle (SDLC). Critically evaluate its applicability in large-scale Government IT Projects with suitable examples.
15 marks · directive: Critically evaluate
The core of a good answer
The SDLC is a phased, documented process for building information systems, from feasibility and requirements through design, construction, testing, deployment and maintenance; it gives large government projects control and accountability, but a rigid waterfall form struggles with changing requirements, so iterative and agile variants are increasingly used.
An outline written by upsc.help, not an official UPSC answer; every fact checked by a separate review. How we work
What the question asks
7 marks to describe the phases and models; 8 marks for a critical evaluation in the government context: strengths (procurement, audit, documentation), weaknesses (long cycles, scope change, user engagement) and named Indian and foreign examples of success and failure.
Answer outline
Introduction
The SDLC divides system development into sequential phases with defined deliverables and review points, giving managers a framework to plan, control and audit IT projects.
Phases of the SDLC
- Preliminary investigation and feasibility study (technical, economic, operational, schedule).
- Requirements analysis and specification with users.
- System design: logical and physical design of data, processes, interfaces and architecture.
- Development or construction: coding and integration.
- Testing: unit, integration, system and user acceptance testing.
- Implementation or deployment: delivery to users, training, data migration.
- Operation and maintenance; finally retirement or decommissioning.
Models
- Waterfall (sequential), prototyping, iterative and incremental, spiral (risk driven), agile (short iterations with working software).
Applicability: strengths for government projects
- Fits government procurement and tendering, which require fixed specifications, milestones and payments.
- Documentation and sign-offs support audit, accountability and continuity when officials transfer.
- Formal testing and security review suit mission-critical systems handling citizen data and money.
- Phased roll-out and pilots reduce risk for nationwide systems.
Applicability: limitations
- Very long cycles: requirements change with policy and law before delivery.
- Big-bang launches carry high risk when load and integration are not tested at scale.
- Weak user and field-level involvement leads to systems that do not match ground reality.
- Vendor lock-in, cost overruns and difficulty in changing scope after contracts are signed.
Way forward
- Iterative or agile delivery within a phased framework, minimum viable products and pilots.
- Strong programme management, independent quality assurance, open standards and API based platforms.
- Continuous user feedback and capacity building in departments.
Conclusion
The SDLC remains essential for discipline and accountability in public IT, but its value depends on adapting it: iterative delivery, early load testing and genuine user participation.
Examples and data to cite
- GST Network: the software developed by Infosys went live with GST on 1 July 2017; when the first returns were filed in August 2017 the system was reported to have crashed under heavy volume.
- HealthCare.gov (USA): launched on 1 October 2013 and failed under load; pre-launch tests had shown slowdowns with only 1,100 simultaneous users; total cost was later put at about $1.7 billion (HHS OIG, 2014).
- UK National Programme for IT in the NHS: established in October 2002, remaining parts cancelled in 2011 after delays, contractor exits (Accenture 2006, Fujitsu 2008) and weak clinical engagement; the original estimate of £2.3 billion over three years compares with an NAO estimate (June 2006) of £12.4 billion over ten years.
Facts to remember
- Winston Royce's 1970 article gave an early detailed diagram of the sequential (waterfall) process and called testing only at the end 'risky'.
- Barry Boehm described the spiral model, a risk-driven process model, in 1986.
- The Agile Manifesto was published in 2001.