Some SDLC Models are listed below:
Thank you for reading this post, don't forget to subscribe!- Waterfall Model
- V-Shaped Model
- Evolutionary Prototyping Model
- Spiral Method (SDM)
- Iterative and Incremental Method• Agile development
1.) Waterfall SDLC:
The Waterfall Model is a sequential and linear approach to software development in which the process flows downwards step-by-step through clearly defined phases.
- Each phase must be completed before the next begins, and there is no overlap between the phases.
Phases of the Waterfall Model:
1.) Feasibility Study:
- This phase involves assessing whether the proposed system is technically, economically, and operationally viable.
- Analysts examine the project’s cost, benefits, risks, and resource requirements. If the project is deemed feasible, it proceeds to the next phase.
2.) Requirements Analysis:
- This phase involves gathering and analyzing all functional and non-functional requirements of the system.
- Analysts and stakeholders define what the system must do. These requirements are documented in detail and reviewed for approval before moving to the next phase.
3.) System Design:
- Based on the requirements, a system design is created to describe how the system will fulfill the requirements.
- This includes architectural design, data models, interface designs, and system components. The design serves as a blueprint for developers.
4.) Implementation (or Coding):
- The actual code for the system is written during this phase based on the approved design.
- Developers create modules, classes, and logic. Unit testing is often done alongside development to ensure correctness at the code level.
5.) Integration and Testing:
- All software components are integrated and tested as a complete system.
- The focus is on system functionality, performance, and identifying defects. This phase ensures the system meets the specified requirements.
6.) Deployment:
- The completed and tested system is deployed in the user’s environment.
- Users begin to operate the system, and it becomes available for daily use. It may be released in stages or all at once.
7.) Maintenance:
- After deployment, the system enters a maintenance phase where issues are fixed and enhancements are made.
- Bug fixes, updates, and minor improvements are applied. This phase can continue for the lifespan of the software.
Advantages of Waterfall Model:
- Easy to Understand: The Classical Waterfall Model is very simple and easy to understand.
- Individual Processing: Phases in the Classical Waterfall model are processed one at a time.
- Properly Defined: In the classical waterfall model, each stage in the model is clearly defined.
- Clear Milestones: The classical Waterfall model has very clear and well understood milestones.
- Properly Documented: Processes, actions, and results are very well documented.
- Working: Classical Waterfall Model works well for smaller projects and projects where requirements are well understood.
Disadvantages of Waterfall Model:
- No Feedback Path
- Difficult to accommodate Change Requests
- No Overlapping of Phases
- Limited Flexibility
- Limited Stakeholder Involvement
- Late Defect Detection
- Lengthy Development Cycle