Software Development Life Cycle

Software Development Life Cycle

1. SOFTWARE DEVELOPMENT LIFE CYCLE MODEL

   • Requirements-gathering
     • During the requirements-gathering phase, the needs of the company are outlined.
   • Design
     • during the design phase, the designers attempt to turn the dreams of the managers and users into reality.
   • Implementation
     • In the implementation phase, the results of the design phase are translated into program code.
   • Testing
     • In the testing phase, the results of the implementation phase are run through a series of tests to verify that it functions and that it meets goals of the requirements phase.

2. WATERFALL LIFE CYCLE MODEL

   • Advantages of the Waterfall model
     • The Waterfall model is appropriate for small development projects in which the requirements are well understood.
   • Disadvantages of the Waterfall model
     • the Waterfall model is inappropriate for complex projects. It should not be used for developing object-oriented software, for long-term or ongoing projects, or for projects in which requirements are unknown or subject to change.

3. V-SHAPED LIFE CYCLE MODEL

   • Advantages of the V-Shaped model
     • the V-Shaped model is appropriate for small development projects in which requirements are well understood.
   • Disadvantages of the V-Shaped model
     • The rigidity of the V-Shaped model makes it inappropriate for most projects.

4. INCREMENTAL LIFE CYCLE MODEL

   • Advantages of the Incremental model
     • Generates a working prototype early in the development process.
   • Disadvantages of the Incremental model
     • The Incremental model is less risky than the Waterfall or V-Shaped models, but it may be inappropriate for large, long-term projects.

5. SPIRAL LIFE CYCLE MODEL

   • Advantages of the Spiral model
     • The customer is given many opportunities to evaluate the software and plenty of time to ease into adoption of the software.
   • Disadvantages of the Spiral model
     • The Spiral model is inappropriate for use in small and medium-scale projects that are not mission-ctical.ri