ASSIGNMENT

SPIRAL MODEL

MEMBERS

ARUN JOSE
ASHWATHI K S
GOPIKA
DEVAKUMAR
PRIYA
SAMEENA
SHIVASHANKAR
SRUTHI NAIR
VINEETH
INTRODUCTION

SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC):

• Software development life cycle is a process used by the software industry
to design, develop and test high quality software’s.
• It aims to develop or produce a high-quality software that meets or exceeds
customer expectations.
• There are various SDLC models, each follows a series of steps unique to
its type to ensure success in the process of software development.

SPIRAL MODEL:
• First mentioned by Barry Boehm.
• A combination of Waterfall Model and Iterative Model.
• Each phase begins with a design goal and ends with the client reviewing
he progress.
• A space for Customer Feedback.
• In this model, at the end of first iteration, the customer evaluates the
software and provides the feedback. Based on the feedback, software
development process entries into the next iteration stage.
• Is used for the development of large and expensive projects like Scientific
Projects.
FIGURE
SDLC- Spiral model
The spiral model of SDLC gives incremental development for a system. It has
four phases,

1. Planning phase
2. Risk analysis phase
3. Engineering phase
4. Evaluation phase.
In spiral model of software development life cycle, each iteration is called a spiral
and the whole development process of a software project passes through these
cycles. The number of loops vary from project to project.

The radius of the spiral represents the value incurred for the project till that point
and therefore the angular dimension of the spiral represents the progress made
thus far for the software project in the current phase.

DETERMINE OBJECTIVES

The initial phase of spiral model starts with gathering of requirements from the
customers and the businesses. The business requirement specifications (BRS) and
system requirement specification (SRS) are identified, this is done by the
continuous communication between the customer and the system analyst. The
alternative solutions possible for the project in the phase are proposed in this
quadrant. The product is positioned in the identified market at the end of the
spiral.

IDENTIFY AND RESOLVE RISKS

In the second quadrant evaluation of all the possible solutions happens, this is to
select the possible solution. After the first iteration customer evaluates the
software and provides feedback and based on that the development process enters
the next iteration. Identifying, estimating, and observing the technical feasibility.
To determine the strategies to be used to overcome the risks. A prototype is
produced at the end of the stage.

DEVELOP, VERIFY NEXT LEVEL PRODUCT

In this phase the planned product is developed along with further testing. The
features identified are implemented, a proof of concept (POC) is developed in
this phase to get the user’s feedback. In the successive spirals higher clarity on
requirements and style a working model of the software called build is developed.
The build is produced with a version number and they are sent to customers for
feedback.

REVIEW AND PLAN FOR NEXT PHASE

In this phase before the project continues to the next spiral the output of the
project is evaluated till date. The customers evaluate the thus far developed
version of the software. Progressively more complete version of the software gets
built with each iteration round the spiral. In the end planning for subsequent phase
is started,
APPLICATIONS

• Software industries make use of different application development models

available. Spiral model is a very important software development lifecycle
model which is used for large and expensive complicated projects.
• This model helps for risk handling based on all the internal and external
factors and all other requirements of software development.
• Spiral modelling approach is extensively used in software industry as it is
in sync with the natural development processes of any product which
include learning with maturity and minimum risk for the customer as well
as the development firms.
• It is the best option for projects in which frequent releases are necessary,
in which changes may be required at any time with unclear or complex
requirements that are long term and less feasible due to altered economic
priorities which are having medium to high risks and high costs, those that
would benefit from the creation of a prototype also.
• For complex projects, spiral model helps in its evaluation to get clarity. It
helps in releasing new product lines in phases to get enough customer
feedback and to help with risk evaluation and cost analysis for expensive
and large projects since there will be a budget constraint at most times.
• Spiral model enables long term project commitment as there is a case of
potential changes in economic priorities as there will be changes in
requirements with time. This is the most sought solution for medium to
high risk project development and also when the customer is not sure of
their requirements which are a usual case. Significant changes are expected
in the product during its developmental cycle and spiral model helps in
meeting all those expectations.
EXAMPLE

• An example of the application of spiral model is the transition of Microsoft

operating system windows 3.1 version to the operating system windows
2010. The evolution of windows 3.1 is regarded as the first iteration in the
spiral approach. This was made possible after listening to their customer
feedbacks about the operating system. With the required functional
enhancement and graphical flexibility incorporated as developments
windows’95 was released and similarly other versions as well with time.
All these are the result of applying spiral model iteration.

• The United States army adopted the spiral model for the development and
upgrading of its future combat systems (FCS) modernization program. It
was officially launched in 2003. FCS was foreseen to equip troops with
manned and unmanned vehicles connected through an extraordinary fast
and flexible real-time battle field network. The project was divided to four
2-year development spirals. The first Spiral was scheduled to begin in 2008
and deliver prototypes for use and evaluation and the second was scheduled
to commence in 2010. The production deployment was planned for 2015.
Now the spiral model has entered the gaming industry as well. The large
projects with budget greater than $3M and continuously shifting goals of
gaming systems development and resolutions achieved through
evolutionary prototyping has created a demand for the process
ADVANTAGES

HIGH RISK CONTROL

