SPIRAL MODEL

Advantages
1. This model improves avoidance of risk 2. This model is very useful to choose a methodology for a software iteration 3. This model can associate other methodologies like Waterfall, Prototyping, and Incremental methodologies. Suppose a project having a low risk of not meeting the user requirement and on other side having high risk of missing budget would follow waterfall approach 4. In this model more functionality can be added in later versions.

Disadvantages
1. This model limiting reusability 2. This model is quite complex 3. Spiral model is very customized for every project 4. To use this model an experienced and skilled team required 5. There is no proper control to move from one cycle to another cycle

Spiral Model Merits:-- This model is an example of evolutionary model and combines the features
of the prototyping model and the waterfall model . Estimates (i.e. Budget, schedule, etc.) become more realistic as work progresses, because important issues are discovered earlier. Software engineers can get their hands in and start working on a project earlier. Prototyping is used as a risk reduction mechanism After final iteration, all risks are resolved and the requirements are ready for development. Demerits:-- The spiral model is intended for large, expensive and complicated projects. Highly customized limiting re-usability. Risk of not meeting budget or schedule. Requires considerable expertise in risk evaluation and reduction. Complex, relatively difficult to follow strictly Advantages: Risk reduction mechanisms are in place Supports iteration and reflects real-world practices Systematic approach Disadvantages: Requires expertise in risk evaluation and reduction Complex, relatively difficult to follow strictly Applicable only to large systems Idris Lawal Merits: 1) dynamic requirement changes present. 2) integration testing is present

demerits:
1) time taken to deliver the product is more 2) only intended to large and complicated project

Merits:
1) dynamic requirement changes present. 2) integration testing is present 3)changes made in one module will not have any impact on another demerits1) time taken to deliver the product is more 2) only intended to large and complicated project

What is Spiral model- advantages, disadvantages and when to use it?The spiral model is similar to the incremental model, with more emphasis placed on risk analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A software project repeatedly passes through these phases in iterations(called Spirals in this model). The baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each subsequent spirals builds on the baseline spiral. Requirements are gathered during the planning phase. In the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is produced at the end of the risk analysis phase. Software is produced in the engineering phase, along with testing at the end of the phase. The evaluation phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral. Diagram of Spiral model:

Advantages of Spiral model:

High amount of risk analysis hence, avoidance of Risk is enhanced. Good for large and mission-critical projects. Strong approval and documentation control. Additional Functionality can be added at a later date. Software is produced early in the software life cycle.

Disadvantages of Spiral model:

Can be a costly model to use. Risk analysis requires highly specific expertise.

Projects success is highly dependent on the risk analysis phase. Doesnt work well for smaller projects. When to use Spiral model: When costs and risk evaluation is important For medium to high-risk projects Long-term project commitment unwise because of potential changes to economic priorities Users are unsure of their needs Requirements are complex New product line Significant changes are expected (research and exploration)