what is Spiral Model?

By -
This model follows a process in which the requirements all the phase activity is performed iteratively till all the requirements are met. This enables the product to be demonstrated at any point of time during the development cycle. It allows the progress to be tracked and the customer approvals to be obtained at regular intervals, thereby reducing the risk of finding major defects at a later point of time.The spiral model is favored for large, expensive, and complicated projects.

This model allows for incremental releases of the product, or incremental refinement through each time around the spiral. This model also explicitly includes risk management within software development. Identifying major risks, both technical and managerial, and determining how to lessen the risk helps keep the software development process under control.



Advantages
  • Changing requirements can be accommodated.
  • Allows for extensive use of prototypes
  • Requirements can be captured more accurately.
  • Users see the system early.
  • Development can be divided in to smaller parts and more risky parts can be developed earlier which helps better risk management.

Disadvantages
  • Management is more complex.
  • End of project may not be known early.
  • Not suitable for small or low risk projects (expensive for small projects).
  • Process is complex
  • Spiral may go indefinitely.
  • Large number of intermediate stages require excessive documentation.

Comments

  1. Unknown29 May 2017 at 03:15

    Hello Fathima,
    The Article on what is Spiral Model with advantage and disadvantages is amazing , gives detailed information about it. Thanks for Sharing the information about the information about Spiral Model For More information check the detail on the Spiral Model testing here Software Testing Services

    ReplyDelete

Post a Comment

Popular posts from this blog

what is Modified Waterfall Model?

By -
Image
In response to the perceived problems with the "pure" waterfall model, many modified waterfall models have been introduced. These models may address some or all of the criticisms of the "pure"  waterfall model. In Water fall method , there is no VALIDATION OR VERIFICATION between the phases , so the customer will finally get unsatisfied product. This Modified Waterfall Model Involves VALIDATION or VERIFICATION between the phases , so any deviations can be corrected immediately , providing the customer satisfaction, so this is preferred.
Read more

what is Prototype Model?

By -
Image
The goal of prototyping based development is to counter the first two limitations of the waterfall model. This prototype is developed based on the currently known requirements. Development of the prototype obviously undergoes design, coding and testing. But each of these phases is not done very formally or thoroughly. By using this prototype, the client can get an "actual feel" of the system. Advantages It could serve as the first system. Prototyping is an attractive idea for complicated and large systems for which there is no manual  process or existing system to help determining the requirements. The customer doesn’t need to wait long as in the Linear Model. Feedback from customers are received periodically and the changes don’t come as a last minute surprise. Users are actively involved in the development It provides a better system to users, as users have natural tendency to change their mind in specifying requirements and this method of developing systems s
Read more

What is User Documentation Testing

By -
User Documentation  covers all the manuals, user guides, installation guides, setup guides, read me files,software release notes, and online help that are provided along with the software to help the end user to understand the software system. User Documentation Testing should have two objectives:- To check if what is  stated in the document is available in the software To check if what is there in the product is explained correctly in the document This testing is plays a vital role as the users will refer this document when they start using the software at their location.a badly written document can put off a user and bias them against the product even the product offers rich functionality. Defects found in the user documentation need to be tracked to closure like any regular software defect.Because these documents are the first interactions the users have with the product. A good User Documentation  aids in reducing customer support calls.The effort and money spend on this effort
Read more