What is Prototype Model in Software Engineering?

In this post you will learn about Prototype Model in Software Engineering and their advantages and disadvantages.The Prototyping Model is a Systems Development Methodology (SDM) within which a paradigm output (or an early approximation of a final system or product) is constructed, tested, and then reworked. It is done till an appropriate paradigm is achieved to help develop the entire system or product. This model works best in situations when all the details or requirements are not known well in advance. It is majorly a trial-and-error process which works in an iterative fashion.. 

Advantages:

1. Users are actively involved in the development
2. Since in this methodology a working model of the system is provided, the users get a better understanding of the system being developed.
3. Errors can be detected much earlier.
4. Quicker user feedback is available leading to better solutions.
5. Missing functionality can be identified easily
6. Confusing or difficult functions can be identified
7. Requirements validation, Quick implementation of, incomplete, but functional, application.

Disadvantages:

Leads to implementing and then repairing way of building systems.
Practically, this methodology may increase the complexity of the system as scope of the system may expand beyond original plans.
Incomplete application may cause application not to be used as the
full system was designed
Incomplete or inadequate problem analysis

There are many steps within the Prototyping Model:

1. New system requirements or expectations of the system output are outlined in as much detail as possible. This requires interviewing variety of users, representing all the segments or stakeholders of the prevailing system.

2. A preliminary layout specification is formed for the new system.

3. A first output model of the new system is made from the preliminary layouts. This is often a scaled-down system which tentatively gives an approximation of the desired output required.

4. The users check the primary output, noting its strengths and weaknesses, the things which need to be carried ahead in the next steps and the things which need to be discarded. The developer collects and examines the remarks from the all the stakeholders.

5. The first paradigm is changed, supported by the comments provided by the users, and is shaped to a second output of the new system.

6. The second output is evaluated in the same manner as was the primary output.

7. These steps are reiterated persistently, till the users are satisfied with the output.

8. The final system is hence constructed, supported by the ultimate output. The final system is completely evaluated and tested. Routine maintenance is administered on a seamless basis to forecast large-scale failures and to reduce the time period.



When To Use:
1.when the requirement of customer is unclear and certainly changing at that time prototype model are used.

 2. in this model generally evolved a customer interaction.