Last updated on June 13th, 2020 at 08:39 pm
Linear Sequential Model/Waterfall Model/Classic Life Cycle
1. Communication :
This activity involves heavy communication with customers and other stakeholders in order to gather requirements and other related activities.
2. Planning :
Here a plan to be followed will be created which will describe the technical tasks to be conducted, risks, required resources, work schedule etc.
3. Modeling :
A model will be created to better understand the requirements and design to achieve these requirements.
4. Construction :
Here the code will be generated and tested.
5. Deployment :
Here, a complete or partially complete version of the software is represented to the customers to evaluate and they give feedbacks based on the evaluation.
Disadvantages of Linear Sequential Model:
- Real projects rarely follow the linear sequential model. Although the linear model can accommodate iteration, it does so indirectly. As a result, changes can cause confusion as the project team proceeds.
- It is often difficult for the customers to state all the requirements explicitly. This model requires this and has difficulty accommodating the natural uncertainty.
- The customers must have patience. A working version of the program will not be available until late in the project time-span. A major mistake, if undetected until the working program is reviewed, can be disastrous.
Today, software work is fast-paced and subject to never ending stream of changes. Linear sequential model is inappropriate for this, but when the requirements are fixed and work is preceded in a linear manner, linear sequential model will be a useful process.