SDLC Waterfall model

Waterfall methodology is the most widely recognized SDLC model.

It was the first process model.

Another name for the waterfall model is the linear sequential life cycle model.

Each phase in the waterfall model must finish before moving on to the next stage.

In the waterfall model the process divided into separate and different phases.

The outcome of the previous phase serves as the input of the next phase.

It’s straightforward and simple, but sometimes complicated projects require more steps.  sdlc

Some software is better repeating various stages multiple times or even rearranging them a bit. sdlc

While the Waterfall Model shortens the project and offers an almost effortless explanation of the process and simple distribution of resources, the overall concern should always be on what is best for the proposed software. sdlc

This is certainly the easiest to keep track of stages and records, but it doesn’t have room for testing during the process and is not the best option for those products that require constant changes. sdlc

Though it is great for smaller projects that are made to be stable, it won’t give much insight into overall performance until later in development. sdlc

There are six phases in the waterfall model, including: sdlc

• 1. Requirement Gathering and analysis sdlc
• 2. System Design sdlc
• 3. Implementation sdlc
• 4. Integration and Testing sdlc
• 5. Deployment of system sdlc
• 6. Maintenance

Applications using Waterfall sdlc

The waterfall model used when: sdlc

• All the requirements are precise, documented, and fixed. sdlc
• No vague requirements. sdlc
• Smaller projects. sdlc

Why should you use Waterfall Model? sdlc

• The waterfall model follows a strict process. sdlc
• A phase must complete before moving to the next phase.
• It is simple and easy to understand. sdlc
• The tasks arranged efficiently. sdlc
• All the stages defined clearly.
• Capture the outcome of the project and process.