Water Fall Model:
1. It is a most straightforward model, which expresses that the stages are coordinated in a direct request.
2. The model was originally proposed by Royce.
3. The various phases in this model are
The primary point of the feasibility study action is to decide if it would be monetarily and in fact achievable to foster the item.
The point of the prerequisite examination is to comprehend the specific necessities of the client and to archive them appropriately.
This phase is concerned with
1. Recognizing programming parts like capacities, information streams and information stores.
2. Specifying software structure.
3. Keeping a record of plan choices and giving blue prints to the execution stage.
It involves the translation of the design specifications into source code. It additionally includes exercises like troubleshooting, documentation and unit testing of the source code.
It involves two kinds of activities
a) Integration Testing:
It involves testing of integrating various modules and testing their overall performance due to their integration.
b) Acceptance Testing:
It includes arranging and execution of different sorts of tests to exhibit that the carried out programming framework fulfils the prerequisites expressed in the necessities record.
In this phase the activities include
a) Corrective Maintenance:
Remedying blunders that were not found during the item improvement stage.
b) Perfective Maintenance:
Improving the execution of the framework, and upgrading the functionalities of the framework as per client’s prerequisites
c) Adaptive Maintenance: Adaptation of software to new processing environments.
Advantages of Water Fall Model:
- All Phase are clearly defined.
- One of the most methodical techniques for programming improvement.
- It is simple and easy to use.
Disadvantages of Water Fall Model:
- It is often difficult for the client to state all requirements explicitly.
- Imperfect model for complex and object oriented projects.
- Not good for long and ongoing projects.
So in conclusion, the software development life cycle (SDLC) waterfall model is still effective for certain projects that are set within a target timeline or forecast. Besides, the technique limits the concentration to give a more complete comprehension of all product expectations, setting assumptions all along. The stage doors between each stage additionally guarantee that each stage is finished prior to proceeding onward to the following, and there is little customer connection which could create setbacks all through advancement. We use software development life cycle (SDLC) water fall model when the requirements are constant and a project is small. This model isn’t suitable for complex and object oriented projects.