Professional Documents
Culture Documents
2.1 Waterfall Process Model
2.1 Waterfall Process Model
BRAC University
New
t
Projec
Team Lead
2
3
M
od
el
A
M
od
el
B
Mo
d el
C
Small Customer
We know What Base
we Want
4
Waterfall Model
A sequential methodology for software project
management.
5
Requirement
Analysis
Design
Coding
Testing
Deployment
Maintenance
6
Requirement Collection
Client Meeting
Collect Requirements
7
1. Address the problem
E D
2. Identify the feasible and non-feasible requirements
O V
R
3. Identify how the software will meet the customer
requirements
P P
8 A
Design
E D
O V
P R
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
D
are converted to code modules on after
E
another.
O V
P R
10 A P
Testing
V E
R O
P P
11 A
Deployment and Maintenance
1. The software goes in production in actual
Location A information technology environment,
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
12
When to choose Waterfall Model
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.
15
16