Human Interface Prototype

Definition

Human Interface Prototype: the design work product that is a prototype of an application’s human interfaces

The typical objectives of a human interface prototype are to:

The typical benefits of a human interface prototype are to:

The typical contents of a human interface prototype are:

Software Prototypes:
- Low-Fidelity Software Prototype (a.k.a., Storyboard):
  - White-board or paper prototype.
  - Site navigation diagram
  - For each screen or webpage, the following elements:
    - Name
    - Responsibility
    - Content
    - Input/Output fields
    - Commands
- Medium-Fidelity Software Prototype (a.k.a., Wireframe):
  - White-board, paper prototype, or wireframe screen mockup
  - Updated site navigation diagram
  - For each screen or webpage:
    - Elements
    - Basic layout
- High-Fidelity Software Prototype:
  - Software prototype
  - Site map webpage
  - For each screen or webpage:
    - Elements including real content
    - Layout
    - Colors, images, and digital branding
    - But no integration with domain and database layers.
Hardware Prototypes:
- Low-Fidelity Hardware Prototype:
  - Empty cardboard mockup
  - Paper dials, switches, displays, etc.
- Medium-Fidelity Hardware Prototype:
  - Empty box
  - Nonfunctioning dials, switches, displays, etc.
- High-Fidelity Hardware Prototype:
  - Breadboard box
  - Semifunctioning dials, switches, displays, etc.

The typical stakeholders of a human interface prototype are:

A human inteface prototype is typically developed during the following phases:

A human interface prototype can typically be started if the following preconditions hold:

The typical inputs to a human interface prototype include:

The human interface prototype can exist in multiple forms that eventually evolve into the deliverable user interfaces.
The human interface prototype can be used to elicit user interface and usability requirements.
A complete human interface prototype can look real enough to mislead customer representatives into thinking that the majority of the appliation is complete. The main work still remains in the transaction, domain, and database layers. Control customer and user expectations.

A human interface prototype is typically constrained by the following conventions: