Traditional Waterfall

FELEC3 – Group 1
first question:
What is the Traditional
Waterfall Method?
It is alinear approach to
software development. Each
phase of a product’s life cycle
takes place in sequence. Progress
flows steadily downwards
through these phases like a
waterfall.
first question:
What is the Traditional
Waterfall Method?
 first question:
What is the Traditional
Waterfall Method?
 second question:
What are these sequence
of events (phases)?
These phases are:
Requirement gathering
System design
Implementation
Integration and Testing
Deployment
Maintenance
second question:
What are these sequence
of events (phases)?
Requirement gathering

All possible
requirements are
captured in product
requirement documents.

second question:
What are these sequence
of events (phases)?
System design
Based on analysis
design the software
architecture.

second question:
What are these sequence
of events (phases)?
Implementation
The system is first
developed in small
programs called units.
Each unit is developed and
tested for its functionality,
which is referred to as Unit
Testing.
second question:
What are these sequence
of events (phases)?
Integration and Testing

Integrating of each unit

developed in previous
phase and post
integration test the
entire system for any
faults.
second question:
What are these sequence
of events (phases)?
Deployment

product live on
Make the
production
environment after all
functional and
nonfunctional testing
completed.
second question:
What are these sequence
of events (phases)?
Maintenance

Issues and release new

version with the issue
patches as required.

second question:
What are these sequence
of events (phases)?
third question:
What are the pros?
 Developers and customers
agree on what will be delivered
early in the development
lifecycle.

third question:
What are the pros?
Progress is more easily
measured as the full scope of the
work is known in advance.

third question:
What are the pros?
 Customer presence is not
strictly required after the
requirements phase.

third question:
What are the pros?
 Software can be designed
completely and more
carefully based upon a more
complete understanding of all
software deliverables.

third question:
What are the pros?
 fourth question:
What are the issues?
 One area which almost falls
short is the effectiveness of
requirements and often the
most difficult part of software
development.

fourth question:
What are the issues?
 Wireframes and mockups
can help, but there’s no question
that most end users have some
difficulty putting these
elements together.

fourth question:
What are the issues?
 Another potential drawback is
the possibility that the
customer will be dissatisfied
with their delivered software
product.

fourth question:
What are the issues?
So, do we need to
use this model?
It may be traditional but it is the
first method used in SDLCs
The success of the project
does not rely only on the
model used, but depends on
how the project team works
together to finish the project
with satisfaction and quality.
Questions?
Thank you!
SOURCES
https://manifesto.co.uk/agile-vs-waterfall-comparing-project-management-methodologies/
https://www.seguetech.com/waterfall-vs-agile-methodology/
https://cheezburger.com/2082309/19-star-wars-reaction-gifs
https://gfycat.com/gifs/detail/IdioticRectangularCockerspaniel
https://economictimes.indiatimes.com/definition/waterfall-model
https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm
https://giphy.com/gifs/darth-vader-star-wars-force-TSmahCISxIiZ2
https://www.romper.com/p/9-ways-to-get-your-kids-excited-for-star-wars-the-force-awakens-in-case-they-arent-
already-1938