Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

diff b/w waterfall model & spiral model?

Answer Posted / dariush

Waterfall Model:
-Series of stages carried out in sequence
-Products of each stage subject to QA inspections
-Only if the products are acceptable is the stage signed off
and the next allowed to start
-Each new stage starts from an agreed baseline established
at preceding stage
-In reality stages will overlap
-No stage is repeated unless a radical change of project scope
-Waterfall may provide a good starting point for structuring
the project
-Can be useful for inexperienced practitioners
Easy to build a simple plan around

Spiral Model:

-When requirements are not well known in advance spiral
model may provide an alternative
-An iterative approach to developing a system
--High level requirement specification is drawn up
--Tested by building a prototype solution
--Prototype is reviewed and requirements are clarified or
changed and amended requirements specification is issued
-The cycle is repeated until requirements are stable and
users approve the deign
-At the beginning of the spiral the focus is on requirements
issues
-At the end concentrates with technical issues
-Iterations can spiral out of control if not tightly managed
--Each iteration will lead to requests for change
--Difficult to call a halt to the process resulting in
projects running late and over budget
-Scope can be difficult to manage
-Final solution can be inadequately documented and poorly
structured
--Prototypes can be viewed as tool for capturing
requirements eliminating design stage
-Can lead to false user expectations
-Early prototypes raise expectations that final solution is
imminent

Is This Answer Correct ?    26 Yes 8 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Beyond the customary advantages of having a testing group, what are the benefits does a company receive from a well run, automated testing group?

3411


Functional and Integration test scenarios for actitime application

7372


When first time we are testing the screen then we have to write that this screen should contains so & so columns [ suppose there r 10 columns on that screen]in the expected result

1763


Risk Analysis a) 2 step, b)3 step, c) 4 step, d) 6 step

2051


Write UI Test case, Integration Test case, Functional Test case & Performance Test case for the File Menu for MS-Word?

2661


send the senario template

1931


Hi, I am planing to give ISTQB - Foundation level exam. Can anyone forward the ISTQB materials at laxmi_002@rediffmail.com mail ID.

1904


Differentiate verification and validation?

1316


wat is meant by frontend and backend testing

6211


which sanity testing is performed?

1657


How to write test case for view the table(i.e it is already stored in database and see the content in the table)

2552


If asked to create a Configuration Design Pattern, where would you start?

1722


how will we change the server system time?

2288


Hello all, Can someone tell me what kind of questions i can expect from hiring manager along with two team members on final face to face interview for manual testing position.. I am switching from BA to QA as its better on benefits etc.. Thanks in advance

2028


please give information about ERP Projects and how V-model use in project

2846