A Brief on Spiral Model Stages
Spiral Lifecycle Model was initiated by Boehm and is meant to be used while working with high risk projects. The features of this model is a emerges from the combination of waterfall model and prototype model. As the name suggests, all the activities is executed in the form of a spiral.
Spiral model is divided into four stages. The entire project goes through these stages now and then through each iteration known as a spiral.
Stage 1: Identification
In the baseline spiral, it all starts with gathering the requirements from the clients. Identifications of system, sub-system and unit requirements are performed in this stage as the project is executed.
A continuous communication is held between the system analyst and the client to gain a thorough understanding over the project. As soon as this spiral is accomplished, the project is deployed into the identified phase.
Stage 2: Design
Design stage begins with a design plan that has the basics of the design in the baseline spiral which includes architectural, logical and physical design of the product followed by final design in the resulting spirals.
Stage 3: Construct
Build stage includes the construction of the existing product at each spiral. In order to get the input from the client, POC is developed during the baseline spiral when the product is about to shape up its design.
At that point in the resulting spirals, a model of the product with version number – “Build” is created. This would be having a clear idea on requirements and design factors. These builds are further sent to client for input.
Stage 4: Assessment and Risk Analysis
This model undergoes through the process of identifying, monitoring technical feasibility, estimation and risk management. In the wake of the testing process of the build, after the completion of the first cycle, the client assesses the product and gives their input accordingly.
The playing point of the spiral lifecycle model is that it takes into consideration components of the product that are supposed to be included as per the requirement. This guarantees that there is no clash with the earlier completed designs.
This technique is reliable with methodologies that have various software builds. Considering to make a move in an organized way from the activity of maintenance to the transition of the project.
An alternate positive angle is that the spiral model compels involvement of the in the framework advancement exertion. Also, there is a risk of executing the spiral in a loop which is indefinite. Hence, a strict management is necessary to establish while dealing with it. For this purpose, disciplinary change is requested to follow in order to deploy the project successfully.