When we are handling high risky projects it is very important that we have a good
risk management. When the project is in second quadrant of the cycle best
possible solution is selected and then the risk which is associated with it is
identified and resolved using the best possible strategy.
GOOD FOR LARGE MISSIONS
Spiral model is used in large missions rather than small ones. Because it is very
useful when it comes to dealing with more complex projects.
CUSTOMER SATISFACTION
Since the software testing's is very transparent the customer can view and review
each stages of testing so suggestions can be made for its modification.
CAN BE SEPERATED
Here the projects can be divided into various parts and tested according to the
management needs.
DOCUMENTATION CONTROL
The documentation control is very strong here.
CUSTOMIZATION
We can produce a highly customized product as per the customers needs and
requirements.
FLEXIBILITY IN REQUIREMENTS
If at the later stage any changes is to be made in the project that can be
incorporated accurately by using this model.
PRODUCED IN EARLY STAGE
Software is produced early in the software life cycle.
DISADVANTAGES

EXPENSIVE
Spiral model can be very costly especially if spirals continue indefinitely that it
can’t be suitable for small projects.

COMPLEX
The spiral model is much more complex than any other SDLC Models. The spiral
model enables gradual release and refinement of a product through each phase
of the spiral as well as the ability to build prototypes at each phase.

TOO MUCH DEPENDABLE ON RISK ANALYSIS

Project’s success is greatly dependent on the risk analysis phase. Without a very
highly experienced expertise, it is going to be a failure to develop a project using
this model. Thus, to review and analyse the project from time to time, special
skills are required.
DIFFICULTY IN TIME MANAGEMENT
Since the number of phases is unknown at the very beginning of the
project, time estimation is very difficult.

RULES AND PROTOCOLS

Rules and protocols must be followed strictly without fail throughout the
development, for the smooth and successful operation of the project.
DOCUMENTATION
Documentation can be heavy, due to the number intermediate stages via,
1. Planning
2. Risk Analysis
3. Engineering
4. Evaluation
NOT IDEAL FOR SMALLER OR LOW RISK PROJECT
It can be a good be a good option if we face a medium, or high-risk project and
costs are highly important, but not suitable for smaller or low risk projects.
RISK HANDLING IN SPIRAL MODEL

A risk is any adverse situation which may affect the successful completion of a
software project. The important feature of the spiral model is handling these
unknown risks after the project has started. Such risk resolutions are done by
developing a prototype. The spiral model supports coping up with risks by
providing the scope to make a prototype at every phase of the software
development.

Prototyping Model also support risk handling, but the risks must be identified
completely before the beginning of the event work of the project. But in real
world project risk may occur after the event work starts, therein case, we cannot
use Prototyping Model. In each phase of the Spiral Model, the features of the
merchandise dated and analyzed and therefore the risks at that time of your time
are identified and are resolved through prototyping. Thus, this model is far more
flexible compared to other SDLC models.

SPIRAL MODEL IS CALLED META MODEL

The Spiral model is named as a Meta Model because it subsumes all the
opposite SDLC models. For example, one loop spiral actually represents the
Iterative Waterfall Model. The spiral model incorporates the stepwise approach
of Classical Waterfall Model. The spiral model uses the approach of
Prototyping Model by building a prototype at the beginning of every phase as a
risk handling technique. Also, the spiral model are often considered as
supporting the evolutionary model – the iterations along the spiral are often
considered as evolutionary levels through which the entire system is made .
REVIEW OF THE MODEL

Different methodologies of development are involved in the development of

computer software and system information. Software development
methodologies help to plan, construct and control the development procedures of
an Information System. The spiral model, which was actually proposed by Boehm
is one of the important evolutionary process models and it involves prototyping.
The spiral model has several organised and controlled characteristics. One
prominent feature is that it has a risk driven nature. It actually has a realistic
approach for the development of large scale projects. As the evolution of the
software progresses further, from the initial stage, the customers and the
developers get to know better of the risks at each level of the spiral process.
Obviously, it can help in the development of increasingly more complete versions
of software projects. And it is true that the spiral model can be referred to as a
risk driven software development process model. And with the incremental
iterative approach, the spiral model facilitates regular risk assessment. This model
is intended to prevent the negative consequences that normally arise.
In the first phase of this model, the objectives and alternatives are determined and
the framework conditions are being described. Followed by this, the next stage is
about identification of the risks and resolving them. Developing and testing the
intermediate status which is the third phase is followed by the fourth phase which
is all about planning the next cycle.
The spiral model is actually a generic process model. Although the different
stages of the model set out the basic objectives of a cycle, it may not be reflected
in each rotation. And adding to that, what we can understand is that the order may
not be determined accurately under this model. Hence, the spiral model is often
combined with other process models
But in fact, this is a pretty flexible model. And because there is always the
possibility to go back to the previous decision at any point of time, definitely it
needs to be a flexible one indeed. And as mentioned earlier, repeatedly iterating
set of elemental development processes and elimination of the risk are some of
the prominent characteristics which make this a unique model. This model is also
called the meta model because the spiral model subsumes the other software
development life cycle models.
But still, the spiral model is not so well known when compared with the other
software development life cycle models. The spiral model is little bit costly to
use. Furthermore, it is not suitable for smaller projects. These could be a few
reasons for this model being not so popular when compared with the other
software development life cycle models. Howsoever, one cannot deny the fact
that the spiral model remains to be one of the most important software
development life cycle models which has the potential to remain relevant.