tell me about v model

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

Answer by Lubna
Submitted on 4/2/2004
Rating:	Rate this answer:
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 Centre 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. The V shows the typical sequence of development activities on the left-hand (downhill) side and the corresponding sequence of test execution activities on the right-hand (uphill) side. In fact, the V Model emerged in reaction to some waterfall models that showed testing as a single phase following the traditional development phases of requirements analysis, high-level design, detailed design and coding. The waterfall model did considerable damage by supporting the common impression that testing is merely a brief detour after most of the mileage has been gained by mainline development activities. Many managers still believe this, even though testing usually takes up half of the project time.

Answer by Babu.j
Submitted on 10/17/2005
Rating: Not yet rated	Rate this answer:
V-Model V stands for verification and validation this modules define the mapping between Development Stage And Testing Stage Tools => Test Director for Test Doc�s Maintains Development Stage Testing Stage Information 1. Assument of Development Plan gathering 2. Prepare Test Plan 3. Requirement Phase Testing Design & coding 1. Design Phase Testing 2. Program Phase Testing [White Box Testing] Build 1. Functional & System Testing [Black Box Testing] 2. User acceptance Testing 3. Test Doc�s maintains Maintains 1. Port Testing 2. Test Software Change 3. Test affiance 4:11

Answer by Srinivasa Pakala
Submitted on 12/27/2005
Rating: Not yet rated	Rate this answer:
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 Centre 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. The V shows the typical sequence of development activities on the left-hand (downhill) side and the corresponding sequence of test execution activities on the right-hand (uphill) side. In fact, the V Model emerged in reaction to some waterfall models that showed testing as a single phase following the traditional development phases of requirements analysis, high-level design, detailed design and coding. The waterfall model did considerable damage by supporting the common impression that testing is merely a brief detour after most of the mileage has been gained by mainline development activities. Many managers still believe this, even though testing usually takes up half of the project time. Traditional Water fall model will not allow to do the testing and the coding process in parallel. V - model in the SDLC will allow the process to have testing and coding as a parallel activity which enables the changes to occur more dynamic.

Answer by rahul QA
Submitted on 12/28/2005
Rating: Not yet rated	Rate this answer:
V Model describes parellel activites of verification and validation The V-model is a graphical representation of the system development lifecycle. It summarizes the main steps to be taken in conjunction with the corresponding deliverables within computerized system validation framework. Verifcation is the different set of activities which ensure that how the product is tracable accoring the requirement specification Validation is the different set of activities which ensure that how the product is tracable accoring the needs of client/customer walkthrough,inspection which are included in verification Testing is validating the specified requirement verification involves application of the system in simulated environment validation involves application of the system in real time environment

Answer by THE TESTER (f)
Submitted on 5/13/2006
Rating: Not yet rated	Rate this answer:
from the real-world experience: The V-model is a "concept" that creates the perception that it increases quality and shortens development time by running the testing in a parallel process to the coding. it has the same processes/artifacts as waterfall. But by doing it parallel it creates more instabilities than solutions. Like any methodology concept, it is as good as the commitments of team members and stakeholders using it. (budget and deadlines rule!). Testing and quality simply have more at risk since the code being released is like "shifting sands". In the end quality is mitigated "in production" or after go-live and a new project is started to address the issues. truth be told all projects are shoe horned to some degree and testing is usually the sacrifice. After all even Microsoft makes patches! Ms. Roberts 17 years experience in software quality.

Answer by Bindumathi
Submitted on 9/6/2006
Rating: Not yet rated	Rate this answer:
model is a software development life cycle in which the development team as well as the testing team work together.its an efficient model compare to other model.If there is a high quality product as to be developed the customer resource specification will be moved to SRS(software resource specification).SRS is a document which is generated after the discussion with the customer so that it can be implemented in the software. CRS(coustemer resource specification)copy goes to testing engineers they will start preparing the testing plans for that document if they find any errors or conflict in the document immediately they will send it to the SRS team.This team wold have been made SRS for that they will send it back to CRS for the error rectification.This type with the development team & testing team try to find the bugs simultaneously as much they can.This is less time consumption and efficient model. The drawbacks are this model is expensive cannot be applied for low quality products.

