SlideShare a Scribd company logo
2
Most read
3
Most read
4
Most read
Waterfall Model
Agenda
• Waterfall Model overview
• Waterfall Model History (it was not waterfall)
• How does it work(which most Activity involved)
• Model derivable
• When to use
• Advantages
• Disadvantage
Waterfall Model overview
• Waterfall approach was first Process Model to be introduced and
followed widely in Software Engineering to ensure success of the
project.
• In "The Waterfall" approach, the whole process of software
development is divided into separate process phases.
• The phases in Waterfall model are:
• Requirement Specifications phase.
• Software Design.
• Implementation .
• Testing
• Maintenance.
• All these phases are cascaded to each other so that second phase is
started as and when defined set of goals are achieved for first phase
and it is signed off, so the name "Waterfall Model". All the methods
and processes undertaken in Waterfall Model are more visible.
Waterfall Model overview
Requirements
Analysis
Implementation
Design
Testing
Delivery and Installation
History of Waterfall (it was not waterfall)
• The waterfall development model originates in the
manufacturing and construction industries
• In 1970 Royce proposed what is now popularly referred to as
the waterfall model as an initial concept, a model which he
argued was flawed (Royce 1970).
• In Royce's original waterfall model, the following phases are
followed in order:
1. Requirements specification
2. Design
3. Construction (AKA implementation or coding)
4. Integration
5. Testing and debugging (AKA Validation)
6. Installation
7. Maintenance
How does it work(which most Activity involved)
• The project moves forward in a linear fashion just as
you would paddle down the stream.
• A preceding phase must be completed before the
next starts. And, once you go over a waterfall (i.e.,
complete a phase) you can't go back.
• This is the earliest method of structured system
development.
How does it work(cont…)
 System Conceptualization.
System Conceptualization refers to the consideration of all aspects of
the targeted business function or process, with the goals of
determining how each of those aspects relates with one another, and
which aspects will be incorporated into the system.
 Systems Analysis:
This is the second phase refers to the gathering of system
requirements, with the goal of determining how these requirements
will be accommodated in the system. Extensive communication
between the customer and the developer is essential.
 System Design:
Once the requirements have been collected and analyzed, it is necessary to
identify in detail how the system will be constructed to perform necessary
tasks. More specifically, the System Design phase is focused on the data
requirements
How does it work(cont…)
Coding:
Also known as programming or the coding phase, this step
involves the creation of the system software. Requirements and
systems specifications from the System Design step are
translated into machine-readable computer code.
Testing:
As the software is created and added to the developing system,
testing is performed to ensure that it is working correctly and
efficiently.
Waterfall Model (again)
Requirements
Analysis
Implementation
Design
Testing
Delivery and Installation
Waterfall Model derivable
• Project plan and feasibility report
• Requirements document (SRS : Software
Requirement Specifications)
• System design document
• Detailed design document
• Test plans and test reports
• Source code
• Software manuals (user manual, installation
manual)
• Review reports
When to use Waterfall
• Requirements are very well known
• Product definition is stable
• Technology is understood
• New version of an existing product
• Porting an existing product to a new platform.
Advantages
• A waterfall model helps find problems earlier on which
can cost a business less than if it was found later on.
• Requirements will be set and these wouldn't be changed.
• As everything is documented a new team member can
easily understand what's to be done.
• Implementers have to follow the design accurately
• Clear project objectives.
• Stable project requirements.
• Progress of system is measurable.
• Although the model is old fashioned, it remains a
resonable approach when requirements are well
understood.
• It is very simple model to implement.
Disadvantages
• Many believe it is impossible to make one stage of the projects life cycle
perfect.
• Difficult to estimate time and cost for each stage of the development
process.
• Constant testing of the design is needed.
• At the beginning of most projects there is often a great deal of
uncertainty about requirements and goals, and it is therefore difficult for
customers to identify these criteria on a detailed level. The model does
not accommodate this natural uncertainty very well.
Thank You

More Related Content

PPTX
What is waterfall
PPTX
Waterfall_Model_Presentation.pptx for s
PPTX
waterfall model.pptx
PDF
Waterfall Model (Software Engineering)
PPTX
Waterfall model
PPTX
Waterfall model
PPTX
software project management Waterfall model
PDF
Waterfall model
What is waterfall
Waterfall_Model_Presentation.pptx for s
waterfall model.pptx
Waterfall Model (Software Engineering)
Waterfall model
Waterfall model
software project management Waterfall model
Waterfall model

