Prototype Model in Software Testing

software testing tutorial

What is Prototype Model?

The requirements are collected from the client in a textual format. The prototype or dummy of the software product is developed. The prototype is just an image or picture of the required software product as per requirements. The customer can look at the prototype or dummy and if the client is not satisfied, then he can request more changes in the requirements.

Prototype testing means developers and testers are checking if all the components mentioned in requirements are existing or not. The difference between prototype testing and actual testing – in Prototype testing, testers are checking all the components as per requirements are exist or not, and on the other hand, in Actual testing testers check all components are working.

The prototype is not a complete system and many of the details are not represented in the prototype. The goal of prototype model is to provide a system with overall functionality as per requirements.

There are two types of prototypes: –

  1. Static Prototype: – It does not contain detailed information about prototype or no information about other pages prototype or dummy.
  2. Dynamic Prototype: – It has links to other pages, links are for navigation of other pages prototype or dummy.

Steps that follow in Prototype model:-

  1. Requirement Collection: – In this step requirement collected from the client side.
  2. Design & Development of Prototype: – In this step prototype/ dummy are created as per requirement for the client.
  3. Prototype Testing: – Testers test the dummy that is created.
  4. Customer Review: – In this step, prototype sent to the client, changes made by the client then again designing of prototype steps involved. If customer finalized/approved the prototype then next step will follow.
  5. Designing: – Actual designing involved in this step.
  6. Coding: – Actual software is to develop in this step by developers
  7. Testing: – Tester tests the actual software.
  8. Installation: – In this step, software installation is done at client place.
  9. Maintenance: – Requirement change according to business demand and issue fixing are involved in this step.


prototype testing


Advantages of Prototype Model:

  1. Users are actively involved in the development.
  2. Errors can be detected much earlier in this SDLC process.
  3. Early user feedbacks, leads to better outcome.
  4. Missing and wrong functionality can be identified easily and early.
  5. This model helps us to gain high-quality product.

Disadvantages of Prototype Model:

  1. Too much documentation required
  2. There is delay in starting the real project
  3. Once the prototype is ready you can’t use it in other projects
  4. Since you have satisfies the customer and built the prototype, this process is much time-consuming.

Applications of Prototype Model:

  1. We use this model when we don’t know what the client wants or client requirement is too abstract.
  2. We use this model whenever the client is new to the Software World