Definition

01 02 03
The prototyping model This prototype is then The prototyping model
is a software used to gather feedback is an iterative process,
development model that from users and and the prototype is
involves creating a stakeholders, which is typically refi ned and
working prototype of the
then used to improve the improved over several
software before design of the system. iterations.
developing the full
system.
 Is the process of creating a working model of
a product or process before developing the
final version. Prototypes can be used to test
ideas, gather feedback from users and
stakeholders, and refine the design before
investing too much time and money into
development.

What
Prototyping Prototypes can be made from a variety of
materials and at different levels of fidel ity.
A low-fidel ity prototype might be a simple
sketch or mock up, while a high-fidel ity
prototype might be a working model that
looks and feels very similar to the final
product.
What is Prototyping?
Prototyping is an important part of many different design and
development processes, including:
• Software development: Prototypes can be used to test different features and
functionality, and to get feedback from users on the overall design and
usability of the software.
• Product design: Prototypes can be used to test different form factors,
materials, and features of a product before investing in mass production.
• Web design: Prototypes can be used to test the layout, navigation,
and functionality of a website before it is launched.
• Business process design: Prototypes can be used to test new business
processes and identify any potential problems before they are implemented in
the real world.
 Requirements gathering and
analysis: The fi rst step is to
gather and analyze the
requirements for the system. This
information is used to create a
Prototype development: The next
step is to develop a prototype of
the system. This prototype can
be a simple mockup or a working

Phases
prototype that meets the needs model of the system.
of users and stakeholders.

of the Prototype refi nement: The

Prototypin Prototype evaluation: The

prototype is then evaluated by
users and stakeholders. Their
prototype is then refi ned and
improved based on the feedback
recei ved. T hi s process i s typi cal l y

g Model
feedback is used to improve the repeated several times until the
design of the system. prototype is acceptable to users
and stakeholders.

System development: Once the

prototype is acceptable, the full
system is developed. The system
is developed based on the refi ned
prototype.
Key Characteristics:
. Iterative Development: The
Prototyping Model follows
an
iterative process, where
multiple versions of a
soiware prototype are
created and
refined.
 Key Characteristics:
.
User Involvement: User feedback is integral to the
Prototyping Model. It ensures that the final soiware aligns
with user expectations and needs.
Key Characteristics:
. Visualization: Prototypes
provide a tangible
representation of the final
product, aiding in better
understanding and clarifying
requirements.
 Key Characteristics:
. Rapid Development:
Prototypes are developed
quickly, allowing
stakeholders to see core
functionalities in action early
in the development process.
 Key Characteristics:
. Risk Reduction: By identifying
issues and improvements at
an early stage, the
Prototyping Model helps
mitigate risks associated with
full-scale soiware
development.
 The Prototyping Model is
most effective in the
following scenarios:
• Projects with evolving or
Use Cases: unclear requirements.
• Situations where direct user
involvement is crucial for success.
• When there is a need to
demonstrate functionality quickly
to stakeholders or clients.
Advantages:
Incomplete Functionality: Prototypes often lack full
functionality and may not represent the entire
system. This can lead to misunderstandings about
what the fi nal product will include.

Scope Creep: The iterative nature of prototyping can

sometimes lead to scope creep, where additional
features and changes are continuously requested by
users, causing the project to expand beyond its
original scope.

Resource Intensive: Developing and

maintaining prototypes can be resource-
intensive in terms
Lack of Formal Documentation:
Prototyping can sometimes lead to a
lack of formal documentation,
making it challenging for
maintenance and future development
efforts.
 Examples of successful use of the
prototype model
 Group Members:
Nodado, John Mario G.
Arcabo, Keneth Roy S.
Saberon, Jeremiah N.