Similar to WaterFall Model.ppt (20)

PDF
waterfallmodelslide-220331073124 (2).pdf
PPTX
Waterfall Model PPT in Software Engineering
PPTX
Waterfall model of Software Engineering
PPTX
Waterfall Model
PPTX
Water fall model
PPTX
Water fall model
PPT
Chapter1 conventional softwaremanagement (1)
PPTX
WATERFALL MODEL
PPT
sdfsdfkjsdbusdbiusdhyusdbvyusdgusdbvusdbvyusdv
PPTX
Waterfall model
PPSX
Class waterfall
PPTX
11000122014_dheiufhieufhisudfhAVISHEK_ROY.pdf.pptx
PPTX
WaterFall Model & Spiral Mode
PPTX
Waterfall
PPTX
Models of SDLC (Software Development Life Cycle / Program Development Life Cy...
PPTX
Software cycles
PPTX
Software cycles
PPTX
Introduction-to-the-Waterfall-Model.pptx
PPTX
Waterfall-Model-A-Step-by-Step-Approach.pptx
PDF
Waterfall And The Agile Model
waterfallmodelslide-220331073124 (2).pdf
Waterfall Model PPT in Software Engineering
Waterfall model of Software Engineering
Waterfall Model
Water fall model
Water fall model
Chapter1 conventional softwaremanagement (1)
WATERFALL MODEL
sdfsdfkjsdbusdbiusdhyusdbvyusdgusdbvusdbvyusdv
Waterfall model
Class waterfall
11000122014_dheiufhieufhisudfhAVISHEK_ROY.pdf.pptx
WaterFall Model & Spiral Mode
Waterfall
Models of SDLC (Software Development Life Cycle / Program Development Life Cy...
Software cycles
Software cycles
Introduction-to-the-Waterfall-Model.pptx
Waterfall-Model-A-Step-by-Step-Approach.pptx
Waterfall And The Agile Model
Ad

Recently uploaded (20)

PPTX
Introduction_to_Human_Anatomy_and_Physiology_for_B.Pharm.pptx
PPTX
The Healthy Child – Unit II | Child Health Nursing I | B.Sc Nursing 5th Semester
PPTX
PPT- ENG7_QUARTER1_LESSON1_WEEK1. IMAGERY -DESCRIPTIONS pptx.pptx
PDF
Supply Chain Operations Speaking Notes -ICLT Program
PDF
Mark Klimek Lecture Notes_240423 revision books _173037.pdf
PDF
O7-L3 Supply Chain Operations - ICLT Program
PPTX
Introduction to Child Health Nursing – Unit I | Child Health Nursing I | B.Sc...
PDF
Microbial disease of the cardiovascular and lymphatic systems
PDF
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
PPTX
master seminar digital applications in india
PDF
STATICS OF THE RIGID BODIES Hibbelers.pdf
PDF
Abdominal Access Techniques with Prof. Dr. R K Mishra
PPTX
BOWEL ELIMINATION FACTORS AFFECTING AND TYPES
PPTX
Cell Structure & Organelles in detailed.
PDF
Insiders guide to clinical Medicine.pdf
PDF
Physiotherapy_for_Respiratory_and_Cardiac_Problems WEBBER.pdf
PPTX
Week 4 Term 3 Study Techniques revisited.pptx
PDF
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
PDF
Pre independence Education in Inndia.pdf
PPTX
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
Introduction_to_Human_Anatomy_and_Physiology_for_B.Pharm.pptx
The Healthy Child – Unit II | Child Health Nursing I | B.Sc Nursing 5th Semester
PPT- ENG7_QUARTER1_LESSON1_WEEK1. IMAGERY -DESCRIPTIONS pptx.pptx
Supply Chain Operations Speaking Notes -ICLT Program
Mark Klimek Lecture Notes_240423 revision books _173037.pdf
O7-L3 Supply Chain Operations - ICLT Program
Introduction to Child Health Nursing – Unit I | Child Health Nursing I | B.Sc...
Microbial disease of the cardiovascular and lymphatic systems
BÀI TẬP BỔ TRỢ 4 KỸ NĂNG TIẾNG ANH 9 GLOBAL SUCCESS - CẢ NĂM - BÁM SÁT FORM Đ...
master seminar digital applications in india
STATICS OF THE RIGID BODIES Hibbelers.pdf
Abdominal Access Techniques with Prof. Dr. R K Mishra
BOWEL ELIMINATION FACTORS AFFECTING AND TYPES
Cell Structure & Organelles in detailed.
Insiders guide to clinical Medicine.pdf
Physiotherapy_for_Respiratory_and_Cardiac_Problems WEBBER.pdf
Week 4 Term 3 Study Techniques revisited.pptx
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
Pre independence Education in Inndia.pdf
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
Ad

WaterFall Model.ppt

  • 2. Agenda • Waterfall Model overview • Waterfall Model History (it was not waterfall) • How does it work(which most Activity involved) • Model derivable • When to use • Advantages • Disadvantage
  • 3. Waterfall Model overview • Waterfall approach was first Process Model to be introduced and followed widely in Software Engineering to ensure success of the project. • In "The Waterfall" approach, the whole process of software development is divided into separate process phases. • The phases in Waterfall model are: • Requirement Specifications phase. • Software Design. • Implementation . • Testing • Maintenance. • All these phases are cascaded to each other so that second phase is started as and when defined set of goals are achieved for first phase and it is signed off, so the name "Waterfall Model". All the methods and processes undertaken in Waterfall Model are more visible.
  • 5. History of Waterfall (it was not waterfall) • The waterfall development model originates in the manufacturing and construction industries • In 1970 Royce proposed what is now popularly referred to as the waterfall model as an initial concept, a model which he argued was flawed (Royce 1970). • In Royce's original waterfall model, the following phases are followed in order: 1. Requirements specification 2. Design 3. Construction (AKA implementation or coding) 4. Integration 5. Testing and debugging (AKA Validation) 6. Installation 7. Maintenance
  • 6. How does it work(which most Activity involved) • The project moves forward in a linear fashion just as you would paddle down the stream. • A preceding phase must be completed before the next starts. And, once you go over a waterfall (i.e., complete a phase) you can't go back. • This is the earliest method of structured system development.
  • 7. How does it work(cont…)  System Conceptualization. System Conceptualization refers to the consideration of all aspects of the targeted business function or process, with the goals of determining how each of those aspects relates with one another, and which aspects will be incorporated into the system.  Systems Analysis: This is the second phase refers to the gathering of system requirements, with the goal of determining how these requirements will be accommodated in the system. Extensive communication between the customer and the developer is essential.  System Design: Once the requirements have been collected and analyzed, it is necessary to identify in detail how the system will be constructed to perform necessary tasks. More specifically, the System Design phase is focused on the data requirements
  • 8. How does it work(cont…) Coding: Also known as programming or the coding phase, this step involves the creation of the system software. Requirements and systems specifications from the System Design step are translated into machine-readable computer code. Testing: As the software is created and added to the developing system, testing is performed to ensure that it is working correctly and efficiently.
  • 10. Waterfall Model derivable • Project plan and feasibility report • Requirements document (SRS : Software Requirement Specifications) • System design document • Detailed design document • Test plans and test reports • Source code • Software manuals (user manual, installation manual) • Review reports
  • 11. When to use Waterfall • Requirements are very well known • Product definition is stable • Technology is understood • New version of an existing product • Porting an existing product to a new platform.
  • 12. Advantages • A waterfall model helps find problems earlier on which can cost a business less than if it was found later on. • Requirements will be set and these wouldn't be changed. • As everything is documented a new team member can easily understand what's to be done. • Implementers have to follow the design accurately • Clear project objectives. • Stable project requirements. • Progress of system is measurable. • Although the model is old fashioned, it remains a resonable approach when requirements are well understood. • It is very simple model to implement.
  • 13. Disadvantages • Many believe it is impossible to make one stage of the projects life cycle perfect. • Difficult to estimate time and cost for each stage of the development process. • Constant testing of the design is needed. • At the beginning of most projects there is often a great deal of uncertainty about requirements and goals, and it is therefore difficult for customers to identify these criteria on a detailed level. The model does not accommodate this natural uncertainty very well.

Editor's Notes

  • #2: This presentation demonstrates the new capabilities of PowerPoint and it is best viewed in Slide Show. These slides are designed to give you great ideas for the presentations you’ll create in PowerPoint 2010! For more sample templates, click the File tab, and then on the New tab, click Sample Templates.