Skip to content
Related Articles
Open in App
Not now

Related Articles

Difference between Prototype Model and RAD Model

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

1. Prototype Model : 

The prototype model is a software development life cycle model which is used when the customer is not known completely about how the end product should be and its requirements. So in this model, a prototype of the end product is first developed by the developers and then tested and changes were made as per customer feedback until the customer is satisfied with the prototype.

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 Prototype Model and RAD Model :

S.No.Prototype ModelRAD Model
1.A prototype model is a software development model where a prototype is built, tested and then refined as per customer needs.RAD model is a software development model where by the components or functions are developed in parallel as if they were mini projects.
2.

Phases-

  1. Requirement Analysis
  2. Quick Design
  3. Build Prototype
  4. User Evaluation
  5. Refining Prototype
  6. Implement and Maintain

Phases-

  1. Business  Modelling
  2. Data Modelling
  3. Process  Modelling
  4. Application Generation
  5. Testing and Turnover
3.It is suitable for high-risk projects.It is not suitable when technical risks are high.
4.It does not give emphasis on risk analysis.It give emphasis on risk analysis.
5.In this, quick initial reviews are not possible.In this, quick initial reviews are possible.
6.It does not support automatic code generation.It supports automatic code generation as. results in minimal code writing.
7.It is best suited when the requirement of the client is not clear and supposed to be changed.It is best suited when the customer requirements are clear.
8.In this user involvement is high.In this user Involvement is only at the beginning.
9.Low team size is sufficient.It requires a large team to carry out the operations.
10.End-Product cannot be developed in less time.End-Product can be developed in less time.
11.

When to use-

  • In case of high interaction requirement like in online platforms and web interfaces from the end-users.
  • When programmers are novice to the field.
  • Whenever end-user input in terms of feedback on the system is required.

When to use-

  • If system modularization is possible for its delivery in incremental manner.
  • If sufficient budget is available for automated code generation.
  • Availability of designers for modelling
  • Expertise available with respect to domain possessing relevant and requisite knowledge
  • In case of changing requirements during the project 
My Personal Notes arrow_drop_up
Related Articles

Start Your Coding Journey Now!