Scribd
Upload
12 views16 pages

1.1.1 Waterfall Process Model

1. The document describes the waterfall model, a sequential software development methodology where each phase must be completed before the next can begin, from requirements analysis through design, coding, testing, deployment and maintenance. 2. The waterfall model involves collecting requirements from clients, creating a logical and physical design, coding by converting the design into a working software project, testing against requirements, deploying the software for user testing and feedback, and ongoing maintenance. 3. The waterfall model is best for projects with well-defined requirements, small or short-term projects, and where resources and technologies are stable rather than dynamic. However, it does not allow for changes between phases and code reuse.

Uploaded by

sudipta.nandi.sarna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views16 pages

1.1.1 Waterfall Process Model

1. The document describes the waterfall model, a sequential software development methodology where each phase must be completed before the next can begin, from requirements analysis through design, coding, testing, deployment and maintenance. 2. The waterfall model involves collecting requirements from clients, creating a logical and physical design, coding by converting the design into a working software project, testing against requirements, deploying the software for user testing and feedback, and ongoing maintenance. 3. The waterfall model is best for projects with well-defined requirements, small or short-term projects, and where resources and technologies are stable rather than dynamic. However, it does not allow for changes between phases and code reuse.

Uploaded by

sudipta.nandi.sarna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

CSE 470 – Waterfall Model

BRAC University
New
t
Projec

Team Lead

2
3
M
A ode
l

Mo
de
lB
Mo
lC de
Small Customer
We know Base
What we
Want

4
Waterfall Model
A sequential methodology for software project
management.

5
Requirement
Analysis

Design

Coding

Testing

Deployment

Maintenance

6
Requirement Collection

It starts with the concept about what


the customer wants to do.

Client Meeting
Collect Requirements

7
1.
2.
Address the problem
Identify the feasible and non-feasible requirements
VE D
3. Identify how the software will meet the customer
requirements
P RO
8 A P
Design

Creates the logical and physical design of the


software project

V E D
P RO
9
A P
Coding
1. We need to build it first
2. Coding can not start until design is fixed
properly
3. Starts with converting the design in actual
running software.
4. The design is spilt into blocks, and blocks
are converted to code modules on after

D
another.

OV E
PP R
10 A
Testing

1. Check the software against the


requirements set at Requirement Analysis
Phase.
It works 2. In case of any problem, that problem is
perfectly !! fixed in the code.

That does not


work !!

V E D
RO
11 A PP
Deployment and Maintenance
1. The software goes in production in actual
Location information technology environment,
A specially goes to user environment.
2. Step by step deployment and maintenance
performed
3. If anything goes wrong here will be
maintained and resolved by the team.
4. Feedback may also be collected

Location B Location C Location D

12
When to choose Waterfall Model

Requirements are well known

Small scale and short term project

Resources are available and trained

Technological tools required are not


dynamic, instead are stable

13
Advantages & Disadvantages
1. Simple to Use and Easy
2. Stages go one by one, so sudden changes
can not create confusions
3. Any changes is done only in Development
stage, so no need to get back and change
everything.

1. While completing a stage, it freezes all the


subsequent stages.
2. No way to verify the design
3. Once in testing phase, no more features
can be added
4. Code Reuse not possible
14
Example Case
1. One of your uncle requested you to develop an
accounting calculator for his local shop.
2. Your start-up company wants to develop an accounting
calculator for super shops.

Will you use Waterfall model for both Case 1 and


2?

15
16

You might also like