Software Development Life Cycle (SDLC): Phases, Models and Examples
The software development life cycle (SDLC) explained: the 7 SDLC phases, the main SDLC models from waterfall to agile, and how to pick one for your project.
The software development life cycle (SDLC) is the process teams use to take software from idea to retirement: planning, requirements, design, development, testing, deployment and maintenance. Every project goes through these seven phases. What differs between SDLC models, such as waterfall, agile, spiral or V-model, is the order, how often the phases repeat, and how much is decided up front. Picking the right model for your project matters more than following any one model perfectly.
Why the SDLC matters
Without a shared process, projects drift: requirements live in someone’s head, testing happens if there is time, and nobody owns the system after launch. The SDLC gives everyone, from founders to engineers, the same map of where the project is, what comes next and what “done” means.
It also makes cost visible. Mistakes are cheap in planning and expensive in production, so a good process catches them as early as possible.
The 7 phases of the software development life cycle
1. Planning
Define the goal, the budget, the timeline and the main risks. Decide whether to build, buy or combine both. Our build vs buy guide covers that decision. The output is a short plan everyone agrees on.
2. Requirements analysis
Turn the goal into specific requirements: who the users are, what they need to do, and which rules, integrations and constraints apply. This is the phase with the largest effect on cost, because a wrong requirement is cheap to fix on paper and expensive to fix in code. See how to write a software requirements document.
3. Design
Decide how the system will work: architecture, data model, integrations, security and the user interface. Big early choices, such as a monolith or microservices, are made here.
4. Development
Engineers write the code, review each other’s changes and integrate them continuously. Good teams keep the main branch deployable at all times and automate builds from the start.
5. Testing
Verify the software does what the requirements say: automated unit and integration tests, manual exploratory testing, performance and security checks, and user acceptance testing. In modern teams testing runs alongside development rather than as a separate phase at the end.
6. Deployment
Release the software to users, ideally through an automated pipeline with the ability to roll back. Staged rollouts and feature flags reduce the risk of each release.
7. Maintenance
Fix bugs, update dependencies, patch security issues, monitor performance and add features. Maintenance usually makes up the largest share of a system’s total cost over its life. Our guide to software maintenance cost has typical numbers.
SDLC models compared
| Model | How it works | Best for | Main risk |
|---|---|---|---|
| Waterfall | Phases run once, in order, with sign-offs | Fixed requirements, compliance, hardware | Problems found late |
| V-model | Waterfall with a test phase planned for each design phase | Safety-critical and regulated systems | Rigid when requirements change |
| Iterative | Build a basic version, then improve it in cycles | Large systems with clear core needs | Scope can grow each cycle |
| Spiral | Cycles driven by risk analysis | Large, high-risk projects | Costly and complex to manage |
| Agile (Scrum, Kanban) | Short cycles with working software each time | New products, changing requirements | Needs active customer involvement |
| DevOps | Agile plus automated deployment and operations | Products released many times a week | Needs strong automation and monitoring |
The two you will meet most often are waterfall and agile. Their trade-offs are covered in detail in agile vs waterfall.
How to choose an SDLC model
Ask three questions:
- How stable are the requirements? Fixed by law or contract points to waterfall or V-model. Likely to change points to agile.
- How costly is a mistake in production? Safety-critical systems need more up-front verification.
- How involved will the customer be? Agile only works if someone with authority reviews progress every week or two.
For most business software we recommend a hybrid: plan and price the scope of version one like waterfall, then deliver it in one-week agile sprints with a demo every week. You get a fixed budget and early, visible progress. More on contracts in fixed price vs time and materials.
SDLC with an outsourced team
When you work with an external team, the life cycle is the same, but ownership needs to be explicit:
- Requirements: you own the “what”; the team helps turn it into acceptance criteria.
- Design and development: the team owns the “how”, in a repository you control.
- Testing: both sides. The team automates; you accept.
- Deployment and maintenance: agree in writing who is on call and how updates are handled after launch.
Our guide to managing an outsourced development team covers the day-to-day routines, and if a project has already gone off track, see how to take over a software project.
The SDLC is not paperwork. It is the shortest reliable path from an idea to software that keeps working, and the earlier each phase catches a mistake, the cheaper that path becomes.
FAQ
What is the software development life cycle?
The software development life cycle, or SDLC, is the structured process teams use to plan, design, build, test, deploy and maintain software, so that it meets requirements, stays on budget and keeps working after release.
What are the 7 phases of the SDLC?
Planning, requirements analysis, design, development, testing, deployment, and maintenance. Some models merge or repeat phases, but every software project goes through each of them in some form.
Which SDLC model is best?
There is no single best model. Waterfall suits fixed, well-understood requirements; agile models such as Scrum suit products whose requirements will change. Many teams use a hybrid with a fixed scope delivered in short iterations.
Is agile an SDLC model?
Yes. Agile is an iterative SDLC approach where planning, design, development and testing repeat in short cycles, usually one to two weeks, with working software delivered at the end of each cycle.
What is the most important phase of the SDLC?
Requirements analysis has the biggest effect on cost, because mistakes made there are the most expensive to fix later. Maintenance usually accounts for the largest share of total cost over a system's life.