Short Note on Waterfall Model
Waterfall Model :-
The waterfall model of the software life
cycle was first put forward by Royce in 1970.
There are many variants of the waterfall
model depending on the organization that use the model and the specific
project. The linear sequential waterfall model is shown below –
 |
| Fig - Linear
Sequential Waterfall Model |
1
. Feasibility Study.
2
. Requirements analysis and specification.
3
. Design and specification.
4
. Coding and model testing.
5
. Integration and System testing.
6
. Delivery and
7
. Maintenance.
Advantage
of Waterfall Model :-
1
. The waterfall model forces discipline in the software development process.
Over coming unstructured code and fixed process.
2
. The waterfall model is document oriented. Design documentation, code
documentation, database manual, user manual, operational manual etc. Make it
easier for maintenance.
3
. The waterfall model has a nicely understood theoretical flow in a cascading
manner.
4
. The waterfall model reflects engineering practices.
5
. The software process models based on this approach will remain the norm for
large hardware, software system developments.
Disadvantage
of Waterfall Model :-
1
. The model is linear, rigid and monolithic.
2
. The documentation is also a disadvantage because the user does not understand
and hence cannot contribute properly during any change.
3
. In practice, linear progression is very tiresome and any mistake found at a
later stage may need re work from the beginning stage.
4
. The model does not recognize the role of iteration in the software process.
5
. The time and cost estimate with limited amount of information in the
beginning results in faulty estimates of the project.
6
. The pre mature freezing of requirements may lead to badly structure system.
|
Subscribe to:
Post Comments
(
Atom
)
No comments :
Post a Comment