Before learning the waterfall model let you know about:
Software bidding: A proposal to develop new software is called as ‘software bidding’
If a proposal came from the customer point of view then it is called as “software project bidding”.
If a company will study the needs of the market and develop the software then that type of proposal is called as “software product bidding”
Note: The above waterfall model is also called as the “Linear Sequential Model”
When requirements are clear, organization can follow waterfall model.
Explanation of above diagram:
- From the above diagram at first software bidding will be done between the CEO of
company and customer or client. Then after bidding, the CEO will conduct the
meeting with all the project managers (PM) in the company called as “kick of
- In that meeting CEO will make an announcement about that new project to
handle that project any one of the project manager will be selected. Then that
project manager will give a project initiation note (PIN) to CEO.
- Then PM will assign the work to the business analyst (BA) to gather all the
requirements from the customer.
- Then BA will submit all the gathered requirements to the system analyst (SA) to design in order to do the analysis or detailed planning which is going to submit it to the PM. Then PM will approve that planning done by SA.
- Then SA will submit that document to the technical architect (TA).
- Then designers will do the design which consists of HLD and LLD’s.
- Based on that design programmers will do the coding and that corresponding programmers will test the developed code.
- Then after testing that s/w few programmers will be selected for onsite and release the s/w.
- Then change for control board (CCB) people will do the maintenance/support of that s/w.
Advantages of waterfall model:
- The main strength of waterfall model is its simplicity and it is very easy to use.
- Output generated at the end of each phase is reviewed and approved and hence
it has high visibility.
- Minimal resources are required.
- It is less expensive as minimal resources are required.
- This model is preferred for smaller projects where requirements are well clear.
- Time spent early on making sure that requirements and design are absolutely
correct saves much time and effort later.
Disadvantages of waterfall model:
- It is difficult to implement any changes in the requirement.
- No working software is produced until the last stage of the life cycle.
- It is expensive to incorporate any changes once the project is in to testing phase.
- Not suitable for complex projects, long term projects.
- Not suitable when requirement are not clear.