Skip to content
Related Articles

Related Articles

Difference between V-model and RAD model

Improve Article
Save Article
  • Last Updated : 23 Aug, 2022
Improve Article
Save Article

1. V-model: 
V-model is the most important model that is used in the process of software testing. It is also known as Verification and Validation Model. It is Introduced by the late Paul Rook in the 1980s. V-model is a sequential process in which the next phase begins only after the completion of the present phase. In this model, steps don’t move in a linear way while the steps are bent upwards. 

2. RAD Model: 
RAD model refers to Rapid Application Development and it is a type of Incremental Model. The components or functions are developed in parallel and it can handle small projects as well as medium projects. In this model, any changes can be made at any stage. It has high productivity due to less number of people. 

Difference between V-model and RAD model :

1.V model is software development model but development and testing are not concurrent.RAD model is a software development model where by the components or functions are developed in parallel as if they were mini projects.
2.In this user involvement is also only in beginning.In this user Involvement is only at the beginning.
3.Flexibility of V-model is Little flexible.Flexibility to change in RAD model is Easy.
4.Cost of V-model is expensive.Cost of RAD model is also Low.
5.In V-model testing activities start with the first stage.Testing is done in RAD model after completion of coding.
6.Guarantee of success through V-model is high.Guarantee of success through RAD model is low.
7.It is not iterative.It is iterative.


  • Easy and simple to use.
  • Prevents the defects from flowing downward.
  • The early detection of defects is possible.
  • It is suited for small projects with clearly defined requirements.
  • Time saving as prior to coding, testing activities like planning and designing tests take place. 


  • Initial reviews are carried out quickly.
  • Shorter development period.
  • Promotes client feedback
  • Resolving of many problems related to integration problems by integrating from the start.
  • Increases the component’s reusability


  • Less flexibility
  • The documents related to testing and requirements need to be updated in between in case of any change.
  • The working software is created only during implementation phase. 


  • High reliance on modelling abilities
  • RAD can only be used to construct systems that can be made modular.
  • Identifies business requirements by looking at strong team and individual performances.
  • Need of developers and designers with advanced skills.
  • Expensive as automated code generation and modelling have very high costs.

When to use-

  • For small to medium-sized projects with fixed, clearly defined requirements.
  • When sufficient technical resources and the necessary technical expertise are available.

When to use-

  • When sufficient budget is available and necessary designers are available for modeling.
  • For building a system that can be modularized in two to three months.
  • When there is availability of resources with advanced business knowledge and a pressing need for the system to be produced quickly (2-3 months).
My Personal Notes arrow_drop_up
Related Articles

Start Your Coding Journey Now!