Scribd
Upload
12 views

Waterfall Model

Notes

Uploaded by

suman.2345567890284
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 views

Waterfall Model

Notes

Uploaded by

suman.2345567890284
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/ 3

WATERFALL MODEL

It is a traditional model.There are 7 stages in Waterfall model:

1. Requirement Collection
Here the Business Analyst/Product Analyst collects the requirement from the
customer.
Requirement is collected in the form of CRS. CRS is converted to SRS –
meaning business language is converted to software language by BA/PA.

CRS — Customer Requirement Specification


It is the requirement document in the form of customer business language

SRS — Software Requirement Specification


It is the requirement document in the form of software language

BA — Business Analyst
BA converts the CRS into SRS in service-based company

PA — Product Analyst
PA converts the CRS into SRS in product-based company

Service based companies


They provide service and develop software for other companies according to their
requirement.
Ex: Wipro, Infosys, TCS, Cognizant

Product based companies


They develop their own software and sell it to other companies which may need the
software and earn profit.
Ex: Oracle, Microsoft, Google
2. Feasibility Study/ Analysis
* It is done by a team consisting of Project Manager, BA, Architect, Finance team
and HR team.
* Here we check:
i. Technical Feasibility: We check technology is available or not to develop the
software. It is done by Architects.
ii. Financial Feasibility: We check budget is available or not to develop the
software. It is done by Finance team.
iii. Resource Feasibility: We check resources are available or not to develop
the software. It is done by HR team.
* Architect will do technical feasibility study and tell which technology to use in
order to develop the software. Any Sr Developer can become an Architect.

3. Design
Here we do High Level Design (HLD) and Low-Level Design (LLD) of the software
HLD — High Level Design
> It is the architecture of the software product to be developed
> It is done by Architects and Sr Developers
LLD — Low Level Design
> It describes how each and every feature in the product should work and how each
and every component should work
> It is done by Sr Developers

4. Coding
* Here we start building the software/ writing the code for the product
* It is done by Sr Developers, Jr Developers and Freshers

5. Testing
* After coding we start testing wherein, we identify defects in the software
* It is done by test engineers
Drawbacks of Developers involved in testing the software

1. They will always see the product from positive point of view, they will never see
the product from negative point of view
2. They will always have over confidence that whatever they have built, works
3. They consume the time allocated for testing to build the product and they say time
is not there to test
4. Even though they know that bugs are there, they might hide it and not fix it

6. Installation
* After the software is developed and tested, it is installed in the customer's place
for using
* It is done by Installation Engineers

7. Maintenance
After the software is installed and used, if the customer finds any defect, the software
company will fix it according to the agreement i.e., if the defect is found in the
Maintenance period, then the software company will fix the defect free of cost.
Advantages
i. Requirement/ Design doesn’t change, so we get a stable product
ii. Quality of software is good

Disadvantages
i. Backtracking is not possible. For example, we can’t change the requirement once
the design stage is completed means the requirement is freezed and hence this model
is not flexible.
ii. Requirement is not tested, design is not tested, if there is bug in the requirement,
it will flow till the end and leads to lot of rework.
iii. It is traditional model where developers were involved in testing.

Applications/ When to go for Waterfall model?


1. Whenever we are building simple/ small applications.
2. Whenever we go for short term projects
3. Whenever we are sure that req. is not going to change
Ex: Calculator, Calendar

You might also like