Answer by Preeti
Submitted on 1/16/2007
Rating: Not yet rated	Rate this answer:
All that gather is:- It is about testing does not have to occur once the 'code' has been delivered which is what you need to have to begin test execution. The testing can start early with analysing the requirements and creating test criteria of 'What' you need to test. The right tail of the V represents the testing stream where the systems are being tested (against the specifications defined on the left-tail). The bottom of the V where the tails meet, represents the development stream Conclusions But this V-Model is an inadequate model for software development for the following reasons: �h�n It is too simple to accurately reflect the software development process, and can lead managers into a false sense of security. �h�n It is inflexible; it has no ability to respond to change. �h�n It produces inefficient testing methodologies.

Answer by Sapna Pillutla
Submitted on 5/14/2007
Rating: Not yet rated	Rate this answer:
The V-Model is a method in which the development and the testing team will perform work in a simultaneous and an independent manner. The devleopment and the test teams will begin planning the development and the testing process separately. However they use the same data/information and begin at the same time i.e during project start. At pre defined intervals, the test team will test the development process deliverables to idenfity defects. During UAT both teams will work together to ensure that the system/application is deployed into the production environment. Again during the maintainence phase the teams split. The development team works on the changes/enhancements while the test team tests the changes made.

Answer by MASBRO
Submitted on 6/5/2007
Rating: Not yet rated	Rate this answer:
the true benefit of the v-model is that it allows the testing teams to review documentation very early in the lifecycle, to review a document by a wider group will obviously find more errors that can be fixed in the document before the software is developed, saving time and money. The extra benefit is that when the tester begins to prepare their tests against documentation more faults can be found then just by review this is due to the level of detail required in order to understand how to test the delivery again adding extra benefit in cost and time savings, the key to a good v model is controlled change management where all parties understand the impact to each other in the process and tightly respected and controlled review periods

Answer by AppuKutty
Submitted on 6/18/2007
Rating: Not yet rated	Rate this answer:
The V model is an approach for Software testing methods. This is one of the most popular model used in the industry. This is actually derivied from Germany and found to be more popular;y used in the Europe in the Late 1970's The V model is an extension of the Waterfall Model. The only Advantage of this model is, we can perform the test operations during the course of the development, thereby reducing the cost and other factors which affect the development lifecycles in Project Management. Considering the Phases of SDLC which is Design, Analysis, Coding, Testing and Maintenance, this falls in the Second phase which is co-related to the testing phase of the SDLC. The Analysis phase is disintegrated into (Req. Analysis, System design, Arch Design, Module Design) which is followed by the Coding. These are the Left part of the "V" Model which explains the disintegration of the Requirements given or extracted, while after the coding stage which is the 2nd phase of the SDLC, we go to Testing Stages which follows up like (Unit Testing / Module Testing, Integration Testing, System Testing and User Acceptance Testing). These mentioned Testing stages forms the right hand side of the "V" model. There is always a co-relation between the Left hand-side and the Right Hand side of the "V" Model. During the coarse of development, there is always a drive to parallely to the testing phase and have it checked whether the modules being developed are correct. This in terms cuts nearly 100% of investment that would have been made for the project to have it tested after it is developed. That's All. Warm Regards, Srinivasan Senthil.

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

[ Home | FAQ-Related Q&As | General Q&As | Answered Questions ]

Question by ask
Submitted on 7/30/2003
Related FAQ: comp.software.testing Frequently Asked Questions (FAQ)
Rating:	Rate this question:
tell me about v model

Answer by jagadeesh
Submitted on 8/2/2003
Rating:	Rate this answer:
'V' shape model describes about the process about the construting the application at a time all the Analysing, designing, coding and testing will be done at a time. i.e once coding finishes it'll go to tester to test for bugs if we got OK form tester we can immediately start coding after coding again send to tester he'll check for BUGS and will send back to programmer then he,programmer can finish up by implementing the project. it is the model what is using by most of the companies.

Answer by anita
Submitted on 8/6/2003
Rating:	Rate this answer:
v model is model in which testing is done prallelly with development.left side of v model ,reflect development input for the corresponding testing activities.

Answer by Niranjan
Submitted on 10/21/2003
Rating:	Rate this answer:
V model is the classic software development model. It encapsulates the steps in Verification and Validation phases for each step in the SDLC. For each phase, the subsequent phase becomes the verification (QA) phase and the corresponding testing phase in the other arm of the V becomes the validating (Testing) phase

