Welcome to our new chapter for Spiral Model. It is one of the best-practised software development models in the industry. The spiral model developed by taking the waterfall model and iterative development into consideration and keeping focused on risk-based development. This model is perfect for a bigger project which require continues improvement and control over quality. In this model we deliver the small feature of the bigger project on each iteration, this iteration repeated until the entire project is not build up.
Phases in Spiral Software Development Model
Planning Phase: In this phase, the team is usually busy in getting the requirement and planning the things. The requirement for a system, subsystem and a unit is gathered in this phase only. We need to perform the feasibility study, walkthrough and review of required documents. An output result of this phase is finalized features which team will work and release at the end of this spiral.
Risk Analysis: Process helps us by giving the chance to identify the risk within the system in this phase. If we encounter any risk, we need to identify the alternative solution in the same phase and before going to the next phase. Mitigation plan needs to create in the same phase for identified risks. We can move to a new phase only after creating the document for identified risks along with mitigation planned for respective risk.
Engineering Phase: It is the model where development and testing are performed in the same phase. It makes it somehow special development model. Some organization shows the practice of developing POC ( Plan of Concept ) before actually starting working on product development.
As I said development and testing need to perform in the same phase, so fully working developed feature, testing artefacts like test cases, test results, and summary report needs to be completed before moving in next phase.
Evaluation Phase: As per the name of this phase, here feature developed in existing spiral needs to be evaluated by the client. Feedback received after analyzing the feature implemented in the live environment. Also needs to document all the ups and downs faced by the team during the spiral development. Once clients give the green signal for the feature deployment, the team starts working on the next spiral with some new feature.