Scribd
Upload
6 views2 pages

Waterfall Model

The Waterfall Model, introduced by Winston W. Royce, is a linear and document-driven software development life cycle (SDLC) that is best suited for small and simple projects with well-defined requirements. It consists of five phases: Communication, Planning, Modelling, Construction, and Deployment, and offers advantages such as simplicity and ease of management. However, it has significant disadvantages, including inflexibility to changes and high risk due to testing occurring only at the end of the process.

Uploaded by

cryptomineunit01
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views2 pages

Waterfall Model

The Waterfall Model, introduced by Winston W. Royce, is a linear and document-driven software development life cycle (SDLC) that is best suited for small and simple projects with well-defined requirements. It consists of five phases: Communication, Planning, Modelling, Construction, and Deployment, and offers advantages such as simplicity and ease of management. However, it has significant disadvantages, including inflexibility to changes and high risk due to testing occurring only at the end of the process.

Uploaded by

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

Q.

Waterfall Model with diagram, Advantages and


Disadvantages. (referred from V-model)
Ans:

Winston W. Royce
● Waterfall Model is an prescriptive process model which is a software development life cycle
(SDLC). This model was introduced by Winston.W.Royce.
● The Waterfall Model is a High Discipline Model. In this model each step is performed in an
linear sequential manner.which means one step is performed one after another.
● Waterfall Model is Document-Driven, which means it heavily depends on documentation
process like: requirement documentation, test documentation, maintenance
documentation e.t.c.
● This model is simple and easy to understand and implement if this model goes in a
sequential manner.
● Waterfall Model is suitable for small and simple projects where requirement and objective of
the project is well known, due to this Rigorous planning is required.
● This model is risky and uncertain,as testing is done first time at the end of the SDLC, which
may cause failure. Which means the test is done after the software is ready at the end stage.

● Here are the following stages/phases of Waterfall model:


1. Communication: The “First stage/phase” of Waterfall model communication and
collaboration with the customer and the stakeholder are done which include tasks like
requirement gathering and other similar tasks.
2. Planning: the next phase is planning in which tasks/activities like: Project
Estimation, Projection Scheduling,Project Tracking e.t.c.
3. Modelling: In modelling stage software design is created by which the developer,
stakeholder and the user can better understand the software design and the software
requirements.
4. Construction: In the Construction phase the actual coding of the software product is
done on the basis of requirement gathering ,planning and design modelling which
involve tasks like: Code Construction, Code Testing e.t.c
5. Deployment: The last stage/phase of the waterfall model is Deployment complete or
incomplete software is delivered to the customer, the customer uses the software
product and provides feedback, then the software developer makes
changes/updates in software on the basis of feedback to supply a new better version
of software.
● Advantages of waterfall model:
1. Waterfall model is Simple, quick and time saving and easier to manage.
2. It is very easy to understand and apply
3. This is a highly disciplined model and Phases are completed one at a time.
● Disadvantages of waterfall:
1. Waterfall models are not flexible to changes, have high risk and uncertainty and are
very rigid.
2. Waterfall model is not suitable for long, big, ongoing, complex and object-oriented
projects.

You might also like