Process Models -Spiral Model
software Engineering
___
Notes
●created by Barry Boehm in the middle of the 1980s
●The main characteristic that sets the Spiral Model apart is that it approaches the
development process from a risk-driven perspective instead of one that is
predominantly document- or code-driven.
●The Spiral Model adds risk assessment as a new component and was created to
combine the best elements of the Waterfall and Prototyping Models.
●The method that is employed while the system is being developed is referred to
as the "spiral" process.
●As with the prototyping model, a first version of the system is created and then
repeatedly adjusted according to feedback from user assessments.
●In contrast to the Prototyping Model, the Waterfall Model's phases are used to
meticulously plan the development of every system version.
●As one circles the spiral (starting in the center and moving outward), even more
sophisticated iterations of the system are constructed.
●In order to evaluate each iteration of the system and decide whether or not to
proceed with development, risk assessment is a phase in the development
process.
●The project may be put on hold if the client determines that any hazards found
to be excessive.
Six Areas of Task
Customer communication: to create a productive line of contact between the client
and the developer.
Planning: defining deadlines, resources, and other project-related details.
Risk analysis: used to evaluate hazards related to management and technology.
Engineering: to construct one or more application representations. Building and
releasing entails building, testing, installing, and offering user assistance (such as
instruction and documentation).
Customer evaluation: to gather input from customers on the assessment of the
software representation developed in the engineering phase and put into use in the
installation phase.
Advantages
●The deliverable is generated early in the software development life cycle;
●It is ideally suited for complicated and large projects; and
●It provides good support for risk analysis.
●Prototyping is used as a risk reduction strategy, and it can significantly lower
hazards in the SDLC process.
Disadvantages
●In addition to being expensive, risk analysis is also exceedingly challenging.
●It is not appropriate for little tasks.
●Requires extensive risk assessment.
Application area:
Business developers are not as familiar with Boehm's model as ADE (Aerospace,
Defense, and Engineering) specialists are. Due to their risky character, ADE initiatives
benefit greatly from it.