Answer by Ian
Submitted on 11/12/2003
Rating:	Rate this answer:
Does any one know of a website that includes samples of the different diagrams. Thank you Ian

Answer by karthi_dk
Submitted on 11/28/2003
Rating:	Rate this answer:
In the Software Development Life Cycle,both the Development activity and the testing activities starts almost at the same time with the same informations in their hands. The development team will apply "do-procedures" to achieve the goals and the testing team will apply "Check-procedures" to verify that. Its a parallel process and finally arrives to the product with almost no bugs or errors

Answer by Farhan
Submitted on 12/4/2003
Rating:	Rate this answer:
V model is where Parallel work goes simontaneously , its verification ......, Validation....,

Answer by sigma
Submitted on 12/16/2003
Rating:	Rate this answer:
V model is a definition in psychology. When a human being faces a change in its environment, at first it feels so motivated and enthusiastic but later, when he frustrates, the motivation goes down deeply. But at the end, when he sees the light at the end of the tunnel, suddenly the motivation starts to go up. This is called V model.

Answer by Icon
Submitted on 1/8/2004
Rating:	Rate this answer:
Some of the answers I find here are too rudimentary. People talkin on these boards should think twice as they could mis-guide newbies

Answer by vp
Submitted on 1/28/2004
Rating:	Rate this answer:
Traditional Water fall model will not allow to do the testing and the coding process in parallel. V - model in the SDLC will allow the process to have testing and coding as a parallel activity which enables the changes to occur more dynamic.

Answer by Hex
Submitted on 2/12/2004
Rating:	Rate this answer:
http://www.comp.glam.ac.uk/pages/staff/bfjones/seminal/seminal1/sld002.htm

Answer by simon
Submitted on 2/27/2004
Rating:	Rate this answer:
The V model is a method of software development, which allows visibility of where we are by stages. Development goes hand in hand with testing and validation, where each step is baselined before proceeding to the next. It replace the waterfall model of the 1970s. It has now been superceded by approaches such as evolutionary and iterative methods.

Answer by Adisehsu
Submitted on 4/7/2004
Rating:	Rate this answer:
V- model is a process where the development and testing phases can do parallely. For every development phase there is a testing phase. Development phases are called as verification whereas testing phases are called as validation. Here verification means the software implements correctly or not. Validation means the software that has been built is traceable to the customer requirements or not. Adiseshu

Answer by harry singh
Submitted on 4/15/2004
Rating:	Rate this answer:
http://www.softwaredioxide.com/Channels/events/testing2001/Proceedings/vijay_honeywell.pdf

Answer by srinivas
Submitted on 5/2/2004
Rating:	Rate this answer:
V-model is one of the sdlc and stlc . it includes testing from the unit level to bussiness level . That is after completing the coding tester starts testing the code by keeping the design phase documents that all the modules had been integrated or not ,after that he will verify for system is according to the requirements or not , and atlast he will go for business scenarios where he can validate by the customer and he can do the alpha testing and beta testing . And atlast he decides to have the complete stable product.

Answer by Anil Jadhav
Submitted on 6/14/2004
Rating:	Rate this answer:
V Model is the process model to provide quality product by combining SDLC and STLC. In this model Both SDLC & STLC works parallely. Left Hand side of the V model contains SDLC in downhill direction whereas right hand side of the V model contains STLC in Uphill direction.

Answer by bala
Submitted on 6/17/2004
Rating:	Rate this answer:
In V model approach when the System test cases, integration, UA test cases are written. My understanding is, UAT & System test cases are written at the early stage of design phase followed by integration test cases. At the end of design stage, along with the design artifacts, these test cases should also be signed off. Please clarify.

Answer by Anil
Submitted on 7/11/2004
Rating:	Rate this answer:
The V model shows the Development Cycle Stages and Maps it to Testing Cycles,but it fails to address how to start for all these test levels in parallel to development.It is a parallel activity which would give the tester the domain knowledge and perform more value added,high quality testing with greater efficiency.Also it reduces time since the test plans,test cases.test strategy are prepared during the development stage itself.

Answer by NSR
Submitted on 8/19/2004
Rating: Not yet rated	Rate this answer:
Actually V-Model follows IVV method (Independent Verification and Validation). In this method testing is done prallelly with development . The left side of the V reflects Verification and right of the V reflects Validation.

