What is Prototype Model?
A Prototype model suggests that before carrying the development of the actual software, a
working prototype of the system should be built.
A prototype is a toy implementation of the system.
By using this prototype, the client can get an “actual feel” of the system, since the
interactions with prototype can enable the client to better understand the requirements of
the desired system.
Prototype is a working model of software with some limited functionality.
A prototype is a version of a system or part of the system that’s developed quickly to check
the customer’s requirements or feasibility of some design decisions.
So, a prototype is useful when a customer or developer is not sure of the requirements,
efficiency, business rules, response time, etc.
Prototyping is an attractive idea for complicated and large systems for which there is no
manual process or existing system to help determining the requirements.
In prototyping, the client is involved throughout the development process, which increases
the likelihood of client acceptance of the final implementation.
Diagram of Prototype model:
A software prototype can be used:
Prototype model should be used when the desired system needs to have a lot of
interaction with the end users.
• Typically, online systems, web interfaces have a very high amount of interaction with
end users, are best suited for Prototype model.
• Prototyping ensures that the end users constantly work with the system and provide a
feedback which is incorporated in the prototype to result in a useable system.
• They are excellent for designing good human computer interface systems.
Advantages of Prototype model:
• Customer can get quickly result.
• Users are actively involved in the development
• Testing is almost completed before build/development is completed.
• Errors can be detected much earlier.
• Quicker user feedback is available leading to better solutions.
• Missing functionality can be identified easily
Disadvantages of Prototype model:
• Time consuming and costly
• Insufficient requirement.
• Extra prototype is required.
• 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.
Post a Comment
If you have any doubts, Please let me know
Thanks!