Monday 4 June 2012

The V-model

The V-model represents a software development process ( also applicable to hardware development ) 

which may be considered an extension of the Waterfall model . Instead of moving down in a linear way , 

the process steps are bent upwards after the coding phase , to form the typical V shape . The V-Model 

demonstrates the relationships between each phase of the development Life Cycle and its associated 

phase of testing . The horizontal and vertical axes represents time or project completeness ( left-to-right ) 

and level of abstraction ( coarsest-grain abstraction uppermost ) , respectively . 



The V Model , while admittedly obscure , gives equal weight to testing rather than treating it as an afterthought .Initially defined by the late Paul Rook in the late 1980s , the V was included in the U .K .’s National 

Computing Center publications in the 1990s with the aim of improving the efficiency and effectiveness of 

software development . It’s accepted in Europe and the U .K . as a superior alternative to the waterfall model ; 

yet in the U .S . , the V Model is often mistaken for the waterfall . 

V-Model : V- stands for Verification and Validation 

1.It is a recognized model by organizations 

 
2.This model defines the mapping in between multiple stages of development and multiple stages of testing


 

To decrease project cost ,the organizations are maintaining the separate testing team only for system testing . Because the system testing stage is working as bottle neck stage in software development . 

2 comments:

  1. There is bug in above V model Diagram

    ReplyDelete
  2. Would you please explain the bug so I will update it accordingly which is helpful for the others also.

    ReplyDelete