Loverson O.

Maguiwe August 16, 2021

Erika G. Maguiwe
BSIT/2

What is prototype model (Overview)?

- A prototyping model suggest that before carrying out the development of the
actual software, a working prototype of the system should be built.
- A prototype is a toy implementation of the system.
- Prototype is a working model of software with some limited functionality.
- Prototyping is used to allow the users evaluate the developer proposals and try
them out before implementation.

HOW DOES THE PROTOTYPE MODEL LOOK?

STEP OF THE PROTOTYPE MODEL
Requirements gathering and Analysis:
A prototype model begins with requirements analysis, and the requirements of the
system are defined in detail. The user is interviewed in order to know the requirements
of the system.
Quick design:
When requirements are known, a quick design for the system is created. It is not a
detailed design, it includes the important aspects of the system, which gives an idea of
the system to the user.
Build prototype:
Information gathering from quick design is modified to form a prototype. It represents a
‘rough’ design of the required system.
Customer evaluation of prototype:
The build prototype is presented to the customer for his/her evaluation.
Prototype refinement:
Once the user evaluates the prototype, it is refined according to the requirements.
When the user is satisfied to the developed prototype, a final system is developed
based on the final prototype, which is developed by the iterative method means we
design the system according to the final prototype, after that implement, test the product
to find the error and at last we maintain the system.

NEED OF THE PROTOTYPE MODEL

Prototype provides a method to examine design problems and evaluating solutions.
“…Prototypes are not self-explanatory…. Clarifying what aspects of a prototype
correspond to the eventual artifact─ and what don’t─ is a key part of successful
prototyping.”
The development of the prototype model is expensive but is a good model because it
satisfies all the requirements of the customers.
Advantages of Prototype model:

 Users are actively involved in the development

 Since in this methodology a working model of the system is provided, the users
get a better understanding of the system being developed.
 Errors can be detected much earlier.
 Quicker user feedback is available leading to better solutions.
 Missing functionality can be identified easily
 Confusing or difficult functions can be identified
Requirement’s validation, Quick implementation of, incomplete, but
 When prototype is shown to the user, he gets a proper clarity and 'feel' of
the functionality of the software and he can suggest changes and modifications.
 This type of approach of developing the software is used for non-IT-literate
people. They usually are not good at specifying their requirements, nor can tell
properly about what they expect from the software.
 When client is not confident about the developer's capabilities, he asks for a
small prototype to be built. Based on this model, he judges capabilities of
developer.
 It reduces risk of failure, as potential risks can be identified early and mitigation
steps can be taken.
 It provides a working model to the user early in the process, enabling early
assessment and increasing the user confidence.
 The developer gains the experience and insight by developing a prototype,
thereby resulting I better implementation of the requirements.
 It helps in reducing the risk associated to the project.
 The prototyping model serves to clarify requirements, which are not clear, hence
ambiguity and improving communication between developer and user.
 There is a great involvement of the users in software development. Hence the
requirements of the users are met to the greatest extent.
Disadvantages of Prototype model:

 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.
 functional, application.
 Prototyping is usually done at the cost of the developer. So it should be done
 using minimal resources. It can be done using Rapid Application Development
(RAD) tools. Please note sometimes the start-up cost of building the
development
team, focused on making prototype, is high.
 Once we get proper requirements from client after showing prototype model, it
 may be of no use. That is why, sometimes we refer to the prototype as
"Throwaway" prototype.
 It is a slow process.
 Too much involvement of client, is not always preferred by the developer.
 Too many changes can disturb the rhythm of the development team.

 If the user is not satisfied with developed prototype, then a new prototype is

developed. This process goes on until a perfect prototype evolves. Thus, this

model is time consuming and expensive.

 The developer loses focus of the real purpose of the prototype and compromises

on the quality of the product. For example: - he/she may apply some of the

inefficient algorithms or inappropriate programming languages used in

developing the prototype.

 Prototype model can lead to the false expectations. It often creates a situation

where the user believes that the development of the system is finished when it is

not.

 The primary goal of the prototype model is rapid development. Thus, the design

of the system may suffer as it built in a series of layers without considering

integration of all the other components.