Waterfall Model in Software Development Life Cycle(SDLC)
a thread...
a thread...
One of the most popular traditional SDLC models - The Waterfall Model...
It's one of the SDLC models it of many, which is used for software development, there're several phases in this model.
It's one of the SDLC models it of many, which is used for software development, there're several phases in this model.
Seven Different Phases:
1. Requirement Gathering
2. Analysis
3. Design
4. Development
5. Testing
6. Deployment
7. Maintenance
1. Requirement Gathering
2. Analysis
3. Design
4. Development
5. Testing
6. Deployment
7. Maintenance
Let's look at the above diagram carefully,
Consider each phase as a step (of a ladder), and water is flowing from top to bottom. That's why it's called waterfall.
The Project flows only in forward direction i.e. After completing one phase, only the next phase is started.
Consider each phase as a step (of a ladder), and water is flowing from top to bottom. That's why it's called waterfall.
The Project flows only in forward direction i.e. After completing one phase, only the next phase is started.
1. Requirement Gathering (RG):
In this phase, the technical team sits with the client and discusses all the client requirements, he/she wants in the software.
The client has to state all the requirements in this phase itself, he cannot add anything later.
In this phase, the technical team sits with the client and discusses all the client requirements, he/she wants in the software.
The client has to state all the requirements in this phase itself, he cannot add anything later.
The requirement Gathering phase forms the basis of the entire SDLC process, Estimations, System Architecture, Team Size, etc.
That's why in this phase multiple meetings happen and all the important features client wants, need to be stated in this phase.
That's why in this phase multiple meetings happen and all the important features client wants, need to be stated in this phase.
2. Analysis:
In this stage, the technical team sits together to discuss the feasibility of the requirements and analyzes all the requirements thoroughly.
Sometimes for complex projects, Requirement Gathering and Analysis are combined into a single phase.
In this stage, the technical team sits together to discuss the feasibility of the requirements and analyzes all the requirements thoroughly.
Sometimes for complex projects, Requirement Gathering and Analysis are combined into a single phase.
For complex projects, sometimes requirements are not feasible so need to be discussed with the client for modifications.
The client modifies it, and there are some back and forth meeting that happens that's why the two phases are combined to save time & effort.
The client modifies it, and there are some back and forth meeting that happens that's why the two phases are combined to save time & effort.
3. Design
When entering this phase, all the requirements are locked.
The team has clear visibility of the requirement.
Now, they start working on Designing the system.
Frontend team working on UI/UX.
The backend team works on designing system architecture.
When entering this phase, all the requirements are locked.
The team has clear visibility of the requirement.
Now, they start working on Designing the system.
Frontend team working on UI/UX.
The backend team works on designing system architecture.
4. Development
Now, it's time to start the development.
Development is started for the frontend and backend parts.
Now, it's time to start the development.
Development is started for the frontend and backend parts.
5. Testing
In this phase, QA gets involved and starts performing different kinds of testing on software.
Like:
1. System Testing
2. Smoke Testing
3. Regression Testing
4. Integration Testing
and many more...
In this phase, QA gets involved and starts performing different kinds of testing on software.
Like:
1. System Testing
2. Smoke Testing
3. Regression Testing
4. Integration Testing
and many more...
6. Deployment
Once QA gives the green signal, our project is ready to be deployed on the client's side.
The team deploys the software on the client-side, and handover to the client.
Once QA gives the green signal, our project is ready to be deployed on the client's side.
The team deploys the software on the client-side, and handover to the client.
7. Maintenance
The client performs basic testing and if found bugs then those bugs are fixed as part of maintenance.
Also sometimes clients want to request some minor changes so those can also be carried out in this phase.
The client performs basic testing and if found bugs then those bugs are fixed as part of maintenance.
Also sometimes clients want to request some minor changes so those can also be carried out in this phase.
When to use Waterfall?
1. Time to mark is very less
2. Project is small
3. Client knows what he needs
4. Client has fix budget
Because we can freeze all requirements beforehand and estimate the time and project cost easily
What are the other reasons? Let me in comments.
1. Time to mark is very less
2. Project is small
3. Client knows what he needs
4. Client has fix budget
Because we can freeze all requirements beforehand and estimate the time and project cost easily
What are the other reasons? Let me in comments.
Do you know Waterfall Model is no Longer used commonly?
What is the problem?
Why did it become unpopular?
We will check them out in detail in my next thread on Wednesday.
Follow @vikasrajputin to not miss my next Thread!
What is the problem?
Why did it become unpopular?
We will check them out in detail in my next thread on Wednesday.
Follow @vikasrajputin to not miss my next Thread!
Namaste, I'm Vikas!
Every Mon, Wed & Fri, I write a thread about Java, Javascript and Fullstack Development.
To read all my future threads follow me @vikasrajputin
Have a great day ahead!
Every Mon, Wed & Fri, I write a thread about Java, Javascript and Fullstack Development.
To read all my future threads follow me @vikasrajputin
Have a great day ahead!
Part 2 is out now,
When not use Waterfall Model:
When not use Waterfall Model:
جاري تحميل الاقتراحات...