Answer by sagar
Submitted on 9/7/2004
Rating: Not yet rated	Rate this answer:
in this process , testing starts in parallel with programming for the speedy completion of the project

Answer by Nanda/Trevi/Shivu
Submitted on 9/13/2004
Rating: Not yet rated	Rate this answer:
Verification & Validation processes propose the Software Development V-model. This process considers development and testing to be a V. The left side of the V is the development and the rightside is Testing. At each point down the left side of the V there is a corresponding Test that checks whether the development is correct.The tests proposed at each level can be planned and designed in parallel to lower level activities being conducted. This way as we come up the right side of the V, the testing is ready to commence.

Answer by Shilpa Gattani
Submitted on 9/22/2004
Rating: Not yet rated	Rate this answer:
V model is integration of software developement & testing. Both the activities go together. Output of previous step is input to the next step. Verifications & validations both the activities performed together.

Answer by chandu
Submitted on 9/30/2004
Rating: Not yet rated	Rate this answer:
V model Method is best method for testing In SDLC is is Both development and testing activities starts at almost same time We can say it as Parllal is process .Finally we arrives to the bugs free product

Answer by santosh kumar.k
Submitted on 10/1/2004
Rating: Not yet rated	Rate this answer:
V model is basically "Verification" and "Validation" model in this model both the development and test activities takes place simultaneously this model is a most optimized model.In this initially after completion of first phase of development then the testing team will prepare test cases for that phase and it continues like that up to last phase.

Answer by Ashy
Submitted on 10/10/2004
Rating: Not yet rated	Rate this answer:
like....huhuhuhuhuhuhu

Answer by Tariq
Submitted on 11/5/2004
Rating: Not yet rated	Rate this answer:
In real Life if you see the V Model it is a failure. there are many Reasion for that but right now i will tell you the one reasion. In real Life you will Never get the all requirments while you are in SDLC phas II. where you have to Decide what SDLC model you are going to use in project life. so for that you the V model needs all the Requirment if i am Not wrong. if there are some changes later on in requirments. so the V model failed over here. there are many other Reasions.

Answer by dsfdfdfd
Submitted on 11/26/2004
Rating: Not yet rated	Rate this answer:
dfdfasdfasdfassdfsfsdfdsfszfssdffsd

Answer by Ajit Rao
Submitted on 12/6/2004
Rating: Not yet rated	Rate this answer:
The 1:1 left-right mapping in the V or Hinged Waterfall model surely helps in easing the cumbersome activity of Testing (in the right side of the V model) which otherwise would is a nightmare in the Waterfall model.

Answer by NAG
Submitted on 1/17/2005
Rating: Not yet rated	Rate this answer:
V-model shows the development cycle stages and maps it to testing cycle. Because testplan,testcase,test strategy everything is done in the coding stage. Validation means the software that has been built is traceable to the customer requirements or not.

Answer by euluis
Submitted on 1/20/2005
Rating: Not yet rated	Rate this answer:
This article in SDMagazine, by Robin F. Goldsmith and Dorothy Graham, explains it: http://www.sdmagazine.com/documents/s=7224/sdm0207e/0207e.htm

Answer by Gursharan
Submitted on 2/16/2005
Rating: Not yet rated	Rate this answer:
http://www.cutter.com/itjournal/rightupfront.html

Answer by Hub van de Bergh
Submitted on 3/5/2005
Rating: Not yet rated	Rate this answer:
Application of V-model is not limited to software engineering. See www.hvdb.tk for a diagram and description of the V-model.

Answer by swanand
Submitted on 3/14/2005
Rating: Not yet rated	Rate this answer:
In V-Module, Development and Testing works parallel to each other. it is from Business Requments upto codeing.Tester work with developer.Unit Testing, Integration Testing, System Testing, Acceptance Testing. works with Development Cycles like. coding ,functional design,Internal design, business concepts.

Answer by Farqualeet Ishrat
Submitted on 3/29/2005
Rating: Not yet rated	Rate this answer:
V model is the model in which the development of the software and the testing is done simultaneously.

Answer by bhuvana
Submitted on 3/29/2005
Rating: Not yet rated	Rate this answer:
Every individual phase grows in the shape of of 'V' and hence bares this name; this is the most widely used model for new development. The actual process of testing starts right from the beggining of development