Spiral Model

Basic Features
• combines the features of the prototyping model(evolutionary type)
and the waterfall model.
• iterative in the sense that it repeatedly passes through each phase
in iterations(called spirals in this model).
• allows incremental releases of the product or incremental
refinement through each iteration around the spiral.
Phases
1.Communication
– effective communication between the customer and the
software team.
– A requirement list is created about what the customer actually
wants.
2.Planning
– Identify problem, decide objectives, decide life cycle phases of
the project, modularize the work, estimate time and resources
requirements, project cost and budgeting, scheduling works.
– More focus during this phase is given to risk management
where risk is identified,analysed,planned and finally monitored.
Contd..
• Risk identification
– List of potential risk that may be related to project, product or
business.
• Risk analysis
– Risks are listed according to priorities.
• Risk planning
– Risk avoidance and contingency plans.
• Risk monitoring
– Risk assessment
3.Modeling Phase
• Feasibility analysis is performed during this phase concluding
whether the software that is going to be developed is feasible or
not.
• Data and process are represented well through different modelling
diagrams making more clear about how actually the software is
going to be developed .
• The task of each subsystem of the software projects are defined
through the designs.
• Overall a sample or a blueprint of the software project is designed
in this phase.
4.Construction
• Designs made in previous phase ,now implemented through
lines of codes using high level programming languages.
• Every organizations have their own framework in which they
can code using Integrated Development environment(IDE).
• After coding is completed ,necessary testing are performed in
this phase.
• Testing include both verifications and validations.
5.Deployment
– finally the software is delivered to the customer making
necessary documentations.
– software is maintained and support is provided in case of any
flaws that the software faces.
– feedback is collected from the customers in order to evaluate
the software that is being delivered.
– Finally a list of changes are prepared on the basis of
customer’s feedback so that this is discussed again in
communication phase with the software team.
Applications
• When there is a budget constraint and risk evaluation is
important.
• For medium to high-risk projects.
• Customer is not sure of their requirements which needs
evaluation to get clarity.
• New product line which should be released in phases to get
enough customer feedback.
• Significant changes are expected in the product during the
development cycle.
Advantages
• Changing requirements can be accommodated.
• Allows extensive use of prototypes.
• Requirements can be captured more accurately.
• Users see the system early.
• Development can be divided into smaller parts and the risky parts
can be developed earlier which helps in better risk management.
Disadvantages
• Management is more complex.
• End of the project may not be known early.
• Not suitable for small or low risk projects and could be
expensive for small projects.
• Spiral may go on indefinitely.
• Large number of intermediate stages requires excessive
documentation.