Waterfall Model in SDLC: SDLC has various models designed which have their advantages and disadvantages. Waterfall model is a traditional SDLC model which will be discussed in this tutorial. It’s a straightforward and basic structure which can be effectively understandable by software developers and testers. It is the first model of SDLC to be presented for software development.
In this article, you will learn-
What is The Waterfall Model?
WATERFALL MODEL is a sequential model that divides software development into pre-defined phases. Each phase should be finished before the next phase can start with no cover between the phases. Each phase is designed for performing specific activity during the SDLC phase. It was presented in 1970 by Winston Royce.
Different Phases of Waterfall Model in Software Engineering
|
Different phases |
Activities acted in each stage |
|
Necessity Gathering stage |
During this phase, point by point necessities of the software system to be |
|
Design Stage | Plan the programming language, for Example Java, PHP, .net or then again database like Or on the other high-level |
|
Build Stage |
After design stage, it is built stage, that is only coding the software |
|
Test Stage |
In this stage, you test the software to confirm that it is worked |
|
Deployment stage |
Deploy the application in the respective environment |
|
Maintenance stage |
When your system is prepared to use, you may later require change the code |
When to use SDLC Waterfall Model
Waterfall model can be used when
• Requirements are not changing often
• Application isn’t complicated and big
• Project is short
• Requirement is clear
• Environment is steady
• Technology and tools used are not dynamic and is steady
• Resources are accessible and prepared
Advantages and Disadvantages of Waterfall-Model
| Advantages | Dis-Advantages |
| • Before the next phase of development, each stage should be completed | • Error can be fixed only during the phase |
| • Suited for more smaller projects where necessities are well defined | • It isn’t attractive for complex project where prerequisite changes as often as possible |
| • They ought to perform quality assurance test (Verification and Validation) before to finishing each stage | • Testing period comes quite late in the developmental process |
| • Elaborate documentation is done at each phase of the software’s development cycle | • Documentation involves a lot of time of developers and testers |
| • Project is totally subject to extend team with minimum client intervention | • Clients significant feedback can’t be incorporated with ongoing development stage |
| • Any changes in software is made during the process of the development | • Small changes or errors that arise in the finished software may cause a lot of issues |
Related:
SDLC: Phases & Models of Software Development Life Cycle
Software Engineer vs Software Developer: What’s The Difference?
10 Steps to Become a Software Engineer/Developer
What is Software Engineering? Definition, Basics, Characteristics
Thanks for reading! We hope you found this tutorial helpful and we would love to hear your feedback in the Comments section below. And show us what you’ve learned by sharing your projects with us.
