Difference between spiral model and proto type in sdlc?

Answer Posted / idrees ashraf

Spiral Model: Spiral Model consists of 4 phases: 1)Planning
2)Risk Analysis 3)Engineering 4)Evaluation.
Prototyping is part of Spiral model and it is done in the
last stage of risk analysis. The radius of the spirals show
cost and angular brackets show progress.

Whereas in

Prototype Model: when the client is not clear with
requirment one dummy project is created presented to the
clint according to the clinet suggestions then again all
steps are applied to make it again.

Is This Answer Correct ?    10 Yes 1 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

hi friends .......... from srs to signoff what r the tests the testing team will conduct either sequentially or parallel pls advice thanks in advance

1450


what is test strategy,test plan and test policy?Does anyone have dummy documents or any links that gives more idea about these?I am a beginner...interested in learning more abt testing.plz help and encourage me........!

1408


tell wat u did in ur banking project?

1846


What are parametere require for Performance testing?

1915


Should testing be done only after the build and execution phases are complete?

1073






What is the full form of cmmi?

665


What are the tasks of test closure activities in software testing?

616


Hi, this is not a tech question, i have 4 yrs of experience in Mainframe systems, presently as a mainframe tester in pune, i just want to step towards south locatios(preferable hyd), suggest me the best way to get calls from hyd.

1640


How does a coverage tool work?

688


functional testing test cases for transfer funds ?

1188


Can any one please tell me which is the best institute in Bangalore to learn QA (crash course)? Thanks

1491


Can you explain boundary value analysis?

656


What do you do (with the project tasks) when the schedule fails?

2570


What is the main use of preparing a traceability matrix?

699


Explain some techniques for developing software components with respect to testability.

3052