This document discusses the waterfall model of the software development life cycle (SDLC). It describes the key phases of the waterfall model as requirements, design, implementation, integration and testing, verification, deployment, and maintenance. Each phase must be completed before moving to the next in a linear fashion. The waterfall model provides structure, sets requirements stability, and is good for management control. However, it requires all requirements to be known upfront and doesn't allow for much flexibility or customer feedback during development. The waterfall model is best suited when requirements are well defined and the technology is understood.

1. Software Development
Life Cycle (SDLC)
Using Waterfall Model
Guided by Miss Priyanka Roy
Created & Presented by
Name: Shubham Gupta
University Roll no: 12000221054
Branch: Information Technology
Subject Code: ESC_501

2. SYSTEM DEVELOPMENT
LIFE CYCLE OVERVIEW
 Software Development Life Cycle(SDLC) is a process used
by the software industry to design, and develop and test
high quality software.
 The SDLC aims to produce a high-quality software that
meets or exceeds customer expectations, reaches
completion within time and cost estimates.
 The life cycle defines a methodology for improving the
quality of software and the overall development process.

3. SDLC MODEL

4. 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. WATERFALL MODEL

6. STEP IN WATERFALL MODLE
 Requirements: Requirements is the initial step in waterfall model.
All possible requirements of the system to be developed are
captured in this phase and documented in a requirement
specification document. In this steps user demands the entire
requirement for the software development.
 Design: This is the second step in waterfall model. This system
design helps in specifying hardware and system requirements
and helps in defining the overallsystem architecture.
 Implementation: It is very important part of waterfall model. After
requirements and design the next step in implementation. With
inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next
phase. Each unit is developed and tested for its functionality,
which is referred to as Unit Testing. The main purpose of these
steps is to execute the program.

7. STEP IN WATERFALL MODLE
 Intergration and Testing: Integration and Testing – All the units
developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire
system is tested for any faults and failures
 Verification: In these steps the entire systems will be tested for
any faults and failures. Once the functional and non-functional
testing is done the product is deployed in the customer
environment or released into the market.
 Deployment of Sytem:Once the functional and non-functional
testing is done; the product is deployed in the customer
environment or released into the market.
 Maintenance: In these last steps there are some issues which
come up in the client environment. In this steps the issue will be
fixed, patches are released. Maintenance is done to deliver
these changes in the customer environment.

8. Waterfall Strengths
 Easy to understand, easy to use
 Provides structure to inexperienced
staff
 Milestones are well understood
 Sets requirements stability
 Good for management control (plan,
staff, track)
 Works well when quality is more
important than cost or schedule

9. Waterfall Deficiencies
 All requirements must be known upfront
 Deliverables created for each phase are
considered frozen – inhibits flexibility
 Can give a false impression of progress
 Does not reflect problem-solving nature of
software development – iterations of phases
 Integration is one big bang at the end
 Little opportunity for customer to preview
the system (until it may be too late)

10. When to use the Waterfall Model
 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.

11. THANK YOU