subject: Discussing In And Outs Of Waterfall Method For Software Development [print this page] Software development methodologies are basically concerned with the organizational aspect of the development process. Rather than putting less emphasize on technical side, these methodologies help us to decide what are the steps that should be followed during software development. In this article, we will try to put some light on the "Waterfall Method" of software development.
Introduction:
Although there are quite a few tried and trusted software development methodologies, still waterfall method is still the most popular one among the all. Despite being the oldest one, nearly 70% of the organizations follow this method. This method comprises of few definite phrases where the next step can be followed only if the last one is being completed. A software development company, following the waterfall methodology, needs to start with heavy documentation where the requirements, plan and sign-offs are listed and documented.
After the initial stage of documentation gets over, sequential phases of designing, coding, test-casing, optional documentation, verification (alpha-testing), validation (beta-testing), and finally deployment/releasing take place. Let's discuss the 10 steps of Waterfall Methodology here:
1. Initiation Phase: In this phase an opportunity gets spotted and is proposed in a formal Concept Proposal Document.
2. System Concept Phase: In this phase, several deliverables are taken care of, like: system boundary, cost benefit analysis, risk management plan, feasibility study (economical, operational and technical) etc.
3. Planning Phase: In this phase of software development the project management plan is developed, which can be tracked to determine the progress of the MIS team.
4. Requirements Analysis Phase: In this phase, the team analysis the requirement and segregate it to be divided among the team members. Depending upon the requirement list, members with different responsibilities will start working on their parts.
5. Design Phase: A software development company will then design the product's architecture.
6. Development Phase: The design is converted into reality and then white box tested by the development team.
7. Integration and Test Phase: In this phase the product gets tested by the development team first, then by the 'quality assurance' team and finally by the end user.
8. Implementation or Deployment Phase: After doing fruitful testing and fixing all bugs, the product gets deployed on the platform for which it meant to be.
9. Operation and Maintenance Phase: In this phase, the product gets monitored to ensure it continues to meet performance requirements. Periodic in-process reviews are conducted to suggest ways on improving the system.
10. Disposition Phase: In this phase all the data regarding the product gets archived so that the reusable components can be saved to be used on any later reference. This phase enables the team to move on to a new project.
