Explain V model in detail?

Showing Answers 1 - 18 of 18 Answers

Ashish

  • Feb 2nd, 2006
 

V model - means the testing involvement starts from the design state itself & continues till system test.

Phase             Testing

Requirements - review

design - review

TR - TUT

then testing phases starts.

So, like this testing makes a perfect V. so we call it V model.

  Was this answer useful?  Yes

Deepu

  • Feb 16th, 2006
 

"V" Model is one of the SDLC Methodologies.

In this methodology Development and Testing takes place at the same time with the same kind of information in their hands.

Typical "V" shows Development Phases on the Left hand side and Testing Phases on the Right hand side.

Development Team follow "Do-Procedure" to achive the goals of the company

and

Testing Team follow "check-Procedure" to verify them

jagan

  • Feb 22nd, 2006
 

until now i not get a clear idea , any one can explain me in detail

  Was this answer useful?  Yes

Anitha

  • Feb 24th, 2006
 

'V' Model

   

              SRS/BRS                                          User Acceptance

                 Analasis/Design                         System Testing

                           HLD                            Integration Testing

                              LLD                    Unit Testing

                                         Coding

              

  Was this answer useful?  Yes

mselvaam

  • Feb 28th, 2006
 

SRS                                                                            User Acceptance

         Design                                                      System Testing

                     HLD                                       Integration Testing

    SDLC                   LLD                    Unit Testing       STLC

                                         Coding

  Was this answer useful?  Yes

kavita kharayat

  • May 3rd, 2006
 

Testing should do along with development process. That is what Spiral SDLC is talking about. In V model, testing and development phases are performing parallel. In that aspect Testing fits in V modelKavita Kharayat

  Was this answer useful?  Yes

Ramesh Madiwalar

  • May 26th, 2006
 

hi i want the detail information abt the V model, i know the block diagram but i don know practically how we can use in the application if anybody knows this please forward the article or detail  to ramesh.madiwalar@gmail.com

Ashish Vats

  • Oct 12th, 2006
 

I am highly agreeing with Deepu¬ís statement. This is the perfect defination of V model.

  Was this answer useful?  Yes

Abdul.Sameer

  • Apr 4th, 2007
 

Hi

V-Model is a Testing Life Cycle Model which is entirely different from Software Development Life Cycle.
V-Model is used for tester's where as SDLC we have developers and testers.

SDLC models are

1. Waterfall model
2.Prototype Model
3. Spiral Model

TLC Models are

1. Fish Model and
2. V-Model

In V-Model the
strategy goes like this

 Gathering phase                                                            User Acceptance Testing.

         Analysing
phase                                     System Testing
   
              Design Phase
             (HLD and
LLD)                           Integration Testing

                     Coding
phase              Unit Testing

                                            build


Here unit testing is done related to Coding
Integration testing is based on Design phase
System Testing is done related to Requirements (Analysing phase)
User acceptance is done based on Gathering phase.


Thanks
sameer
QA Test Lead( Certified Tester)

  Was this answer useful?  Yes

Bob Corrick

  • Apr 16th, 2007
 

Does anyone have a reference to the Fish model (context: testing life cycle)?

  Was this answer useful?  Yes

Pothiraj

  • Jun 19th, 2007
 

The level of test is the primary focus of a system and derives from the way a software system is designed and built up. Conventionally this is known as the "V" model, which maps the types of test to each stage of development.


A diagram showing the development and testing steps described in the text.
http://www.csus.edu/indiv/L/LegorretaL/160_Spring_2005_V-Model_files/vmodel.gif

  Was this answer useful?  Yes

satish.anna

  • Apr 23rd, 2008
 

V model is a process model that helps in improving the quality of the software product by combining SDLC & STLC. In this model both SDLC & STLC works parallel. The left hand side of the V model contains SDLC in down-hill direction & the right hand side of the V Model contains STLC in up-hill direction.

V Model is a process where development & testing can do parallel. For every development phase there is a testing phase. Development phases are called as verifications & testing phases are called as validations. Here the verification means the software implements correctly or not & the validation means the software that has been built is traceable to customer requirements or not.

syed noor

  • Aug 6th, 2011
 

"V" Model is one of the SDLC Methodologies.
In this methodology Development and Testing takes place at the same time with the same kind of information in their hands.
Typical "V" shows Development Phases on the Left hand side and Testing Phases on the Right hand side.
Development Team follow "Do-Procedure" to achieve the goals of the company
and
Testing Team follow "check-Procedure" to verify them.

  Was this answer useful?  Yes

prabhakar

  • Aug 7th, 2011
 

it stands for verification and validation process it always close relation between Developer and QA.
when the Developer to Develop a module that module immidiatly sent to tester.The tester can test the Application

  Was this answer useful?  Yes

chandra

  • Sep 5th, 2011
 

V' Model

BRS User Acceptance
reviews
SRS System Testing
reviews
HLD Integration Testing
reviews LLD Unit Testing
Coding
" V" stands verification and validation. In this model the multiple stages of development process and multiple stages of testing. The testing at documents level is calling as verification. The testing at programs program interconnection and the software is calling as validation. That STLC means that verification and validation

  Was this answer useful?  Yes

Barb

  • Oct 11th, 2011
 

I think there are two ways to review this one is that as each set of deliverable is produced there is a validation process that goes with it
Therefore the Requirements deliverables are validated and the outcome should be an acceptance test plan and the finished application should be accepted based on those requirements.
As the design and development deliverables are finalized an integration of system test plan should be developed as an outcome of the validation of those deliverables and the application is accepted and validated based on the information from that level of deliverable
at a lower level program and module specifications are used as the basis for program or module level tests (white box) and unit level test plans are the result of those validation activities.
The validation activities that create the test plans occur shortly after the deliverable is created in an effort to catch defects or issues in the deliverable to take advantage of the cost of changes curve metric. The plans are executed in reverse order of their creations Program or unit tests executed first created last, integration plans created second and executed second, acceptance plans created first and executed last.

In all instances the plans should include test case definitions and details as the design and UI definitions become available.

  Was this answer useful?  Yes

Hi,
V model : As the letter "V" says, left line of the "V" contains the developing phases while right line of the "V" contains all the testing phases.
For each level of a development phase there is an associated testing phase.
Thanks

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

Answer Question

Click here to Login / Register your free account


 
Send   Reset

 

Related Answered Questions

 

Related Open Questions