Starting the Cycle

• The initial task is to put together a preliminary design and prototype for the new system. This requires programmers to define the needs and requirements of the project, interviewing people both inside and outside the company to represent those who will use the new application, and determine specifications that will aid in the new software's development.
  
  

The Prototypes

• The first prototype is a stripped-down version of the finished product. The second prototype is much more extensive. Work begins with assessing what worked and what didn't work with the first prototype. Software designers then update the requirements for the second prototype and follow that by planning and designing the new prototype. Finally, the second prototype is constructed and tested.
  
  

Pulling the Plug

• Some clients will choose to pull the plug at this state of the application's development. There are a variety of reasons for this decision. It could be that the project is proving too costly for the intended use of the product. It also could be that there is too much risk involved in continuing to work on a solution to the application. At this point, it is solely up to the client to determine if the project is worth continuing the spiral life cycle.
  
  

Moving Forward

• If the client chooses to move forward, the spiral continues to spin around prototypes. The current prototype is evaluated and modified to fit the client's needs. If necessary, more prototypes can be constructed until the client is satisfied with the finished product. While developing these prototypes, designers will adhere to the guidelines set forth in the second prototype.
  
  

Approval

• Once the client approves the final prototype, the application is constructed, evaluated, and tested. After the application's release, programmers can provide modifications and maintenance to the application.
  
  

Why This Works

• Software programmers like the spiral life cycle because it provides a great amount of risk analysis, which is essential in putting together a new program. The life cycle breaks down large and critical projects with relative ease, and the application is developed early in the spiral life cycle, meaning that it goes through several quality control checks before release.
  
  

Why This Might Not Work

• The financial costs involved in using the spiral life cycle can be high. The company developing the software may not get its money's worth. The risk analysis phase can be especially troublesome, as companies need programmers with specific expertise to carry this out. Plus, it's difficult to apply the model to smaller, less costly projects.