Prototyping
INFORMATION
The basic idea in Prototype model is that instead of
freezing the requirements before a design or coding can proceed, a
throwaway prototype is built to understand the requirements. This
prototype is developed based on the currently known requirements.
Prototype model is a software development model.
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.
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.
Overview
The prototype are usually not complete systems and many of the details
are not built in the prototype. The goal is to provide a system with
overall functionality.
Primary Principles.
The main principles behind the Prototyping approach are:
Basic Requirement Identification Developing the initial Prototype Review of the Prototype Revise and Enhance the Prototype.
Strengths:
Confusing or difficult functions can be identified Errors can be detected much earlier Missing functionality can be identified easily Quicker user feedback is available leading to better solutions Users are actively involved in the development Users get a better understanding of the system being developed.Weaknesses:
Incomplete application may cause application not to be used as the system was designed Leads to implementing and then repairing way of building systems May increase the complexity of the system as scope of the system may expand beyond original plans..
Downloadable reference material being added in due course.
Downloadable reference material being added in due course.
Downloadable reference material being added in due course.