Spiral Model (Part 2) ~ Tumblia Test Solution

How to handle requirement changes in spiral model

Customer will do requirement changes in two ways

Major Changes
Minor Changes

Major Changes

Explanation

In my previous post I have already explain how the model works here I will explain only how we can handle major changes (70-80% changes) .

If customer gives a new module and also he want some major changes in previous released modules then company will handle the major changes first as a part of one new cycle.

As per above picture after the release of module 'C' customer wants major change in module 'B'

so here we have taken major changes of module 'B' as a new cycle .

Here is the explanation for how we can handle major changes.

Customer will give requirement for new module 'D' and major changes for module 'B'.
Business Analyst will go to customer place and collect the requirement for major changes in module 'B'.
Architect will do the design for major changes in module 'B' (i.e. High Level Design and Low Level Design).
Developer will write the code for major changes in module 'B' and give software to Test Engineer.
Test Engineer will first test the major changes in module 'B'.
Then Test engineer will test the remaining portion of module 'B'.
Test Engineer will then test the integration between module 'BA' and 'BC'.
Test Engineer will then test old modules 'A' and 'C'.

This is how we can handle the major changes.

Minor Changes

Explanation

Here I will explain how we can handle minor changes.

If customer give new module 'D' and also he wants some minor changes in module 'B' and he also wants 2 defects should be fixed in module 'C'.

For this kind of requirement we will take all the requirement as one cycle.

so here is the explanation how we can handle minor chances, new module and defect in one cycle.

Customer will give requirement for new module 'D' and minor changes in module 'B' and he also wants 2 defects in module 'C' should be fixed .
Business Analyst will go to customer place and do the requirement collection for new module 'D' and minor change in module 'B' and he will also bring the list of defects.
Architect will do the design for new module 'D' and minor changes in module 'B'.
Developer will do the development for new module 'D' and minor changes in module 'B' and he will also fix 2 defect and give software to Test Engineer.
Test Engineer will first test new module 'D'.
Then Test Engineer will test the minor changes in module 'B'.
Test Engineer will then test integration between module 'DC, 'DB' and 'DA'.
Test Engineer will then test 2 minor defect.
In the end Test Engineer will test the old modules 'A', 'B' and 'C'.

This is how we can handle minor changes.

Advantages of Spiral Model

Requirement changes can be done after every cycle.
Customer will get an opportunity to see the software after every cycle.
Testing is done in every cycle before going to the next cycle.
Spiral model is a controlled model .(First we take requirement for 1 module then develop the module and test the module if the quality is good then only we will take requirement for next upcoming module.)
Investment is done in proper way.