A prototype is according to the RAE (Royal Academy of the
language) an original copy or first mold in which a figure or something else is
made.
Characteristics
of a prototype for medical product development
Types of prototype
Low
Fidelity vs. High Fidelity
Low
Fidelity: set of drawings (for example, a presentation of scenarios)
that constitutes a static model, not computerized and non-operative of a user
interface for a system in planning.
High Fidelity: set of
screens that provide a dynamic, computerized and operational model of a
planning system.
Exploratory
vs. Experimental vs. Operational
Exploratory:
non-reusable prototype used to clarify project goals, identify requirements,
examine design alternatives or investigate an extensive and complex system.
Experimental: prototype
used for the validation of system specifications
Operational: iterative
prototype that is progressively refined until it becomes the final system.
Horizontal
vs. Vertical
Horizontal: prototype
that models many features of a system but with little detail. This detail will
reach a certain depth, will be especially useful in the early stages of design
and aims to test the global interaction mode, by contemplating common functions
that the user will use frequently.
Vertical: prototype
that models few features of a system but with a lot of detail. It will be
especially useful in more advanced stages of design and aims at the design
details test
Diagonal: horizontal
prototype up to a certain level, from which it can be considered vertical
Global vs.
Local
Global: prototype
of the complete system. Expanded horizontal prototype that models a large
number of features and covers a wide range of functionalities. It will be very
useful throughout the entire design process.
Local: prototype
of a single component or characteristic of the critical usability system. It
will be useful in some specific stages of the design process.
When is medical device prototyping?
Before starting...to show the concept to the board.
Starting.... to meet the initial user requirements
After starting .... to validate the evolution of user
requirements.
In the intermediate stages..... To validate system specifications
Between the intermediate and final stages .... To prepare users
or create a marketing demonstration
In the final stages ..... to explore solutions to specific
design or usability problems.
Considerations
prior to the construction of a prototype
- Depth of functionality required in the prototype
- Choice of the prototyping tool and consideration of its limitations
- Completion criteria for the iteration cycle
- Composition of the team (users, developers and others involved)
- Level of fidelity required in prototyping
- Maximum length of an iteration cycle
- Purpose of the prototype
- Ways to handle conflicts between members of the design team and consensus building.
Comments
Post a Comment