Spiral model in Manual Testing

 Spiral Model  

• In this model, the customer can ask for the changes any number of times.
• Here the customer gives the requirements in parts.

Spiral Model

• In the first stage of the spiral model, the customer gives the requirement "A".
• Bussines analyst the requirement "A".
• The design of the "A" model is done by the architect.
• The coding and testing of the "A"  Module are done by the developers. 
• Once the "A" module is ready the module is reviewed by the customer.
• If he is satisfied with the module he gives some new requirements.
• He is not satisfied with the module he asked for the changes to be done.
• The customer gives a new "B" requirement and changes in "A" requirement.
• Design of "B" takes place and redesign of "A" module takes place.
• Coding of "B" module and remodification in the source code of "A" module is done.
• Testing of "B" Module and retesting of "A"  module is done.
• The test the integration between "A" and "B" modules and send it to the customer for review 
• The customer reviews the modules and if not satisfied asks for change and gives some other requirements.
• The process goes on until all the modules are develop.

Advantages of the spiral model

• Requirement changes are allowed in this model.
• If there are any major changes in the model, separate integration is carried out to do those major changes.
• If there are any minor changes in the module those changes are done along with developing a new model

Disadvantages 

• Since it is a traditional model coding and testing done by the developer 
• It is time-consuming.

Application of  spiral model 

• When the customer gives requirements in stages the developer the product in stages.
• When the customer has no idea how the end product looks like.

• What Is SDLC (Software Development Life Cycle ) In Manual Testing?
• Advantages , Disadvantages And Application Of Waterfall Model In Manual Testing

• Tweet
• Share
• Share
• Share
• Share