This post describes the Software Development Life Cycle with the help of its definition and stages on which the Software Development Life Cycle is based. It also describes the main SDLC Models Comparison in the tabular form with the help of its pros and cons and the types of projects can be made using that model.
What is SDLC?
The Software Development Life Cycle (SDLC) is a method used by the software industry to design, produce, and validate software quality. Its mission is to build high-quality software that meets or exceeds consumer standards in terms of timeliness and cost estimates.
Stages of SDLC Models
A typical Software development life cycle consists of the following stages which are as follows:
- First Stage : Planning an requirement analysis
- Second Stage : Defining requirement
- Third Stage : Designing the product architecture
- Fourth Stage : Building or developing the product
- Fifth Stage :Testing the product
- Sixth Stage : Marketing of the product and marketing development
Comparison of SDLC Models
mS.NO | MODELS | STRENGTH | WEAKNESS | TYPES OF PROJECT |
1 | Waterfall Model | Simple. Easy to execute. Intuitive & logical. | Simple approach. Do not allow changes. Cycle time is too long. User feedback is not allowed. | For well-understood problem. Short duration project. Automation of adjusting manual system. |
2 | Prototyping Model | Helps in requirement elicitation. Reduce the risk. Lead to a better system. | Possibly higher cost. Do not allow labour charges. | System With massive users. Uncertainty in requirement. |
3 | Iterative Enhancement Model | Regular/Quick delivery. Reduces risk. accumulate Changes. prioritizes requirement. | Each Iteration Can Have Planning Over Head. Cost may increase as work done in one iteration may have to be undone later. System design & structure may suffer as frequent changes are made. | For a business where time is of the essence. Where the risk of the long project can be taken. |
4. | Spiral Model | Control project risk. Very flexible. Less document needed. | No strict standard for software development. No particular began and ending of the particular phase | Project build on untested assumptions |
Discover more from easytechnotes
Subscribe to get the latest posts sent to your email.