Spiral Agile Testing

Many attempts were made to address the shortcomings of the waterfall approach, such as the spiral model of software development defined by Barry Boehm in 1988[6]. Intended for use in large,complex,and costly projects, and intended to address the issues of meeting customer requirements,this incremental development process relied heavily on the development and testing of a series of software prototypes of the final system. The typical steps involved in a spiral model–driven project are as follows:

  1. In discussion with the customer, the requirements for the system are defined and documented in as much detail as possible.
  2. An initial design is created based on the requirements.
  3. A sequence of increasingly complete prototypes are constructed from the design in order to
  4. _ test the strengths and weaknesses of the prototypes,and to highlight any risks;

    assist in refining the requirements by obtaining customer feedback;and

    _ assist in refining the planning and design.

  5. The risks identified by testing the prototypes are reviewed with the customer,who can make a decision whether to halt or continue the project.
  6. Steps 2 through 4 are repeated until the customer is satisfied that the refined prototype reflects the functionality of the desired system,and the final system is then developed on this basis.
  7. The completed system is thoroughly tested(including formal acceptance testing)and delivered to the customer.
  8. Graphical Overview of the Spiral Model.

    Graphical Overview of the Spiral Model

  9. Where appropriate,ongoing maintenance and test are performed to prevent potential failures and to maximize system availability. Figure provides a graphical overview of a typical interpretation of the spiral model.
  10. Although considered to be an improvement over the waterfall approach in terms of delivering systems that more closely match the customer’s requirements, and for delivering higher-quality software(achieved in large part by the spiral model, which encourages early and continued testing of the prototypes), issues existed regarding the difficulty of estimating effort,timescales, and cost of delivery;the nondeterministic nature of the cycle of prototype development and testing meant that it was difficult to bound the duration and effort involved in delivering the final product.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Agile Testing Topics