SDLC, STLC, and Development Models: Waterfall, V-Model, and Agile

Understanding SDLC and STLC alongside Waterfall, V-Model, and Agile: what QA needs to know and how the tester's role changes in each approach.

Updated:

Contents

SDLC, STLC, and Development Models: Waterfall, V-Model, and Agile

In almost any QA team, you will eventually hear SDLC, STLC, Waterfall, V-Model, and Agile. These terms matter because they explain the product's process and QA's place within it, beyond their popularity in interviews. Understanding the development lifecycle helps testers plan checks, join requirements discussions in time, and explain why quality begins long before clicking Run regression.

What is SDLC?

SDLC stands for Software Development Life Cycle. It describes a product's journey from an idea to production support, usually including analysis, design, development, testing, release, and maintenance. For QA, this is practical knowledge: SDLC reveals where risks arise, whether in requirements, architecture design, integration, or release.

  • →SDLC answers how a product is created from idea to delivery.
  • →QA matters at almost every SDLC stage, beyond the testing phase.

What is STLC?

STLC stands for Software Testing Life Cycle. It describes testing activities within development rather than the product's entire journey: requirements analysis, test planning, test data preparation, test design, execution, reporting, and closure. Essentially, STLC treats QA work as a distinct process within the overall SDLC.

  • →STLC helps structure QA work.
  • →Without understanding STLC, testing can quickly become a disorganized collection of checks.

Waterfall: sequential development

In Waterfall, stages proceed sequentially: requirements, design, development, testing, and release. Its strengths are predictability and clear structure; its weakness is late feedback. Poor requirements often become evident only when changes are already expensive. QA in Waterfall needs to scrutinize requirements and documentation because corrections cost more at later stages.

  • →Waterfall suits stable requirements.
  • →For QA, Waterfall's main risks are late error detection and limited flexibility.

V-Model: stronger connections between stages

The V-Model developed from Waterfall and emphasizes relationships between development and testing stages. Requirements connect to acceptance testing, system design to system testing, architecture to integration testing, and module design to unit tests. It is useful to QA because it demonstrates that testing should be planned early rather than starting only after coding ends.

  • →The V-Model makes quality more predictable.
  • →It helps QA explain why testing begins well before release.

Agile: iterative, adaptive development

Agile is a family of adaptive approaches rather than one specific process. Products develop through short iterations, work is delivered in small increments, feedback arrives sooner, and requirements evolve. QA needs communication skills, responsiveness, the ability to work with incomplete requirements, and continual participation in team activity. QA is integrated into everyday work rather than positioned at the end of a chain.

  • →In Agile, QA participates more often in requirements and acceptance criteria discussions.
  • →Better team communication leads to stronger quality outcomes.

How QA's role changes across models

In Waterfall, QA often joins later and works more with completed functionality. In the V-Model, testers plan checks for each stage in advance. In Agile, QA participates in daily product work: discussing requirements, assessing risks, testing increments, and helping decide readiness. In practice, a company calling itself Agile may combine several approaches. Testers therefore benefit from understanding these models' practical effects as well as their definitions.

  • →No single model is ideal for every product.
  • →Strong QA adapts to the process while protecting quality.

Conclusion

SDLC describes the product's full journey; STLC describes testing within it. Waterfall illustrates a sequential approach, the V-Model connects development and testing, and Agile emphasizes continual adaptation and short feedback loops. For beginners, understanding how process affects risks, schedules, and the tester's place in the team matters more than memorizing polished definitions.