Software Development Life Cycle Phases And Its Business Impact
by GainHQ Editorial Team | Jun 10, 2026 | Software Development Insights | Editorial policy
Table of Contents
- What is the software development life cycle?
- Why the SDLC matters to the business
- The 7 phases of the software development life cycle
- SDLC models compared
- How to choose an SDLC model
- SDLC environments: development, test, staging and production
- Secure SDLC: building security into every phase
- How to measure whether your SDLC is working
- AI in the software development life cycle
- A worked SDLC example (illustrative)
- Common SDLC mistakes
- How GainHQ can help
The software development life cycle (SDLC) is the structured sequence of phases a team follows to plan, build, test, release and maintain software. Most guides describe seven phases: planning, requirements analysis, design, development, testing, deployment and maintenance. A model such as waterfall, agile or DevOps decides how those phases are ordered, repeated and overlapped.
This guide explains each phase, compares the main SDLC models with a decision table, shows how to build security in, covers how to measure whether your life cycle is working, and finishes with a worked example.
What is the software development life cycle?
The software development life cycle is a framework that breaks software work into defined phases, each with its own inputs, outputs and checks. Its purpose is to make delivery predictable: everyone knows what has to be true before work moves on, and problems are caught in the phase where they are cheapest to fix.
The international reference for this is ISO/IEC/IEEE 12207:2026, which "establishes a common framework for software life cycle processes" covering acquisition, supply, development, operation, maintenance and disposal. The 2026 edition replaced the 2017 edition in April 2026, and it does not require any specific life cycle model or methodology. That is the key point most explanations miss: the SDLC is the set of activities, and the model is how you arrange them.
Three terms get mixed up, and Google tests this page for all of them:
| Term | What it covers | Ends when |
|---|---|---|
| Software development life cycle (SDLC) | The engineering work to define, build, release and maintain software | The software is retired |
| Software product life cycle | The market life of a product: introduction, growth, maturity, decline | The product is withdrawn from sale |
| Systems development life cycle | The wider system: hardware, software, people, processes and data | The system is decommissioned |
Why the SDLC matters to the business
A defined life cycle turns software spending into a series of decisions you can review. Each phase ends with something concrete (a scope, a design, a tested build), so leaders can stop, change direction or invest more before the expensive work starts. Without that, the first real evidence of a problem often arrives at testing or launch.
Winston Royce made this point in 1970. Describing a single pass from requirements to operations, he wrote that "the implementation described above is risky and invites failure", because testing at the end is the first time real behaviour is observed, and a failure there can force a redesign that sends the project "back to the origin" (Royce, 1970). Every modern model is, in part, an answer to that problem.
The 7 phases of the software development life cycle
The seven phases are planning, requirements analysis, design, development, testing, deployment and maintenance. Some teams merge planning with analysis and deployment with maintenance, which gives the five-phase version you also see. The count matters less than making sure every activity is covered and has a clear exit check.
| # | Phase | Key question | Main outputs | Typical tools |
|---|---|---|---|---|
| 1 | Planning | Should we build this, and within what limits? | Goals, scope boundary, budget range, timeline, risks | Roadmaps, spreadsheets |
| 2 | Requirements analysis | What exactly must it do? | Requirements, user stories, acceptance criteria | Issue trackers, PRD templates |
| 3 | Design | How will it work? | Architecture, data model, UX flows, threat model | Diagramming, design tools |
| 4 | Development | Is it built to the design? | Source code, unit tests, code reviews | Git, IDEs, CI |
| 5 | Testing | Does it work, and is it safe? | Test results, defect log, sign-off | Test frameworks, scanners |
| 6 | Deployment | Can users get it safely? | Release, rollback plan, release notes | CD pipelines, feature flags |
| 7 | Maintenance | Is it still doing its job? | Fixes, updates, monitoring, retirement plan | Monitoring, incident tools |
1. Planning
Planning decides whether the project should go ahead and sets its limits: the business goal, the scope boundary, the budget range and the target timeline. A realistic schedule depends on scope and team size, so tie the plan to a software development timeline rather than a date picked first. If you are hiring a partner, this is where a software development RFP is written.
2. Requirements analysis
Requirements analysis turns goals into specific, testable statements of what the software must do. A product requirements document holds the big picture, and each user story needs acceptance criteria so "done" can be checked rather than argued about.
3. Design
Design decides how the software will meet the requirements: architecture, data model, integrations, user flows and security controls. It is also where you confirm what type of software you are building, because a web app, mobile app and embedded system carry very different design constraints. Threat modelling belongs here, not after launch.
4. Development
Development is where code is written, reviewed and merged against the design. Small changes, peer review and automated builds on every commit keep problems small. In agile teams this phase runs in short cycles; see our guide to sprint planning.
5. Testing
Testing checks that the software meets its acceptance criteria and does not break what already works. It covers unit, integration, end-to-end, security and performance testing. Royce's 1970 advice still holds: plan, control and monitor testing from the start rather than leaving it to the end.
6. Deployment
Deployment releases the tested build to users. Low-risk deployment means automated pipelines, a rollback plan and, where useful, gradual rollouts or feature flags so a bad change reaches as few users as possible.
7. Maintenance
Maintenance keeps the software useful and safe after release: bug fixes, security patches, dependency updates, performance work and new features. It runs for the whole life of the product, and it ends with a deliberate retirement or replacement decision.
SDLC models compared
An SDLC model is the pattern that decides how the phases run: once in sequence, in repeated loops, or continuously. The main models are waterfall, V-model, iterative/incremental, spiral, agile and DevOps. None is best in general; each fits a different level of requirement certainty and risk.
| Model | How phases run | Best fit | Main risk |
|---|---|---|---|
| Waterfall | Once, in sequence, with sign-off between phases | Stable, well-understood requirements; fixed contracts | Late discovery of problems at testing |
| V-model | Sequence, with a test level planned for each design level | Regulated or safety-critical work needing traceability | Expensive to change once underway |
| Iterative / incremental | Repeated cycles, each adding working functionality | Large products that can ship in parts | Architecture drift without a clear target |
| Spiral | Repeated cycles driven by the biggest open risk | High technical or business risk, novel systems | Needs real risk-assessment skill; overhead |
| Agile (e.g. Scrum) | Short fixed cycles, all phases in each one | Changing requirements, frequent user feedback | Scope creep without a strong product owner |
| DevOps / continuous delivery | Small changes flow continuously to production | Products released often, with automation in place | Needs mature testing and monitoring first |
What Royce actually said about waterfall
Royce's 1970 paper is usually cited as the origin of waterfall, but he did not recommend the single-pass version. He called it "risky" and proposed five fixes: do program design first, document the design, "do it twice" (build an early pilot), plan, control and monitor testing, and involve the customer (Royce, 1970). The word "waterfall" does not appear in the paper.
Spiral: risk decides the next step
Barry Boehm's spiral model was designed as "a risk-driven approach to the software process rather than a primarily document-driven or code-driven process" (Boehm, IEEE Computer, May 1988). Each cycle identifies objectives, alternatives and constraints, resolves the biggest risk (often with a prototype), and ends with a review where stakeholders commit to the next cycle.
Agile and Scrum
Agile is a set of values rather than one model. The Agile Manifesto (2001) values "working software over comprehensive documentation" and "responding to change over following a plan". Scrum, a widely used agile framework, runs work in Sprints that are "fixed length events of one month or less", with three accountabilities: Developers, Product Owner and Scrum Master (Scrum Guide 2020). Every SDLC phase still happens, just inside each Sprint.
DevOps and continuous delivery
DevOps extends the life cycle past release by joining development and operations, so deployment and maintenance happen continuously in small, automated steps. It works well only when testing, monitoring and rollback are already reliable.
How to choose an SDLC model
Choose the model by how certain your requirements are and where your biggest risk sits. Fixed, well-understood requirements suit sequential models; uncertain requirements suit iterative or agile models; high technical risk suits spiral-style prototyping. Many teams combine them, for example stage-gated planning with agile delivery.
| If this is true | Lean towards | Why |
|---|---|---|
| Requirements are fixed and signed off in a contract | Waterfall or stage-gated | Change is costly anyway; clear sign-offs help |
| You need audit trails or safety certification | V-model | Every requirement maps to a test |
| Users will only know what they want once they see it | Agile (Scrum or Kanban) | Short feedback loops |
| The core technology is unproven | Spiral or prototype-first | Retire the biggest risk before scaling up |
| You release several times a week | DevOps / continuous delivery | Automation keeps each change small |
| You are building a first version to test demand | Agile with a narrow MVP scope | Learn before committing budget |
SDLC environments: development, test, staging and production
Most teams run separate environments so unfinished work never touches real users. A change moves from development to test to staging to production, and each step adds a check.
| Environment | Purpose | Who uses it | Data |
|---|---|---|---|
| Development | Write and run code locally or in a shared dev space | Developers | Fake or seeded |
| Test / QA | Run automated and manual tests | QA, developers | Test data |
| Staging | Final check in a production-like setup | QA, product, stakeholders | Production-like, anonymised |
| Production | Live software | End users | Real |
Secure SDLC: building security into every phase
A secure SDLC adds security activities to every phase instead of testing for them at the end. NIST notes that "few software development life cycle (SDLC) models explicitly address software security in detail", which is why it published the Secure Software Development Framework (SSDF), SP 800-218, as practices you add to whichever model you use.
The SSDF groups its practices into four groups. Here is how they map to the phases:
| SSDF practice group | What it means | Where it lands in the SDLC |
|---|---|---|
| Prepare the Organization (PO) | People, processes and tools ready for secure development | Planning; ongoing |
| Protect the Software (PS) | Protect code and components from tampering and unauthorised access | Development, deployment |
| Produce Well-Secured Software (PW) | Releases with minimal vulnerabilities | Requirements, design, development, testing |
| Respond to Vulnerabilities (RV) | Find residual vulnerabilities, fix them, prevent repeats | Maintenance |
To assess how mature your secure SDLC is, OWASP SAMM 2.0 scores five business functions: Governance, Design, Implementation, Verification and Operations. CISA's Secure by Design initiative adds the expectation that security is decided at the design phase and shipped on by default. For SaaS-specific controls, see our SaaS security best practices.
How to measure whether your SDLC is working
The most widely used measures of software delivery are the five DORA metrics. They split into throughput (how fast changes move) and instability (how well deployments go), so you can see whether speed is coming at the cost of quality (DORA).
| DORA metric | Type | Definition (DORA) |
|---|---|---|
| Change lead time | Throughput | Time for a change to go from committed to version control to deployed in production |
| Deployment frequency | Throughput | Number of deployments over a period, or time between deployments |
| Failed deployment recovery time | Throughput | Time to recover from a deployment that fails and needs immediate intervention |
| Change fail rate | Instability | Ratio of deployments that need immediate intervention after deployment |
| Deployment rework rate | Instability | Ratio of unplanned deployments made because of a production incident |
Illustrative example (not GainHQ data): a team makes 40 deployments in 20 working days, an average of 2 per day. Three needed immediate intervention, so the change fail rate is 3 ÷ 40 = 7.5%. Two were unplanned fixes for production incidents, so the deployment rework rate is 2 ÷ 40 = 5%. Track the trend over time rather than the single number. Our guide to engineering KPIs covers how to report these alongside business measures.
AI in the software development life cycle
AI tools now assist in most phases: drafting requirements and test cases, suggesting code, reviewing pull requests and summarising incidents. They change how fast each phase runs, but not the need for each phase's checks. AI-generated code still needs review, testing and security scanning before it ships.
If you build AI features into your product, the life cycle gains extra work: data sourcing, model evaluation and monitoring for drift. NIST's SP 800-218A (July 2024) extends the SSDF with secure development practices for generative AI and foundation models.
A worked SDLC example (illustrative)
This example is illustrative, not a GainHQ project. A regional distributor wants a customer portal where clients can track orders and download invoices, replacing phone and email requests.
| Phase | What happens | Exit check |
|---|---|---|
| Planning | Goal: cut order-status calls. Scope: order tracking and invoices only; payments later. Team and timeline agreed | Sponsor approves scope and budget range |
| Requirements | User stories, e.g. "As a client, I can see the status of each open order". Acceptance criteria written per story | Every story has testable criteria |
| Design | Web app reading from the existing ERP via an API; login with multi-factor authentication; threat model for invoice access | Architecture and threat model reviewed |
| Development | Two-week Sprints; code review and automated builds on every merge | Each story meets its acceptance criteria |
| Testing | Integration tests against an ERP test copy; access-control tests so one client cannot see another's invoices; load test | No open critical defects |
| Deployment | Release to a pilot group of clients first, with a rollback plan | Pilot runs without critical incidents |
| Maintenance | Monitor errors and usage; patch dependencies; plan the payments feature as the next cycle | DORA metrics and support-call trend reviewed |
Common SDLC mistakes
- Treating phases as paperwork. Documents that nobody reads do not reduce risk. Each phase needs an exit check that someone owns.
- Vague requirements. Without acceptance criteria, testing cannot prove anything.
- Testing and security at the end. This is the exact failure Royce described in 1970.
- Picking a model by fashion. Choose by requirement certainty and risk, using the table above.
- No measurement. Without the DORA metrics or similar, you cannot tell whether changes to the process help.
- Forgetting maintenance. Budget and staff for the years after launch, not just the build.
How GainHQ can help
GainHQ is a custom software development agency with more than 15 years of building software, more than 13 products delivered and a team of over 30 people. We run the full life cycle for our own products, Payrun (HR and payroll) and Gain.io (CRM and helpdesk), as well as for client work. If you want help planning, designing, building or maintaining software, see our services.
Frequently asked questions
What are the 7 phases of the SDLC?
The seven phases are planning, requirements analysis, design, development, testing, deployment and maintenance. Each phase has its own outputs and an exit check, such as signed-off requirements or a passed test run, before work moves on. Agile teams run all seven inside each short cycle.
What are the 5 phases of the software development life cycle?
The five-phase version merges some of the seven: typically planning and requirements, design, development, testing, and deployment and maintenance. Nothing is removed, only grouped. The phase count is a naming choice; what matters is that every activity is covered.
Is the SDLC outdated?
No. The rigid single-pass version is outdated, and Royce warned against it in 1970. The phases themselves still happen in agile and DevOps teams, just in shorter, repeated cycles. ISO/IEC/IEEE 12207 was revised in 2026 and does not require any particular model.
What is the difference between the SDLC and agile?
The SDLC is the set of phases every software project goes through. Agile is one way of running those phases: in short, repeated cycles with frequent feedback, guided by the Agile Manifesto's values. Agile is a model or approach within the SDLC, not a replacement for it.
Which SDLC model is best?
None is best in general. Waterfall or V-model suits fixed, regulated requirements; agile suits changing requirements; spiral suits high technical risk; DevOps suits frequent releases with strong automation. Many teams combine stage-gated planning with agile delivery.
What is a secure SDLC?
A secure SDLC adds security activities to every phase, such as security requirements, threat modelling, secure coding, security testing and vulnerability response, instead of testing at the end. NIST's SSDF (SP 800-218) defines four practice groups you can add to any model.
What is the difference between the SDLC and the software product life cycle?
The SDLC covers the engineering work to build, release and maintain software. The product life cycle covers the product's market life: introduction, growth, maturity and decline. One product can go through many SDLC cycles during its market life.
How do you explain the SDLC in an interview?
Define it in one sentence, name the seven phases in order, then name two or three models and when each fits. Close with how you measured delivery, for example DORA's change lead time and change fail rate, and how security was built into each phase.