The waterfall model the process goes to the next step after
completion of the previous step as first requirement then
design then coding then implementation then maintenance but
here is no end user feedback taken to consideration any
change in SRS will result to start work fro first step and
goes step by step again.
But in case of Spiral model for each and every step there
is testing for that step carry on simultaneously after
finishing that step so that it will easy to recover any
error and fix it there. In this model we don?t have to
start work from beginning
water fall model is casecade in nature, because it goes
from one stage to the other and it cannot come back to the
prevoius stage. it follows the principal like
Analysis of the requirements
while in spiral model the concept of waterfall model is
combined with the iterations. it is also different in the
design from the waterfall model, after completing one stage
we can easily come back to the pravious stage.
In Waterfall model each step is distinct.After completion
of step one can move to next step and once you are through
from one step you cant move back.Hence waterfall model is
useful only those projects where requirements are well
understood and no chang in requirements is needed.
In spiral model we dont define every thing in detail at
very beginning.we start with basic functionality and work
them out.we take client's feedback.If developed
functionalities is as per clients requirement then we move
on to next step.Spiral model is useful when requirements
"Waterfall model is a document driven process.
While spiral model does not requires the document."
Is this mentioned anywhere? Because at the end of the last
prototyping in spiral modeling, water fall model process (
like detail design, coding, testing, acceptance) is applied,
and hence it should also be considered as document driven
process. Please comment.
Yes I agree that spiral modeling will help client to
understand the approximate characteristics of end product
and on the basis of which he can rework on the requirements
and hence it is suitable for big projects with high risk
When using the waterfall model, once each stage is
complete, you continue onto the next step, however you
cannot return to the previous stage.. The waterfall model
is only used when the requirements are well understodd and
there is no change in requirements.
In the case of using the spiral model, the completion
of one step can allow you to move to the next step or to go
back to the previous step.This means that the stages in the
spiral model can be repeated.
Waterfall Model also called as linear Sequential Model or
classical life cycle model is purely a pre
planned /strategic in nature. The requirements gathering is
the important phase and once the requirements have been
identified and agreed, the subsequent activities like
analysis, design, and implementation exactly resembles to
the requirements specification.If any flaw is uncovered in
the specification it leads to a serious/major error/defect
in the building product. No subsequent changes can be done
once you have skipped to one phase another, similar to
waterfall from a hill to ground, flow of water cant be
reversed. It is the best model if requirements gathering
have done perfectly and clearly stated in the initial
phase. Coming to spiral model, unlike waterfall model is
iterative in nature. This model suits for certain
situations where you need to build a novel system or
product which you dont have adequate requrirements
gathering. Spiral model starts in developing a new/novel
concept and upon subsequent refinements, the concept can be
turned into a product or a system. At each iteration, the
daemon activities like analysis, design, coding, testing
etc will be commenced.The errors/defects uncovered can be
fixed on next version or iteration. Also the spiral model
stresses more on the risk analysis which is not much
considered in waterfall model. The major drawback of
waterfall model is Customer should have patience and both
customer and s/w engineer should have a perfect picture of
what they are going to do, in real time situations this
will happen rarely as most of customers and engineers are
not fully experts in particular domain, and ofcourse
changing requirements continously makes you select spiral
model rather than the waterfall model.
there are 100 test cases. and u got a bug at 85th test
cases. u reported it to dev and dev fixed that bug. when u
r doing regression testing from whic test case u'll do
tetsing?? will start from 85 th test case are u'll execute
100 test cases??
if the interviewer asked what are thec hallenges did u face
in ur project how should we answer in project point of view
and as well as testing technical point of view plzzz send
the answer i faced this question lot of times but i am
unable to expose correctly plz send the answer how to say
Generally how do we do DataBase testing in Manual testing..
Do we prepare any testcases.. Generally do we concentrate
more means ex: Joins, Triggers.....Anybody can expalin it
in detail..Thanks in Advance....
i ask about job to friends but all people in software
testing gives suggestion.why they did not help for getting
call and at least gives one chance .we will show what we
are??but by giving only suggestion .is not write ans.see
many people from andrha pradesh giving refrences to there
people .why other people not follow to them.