Prototype Model or Pilot Model in software Testing

Prototype Model (Pilot Model)

Prototype module is just a demo application to show client, who does not belongs to the IT sector. It just to show how the application looks after completion whether he wants any changes or as it is.

•         I.            Prototype is a working model of software with some limited functionality.
•       II.            The prototype does not always hold the exact logic used in the actual software application and is an extra effort to be considered under effort estimation.
•     III.            Prototyping is used to allow the users evaluate developer proposals and try them out before implementation.
•     IV.            It also helps understand the requirements which are user specific and may not have been considered by the developer during product design.

Following is the step-wise approach to design a software prototype:

1. Basic Requirement Identification: This step involves understanding the very basics product requirements especially in terms of user interface. The more intricate details of the internal design and external aspects like performance and security can be ignored at this stage.
2. Developing the initial Prototype: The initial Prototype is developed in this stage, where the very basic requirements are showcased and user interfaces are provided. These features may not exactly work in the same manner internally in the actual software developed and the workarounds are used to give the same look and feel to the customer in the prototype developed.
3. Review of the Prototype: The prototype developed is then presented to the customer and the other important stakeholders in the project. The feedback is collected in an organized manner and used for further enhancements in the product under development.
4. Revise and enhance the Prototype: The feedback and the review comments are discussed during this stage and some negotiations happen with the customer based on factors like, time and budget constraints and technical feasibility of actual implementation. The changes accepted are again incorporated in the new Prototype developed and the cycle repeats until customer expectations are met.

Advantages:-

1. Changes in prototype can be made with list effects compare to the real application.

2. There will be no confusion among customer and the company.

3. Company brings out customer acceptation.

Disadvantages:-

1. Time, cost, resources are required more.

2. Once the real application is developed the prototype is not in use.

You May also like:
Complete Testing Material

Testing basic interview questions