software life cycle

software life cycle

1. V.shape

   • The Incremental life cycle model builds an iterative approach into the Waterfall model. Development projects are divided into several smaller, more manageable iterations
   • Advantages:Unlike the Waterfall and V-Shaped models, the Incremental model generates a working prototype early in the development process.
     • Disadvantages Like the Waterfall model, the Incremental model exhibits some rigidity in that phases cannot be overlapped.

2. Waterfall

   • The Waterfall life cycle model, also known as the classic or linear-sequential life cycle model, is one of the simplest to understand and use
     • Advantages: As a formalized approach to software development, the Waterfall model is simple and easy to use.
       • Disadvantages: Although the Waterfall model provides a good introduction to software life cycle models, its usefulness is limited.

3. Spiral Life

   • The Spiral life cycle model is similar to the Incremental model but incorporates risk analysis. It is divided into four phases: planning, risk analysis, engineering, and evaluation.
   • Advantages: The focus on risk avoidance makes the Spiral model ideal for large-scale and missioncritical products
     • Disadvantages: The Spiral model can cost considerably more to implement than other life cycle models.

4. Incremental

   • The Waterfall life cycle model, also known as the classic or linear-sequential life cycle model, is one of the simplest to understand and use.
     • Advantages: The Waterfall model is appropriate for small development projects in which the requirements are well understood.
     • Disadvantages : Although the Waterfall model provides a good introduction to software life cycle models, its usefulness is limited.

5. Software Model

   • Requirements-gathering
     • During the requirements-gathering phase, the needs of the company are outlined. Managers and users (and in some cases, clients) make their “wish-lists” about what they would like the software to do
   • Design
     • In the design phase, the results of the requirements-gathering phase are translated into a software design plan.
   • Implementation
     • In the implementation phase, the results of the design phase are translated into program code. Software that does not meet the needs of the company is wasteful.
   • 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