This document provides an overview of different software development life cycle (SDLC) models including Waterfall, Iterative, V-Model, Spiral, and Agile. It describes the key phases and characteristics of each model. For the Waterfall model, it outlines the sequential phases as well as advantages of being well documented and cost estimates being more accurate, and disadvantages of lack of feedback and inability to make changes late in the process. For the Agile model, it summarizes the Agile Manifesto values and principles of incremental, iterative development with a focus on customer collaboration and responding to change.

1. Quality Assurance /
Software Testing Training

2. Page 2Classification: Restricted
Agenda
• Software Development Life Cycle – SDLC –
• Waterfall Model,
• Iterative Model,
• V Model,
• Spiral Model,
• Agile Model

3. Page 3Classification: Restricted
SDLC Models
Waterfall Model
Waterfall approach was first SDLC Model to be used widely in Software
Engineering to ensure success of the project. In "The Waterfall" approach,
the whole process of software development is divided into separate
phases.
In Waterfall model, typically, the outcome of one phase acts as the input
for the next phase sequentially.

4. Page 4Classification: Restricted

5. Page 5Classification: Restricted
• System is well documented.
• Phases correspond with project management phases.
• Cost and schedule estimates may be lower and more
accurate.
• Details can be addressed with more engineering effort if
software is large or complex.
Waterfall Approach - Advantages

6. Page 6Classification: Restricted
• All risks must be dealt with in a single software development effort.
• Because the model is sequential, there is only local feedback at the
transition between phases.
• A working product is not available until late in the project.
• Progress and success are not observable until the later stages. If a mistake
or deficiency exists in the documentation of earlier phases, it may not be
discovered until the product is delivered.
• Corrections must often wait for the maintenance phase.
Application
The Waterfall model can be successfully used when requirements are well
understood in the beginning and are not expected to change or evolve over
the life of the project. Project risks should be relatively low.
Waterfall Approach - Disadvantages

7. Page 7Classification: Restricted
Iterative Model

8. Page 8Classification: Restricted
Spiral Model
The spiral model has four phases. A software project repeatedly passes through these
phases in iterations called Spirals.
• Identification: This phase starts with gathering the business requirements in the
baseline spiral. In the subsequent spirals as the product matures, identification of
system requirements, subsystem requirements and unit requirements are all done
in this phase.
• Design: Design phase starts with the conceptual design in the baseline spiral and
involves architectural design, logical design of modules, physical product design and
final design in the subsequent spirals.
• Construct or Build: Construct phase refers to production of the actual software
product at every spiral. In the baseline spiral when the product is just thought of
and the design is being developed a POC (Proof of Concept) is developed in this
phase to get customer feedback.
• Then in the subsequent spirals with higher clarity on requirements and design
details a working model of the software called build is produced with a version
number. These builds are sent to customer for feedback.
• Evaluation and Risk Analysis :Risk Analysis includes identifying, estimating, and
monitoring technical feasibility and management risks, such as schedule slippage
and cost overrun. After testing the build, at the end of first iteration, the customer
evaluates the software and provides feedback.

9. Page 9Classification: Restricted

10. Page 10Classification: Restricted
V-Model
Under V-Model, the corresponding testing phase of the development phase
is planned in parallel. So there are Verification phases on one side of the .V.
and Validation phases on the other side. Coding phase joins the two sides
of the V-Model.

11. Page 11Classification: Restricted
Agile Approach

12. Page 12Classification: Restricted
• Processes and techniques for incremental and iterative software
development
• Agile Manifesto
• – “We are uncovering better ways of developing software by doing it
and helping others do it. Through this work we have come to value”:
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
Valuable
More
Valuable
Agile Approach

13. Page 13Classification: Restricted
What does the Agile Manifesto Mean?

14. Page 14Classification: Restricted
12 Principles of Agile (1)

15. Page 15Classification: Restricted
12 Principles of Agile (2)

16. Page 16Classification: Restricted
Central: Incremental and Iterative Development

17. Page 17Classification: Restricted
Agile Methods

18. Page 18Classification: Restricted
• Planning
• –Vision, expectations, funding
• Staging
• – Identify requirements, prioritize iteration
• Development
• – Implement system ready for release in each sprint
• Release
• –Operational deployment
Scrum Lifecycle

19. Page 19Classification: Restricted
Agile Methods – Scrum (1)

20. Page 20Classification: Restricted
Agile Methods – Scrum (2)

21. Page 21Classification: Restricted

22. Page 22Classification: Restricted
Commitment
– Team takes responsibility to complete the Sprint. To avoid things that
will stand in its way
Focus
– Team’s focus is maintained. Distractions, interruptions are fielded
Openness
– Overall and individual status and commitments kept open.
Respect
– Team responsibility rather than scapegoat.
Courage
– Management and team have the courage to take responsibility to do
what is necessary
Scrum Values

23. Page 23Classification: Restricted
• What is the Agile manifesto?
• Compare Waterfall vs Agile
• How long were the iterations (or sprints) on the projects you worked on in
Agile?
• Did your iterations overlap? For instance, were the testers still testing
Iteration 6 while Iteration 5 was being designed/developed in Agile?
• What project management tools were used on your project in Agile ?
• What are the different Methodologies in Agile Development Model?
Assignments 2

24. Page 24Classification: Restricted
Question?

25. Page 25Classification: Restricted
Thank You