Quality Testing

Quality is delighting customers

Hi all,

Why you are using V Model...? 

is it better than other models...?

Can any one please explain ....



Views: 5539

Reply to This

Replies to This Discussion

V Model for Testing


V Model is a development model which demonstrates the relationship between each phase of development life cycle and related phase of software testing. The left side of the V Model consists of development phase and the right side of the V Model consists of software testing phase. The flow of V Model will be start at Requirement phase and end at Acceptance Testing phase. 

Testing document in a software testing phase will be derived from the document in development phase that stays at the same level (e.g., Acceptance Testing and Requirement Phase, System Testing and Specification Phase). So, tester can start working on software testing activity as soon as the development activity starts.

The benefit from early software testing activity is that we can detect some faults early. As a result of early fault detection, the cost for fixing will be less.

Thanks swetha...

Thanks Nagaraju

Hi Kavya,

Advantages of v model :

a) Proactive defect tracking i.e defects r found at early stages even may be in the development phase before application is tested.

b) avoids the downward flow of the defect.

c) reduces the cost for fixing the defect since defects will be found in early stages.

d) it is a fast method.



V model for Testing

v stands for verification and validation.developmant side comes under verification and testing side comes under validation.this model defines pratical testing b/w development stages and testing stages.it's applicable for large scale projects.

 Based on BRS User acceptance testing is done 

Based on SRS system testing is done 

Based on HLD integration testing is done

Based on LLD Unit testing is done

If the code and testcase are same than product is released

there is a simultaneous process on both developer and testing side

BRS: It is a document which describes about customer requirements.

SRS: It describes about functionalites to be developed as a s/w based on customer requriments

HLD:It describes about overall hirerachy of an application from root module to leaf module

LLD:It describes about internal structure of logical madules

Eg:class diagram,ER-diagram

if the requirements are not clear

use Rad Model or Prototype Model both include customer evaluation

V-Shaped Strengths


  • Emphasize planning for verification and validation of the product in early stages of product development
  • Each deliverable must be testable
  • Project management can track progress by milestones
  • Easy to use


V-Shaped Weaknesses


  • Does not easily handle concurrent events
  • Does not handle iterations or phases
  • Does not easily handle dynamic changes in requirements
  • Does not contain risk analysis activities


When to use the V-Shaped Model

  • All requirements are known up-front
  • When it can be modified to handle changing requirements beyond analysis phase
  • Solution and technology are known


TTWT Magazine





© 2022   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service