2.2.1. Waterfall Model

A linear, step-by-step model where each phase must be completed before the next begins.

The Waterfall Model is a sequential approach to software development. It means that once one phase is finished, the team cannot return to it to make changes. The phases must flow in one direction, hence the term 'waterfall.' For example, if the requirements are gathered but later need to change, it's difficult because the team has to go back to the beginning.

Imagine a factory assembly line where each worker has a specific task. The first worker adds parts to a product, and before the next worker can begin, the first must finish their part completely. If an error is found in the first step after the product has moved on, the entire line must be stopped to fix it.

1. Requirements: Gather and document all requirements
2. Design: Define system architecture and design
3. Development: Build the software
4. Testing: QA team tests the software
5. Deployment: Release to production
6. Maintenance: Fix issues and make minor enhancements

The Waterfall Model consists of six key phases, each with specific tasks. First, you gather all requirements needed for the software (Requirements phase). Next, you design the system architecture, which outlines how the software will function (Design phase). After that, actual coding happens in the Development phase. Following development, the software is tested thoroughly by the QA team to find defects (Testing phase). Once testing is complete and the product is ready, it is deployed to users (Deployment phase). Finally, ongoing maintenance includes fixing bugs and making updates (Maintenance phase).

Think of it like building a house. First, you need to design the blueprints (Requirements and Design). Then you gather materials and build the structure (Development). After the house is built, inspectors come in to check for problems (Testing). Once everything is approved, the house is ready for people to live in (Deployment), and after moving in, small repairs and upgrades might be required (Maintenance).

● QA is usually involved after development, making early defect prevention difficult. ● Requirements and test plans are finalized upfront.

In the Waterfall Model, Quality Assurance (QA) typically occurs after the development phase. This timing means that any defects or issues often arise late in the process, making it tough to fix them without backtracking. Also, QA needs to create test plans before starting their testing, which can lead to missing unexpected issues since it’s all based on initial requirements. This procedural block can impact the overall quality of the final product.

Imagine you are preparing a big meal for guests. You prep everything based on a recipe and cook, but only after serving do you realize that the soup is too salty. Since you've already plated everything, making changes becomes cumbersome and delays serving. If you had taste-tested throughout the cooking process, you could have adjusted ingredients along the way.

● Easy to manage, well-documented

One major advantage of the Waterfall Model is its simplicity and structured nature. Each phase is clearly defined and documented, which makes it easier for teams to track progress and ensure that each step is completed before moving on. This clear documentation can be very beneficial for larger teams or projects that need to adhere to strict regulations or standards.

Consider reading a book. Each chapter builds upon the previous one, and you often cannot fully understand chapter two without first reading chapter one. The organization helps readers follow the storyline logically and ensures comprehension.

● Inflexible to changes, late QA involvement

While the model has its advantages, it also has downsides. The primary drawback is its inflexibility; once a phase is completed, revisiting it is not straightforward. This rigidity can make it challenging to adapt to new insights or changing requirements. Additionally, because QA comes in late in the process, there is a higher risk of defects being discovered too late, which can lead to increased costs and delays.

Imagine planning a vacation. If you book your flights first, then decide on your accommodation and destinations, changing your plans becomes complicated. If a better flight deal comes up after you've booked, you might miss out on it due to the rigidity of your initial plan. This links back to the challenge of making changes in the Waterfall Model.

--