Spiral Method
The spiral model is a risk-driven process model generator for software projects. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
The maroon dot is our current location within the spiral model.
Risk analysis
Risk Analysis includes identifying, estimating, and monitoring technical feasibility and management risks, such as schedule slippage and cost overrun. After testing the build, at the end of first iteration, the customer evaluates the software and provides feedback.
Deliverables
Preliminary Design document
Requirements
To view this document, visit our documents page.
Preliminary Design
To view this document, visit our documents page.
Release
E.A.S. will be released in late May 2015.
Implementation
This document will be available shortly.
Test
Unit tests will be available shortly.
Detailed Design
To view this document, visit our documents page.
Development
Development phase starts with the conceptual design in the baseline spiral and involves architectural design, logical design of modules, physical product design and final design in the subsequent spirals.
Deliverables
Detailed Design document
Evaluation
This phase allows the all parties to evaluate the output of the project to date before the project continues to the next spiral.
Deliverables
Acceptance Test document
Planning
This phase starts with gathering the business requirements in the baseline spiral. In the subsequent spirals as the product matures, identification of system requirements, subsystem requirements and unit requirements are all done in this phase.
This also includes understanding the system requirements by continuous communication between the customer and the system analyst. At the end of the spiral the product is deployed in the identified market.
Deliverables
Requirements Specification document, a finalized list of requirements.