7/27/2019 Software Design - Differences between Spiral Model and
Waterfall Model
1/2
Question B
1. Describe the difference between Spiral model and Waterfall
model. Describe the ways in
which they are related.
Spiral model Waterfall model
Spiral model is best suited for projectsassociated with risks.
In Waterfall modeleach step is distinct. After completionof step
one can move to next step and onceyou are through from one step you
can tmove back. Hence waterfall model isuseful only those projects
whererequirements are well understood and nochange in requirements
is needed.
In spiral model we don t define every thing indetail at very
beginning. we start with basicfunctionality and work them out. we
take client's feedback.If developed functionalities is as per
clientsrequirement then we move on to next step.Spiral model is
useful when requirementsare changing.
The waterfall is a linear & sequential design process, that
goes to the next step one after another after complete the previous
step. It seenas flowing downwards like waterfall. Throughthe phases
of conception, initiation, analysis,design, construction,
testing,
production/implementation & maintenance.
Once a phase of development is completed, thedevelopment
proceeds to the next phase andthere is no turning back. It allows
for departmentalization and managerial control. Aschedule can with
deadlines for each stage of development and a product can proceed
throughthe development process
The disadvantages is not allow much reflectionor revision. It is
difficult to go back and changesomething that not well thought out
in conceptstage. Its
Difficult to estimate time and cost for each phase of the
development process. Noflexibility to consideration anychange in
SRS will result to start work for firststep and goes step by step
again.
7/27/2019 Software Design - Differences between Spiral Model and
Waterfall Model
2/2
2. Explain how the Spiral model mitigates the inherent
disadvantages of the waterfall model
The spiral lifecycle model allows for elements of the product to
be added in when
they become available or known. This assures that there is no
conflict with
previous requirements and design. This method is consistent with
approaches that
have multiple software builds and releases and allows for making
an orderly
transition to a maintenance activity. Another positive aspect is
that the spiral
model forces early user involvement in the system development
effort. For
projects with heavy user interfacing, such as user application
programs or
instrument interface applications, such involvement is
helpful
3. You are developing an online video game application for
children under 12 years old.
List the potential stakeholders that will involve in the
development
Customer Client Users
Developer Data analyst
