Technique - Prototyping

Proof of Principle or Proof of Concept Prototype

A model created to validate the design of a system without modelling the appearance, materials used in the creation of work, or processes/workflows ultimately used by the stakeholders.

Element: Prototyping Approach - Throw-Away

Prototypes are generated with simple tools Throw-away (such as paper and pencil, a whiteboard, or software) to serve the goal of uncovering and clarifying requirements. The prototype may be updated or evolve during the course of discussion and development, but does not become workable code or get maintained as a deliverable once the final system or process is implemented.

Description

Prototyping is a proven method for product design. It works by providing an early model of the final result, known as a prototype. Prototyping is used to identify both missing or improperly specified requirements and unsubstantiated assumptions by demonstrating what the product looks like and how it acts in the early stages of design.

Purpose

Prototyping is used to elicit and validate stakeholder needs through an iterative process that creates a model or design of requirements

Simulation

Used to demonstrate solutions or components of a solution. It may test various processes, scenarios, business rules, data, and inputs.

Form Study Prototype

Used to explore the basic size, look, and feel of a product that will be manufactured, without creating actual functionality.

Storyboarding

Used to visually and textually detail the sequence of activities by summing up different user interactions with the solution or enterprise.

Paper Prototyping

Uses paper and pencil to draft an interface or process

Element: Prototyping Approach - Evolutionary or Functional

prototypes are created to extend initial requirements into a functioning solution as requirements are further defined through stakeholder use. This approach produces a working solution and usually requires a specialized prototyping tool or language

Limitations

• If the prototype is deeply elaborate and detailed, stakeholders may develop unrealistic expectations for the final solution. • Stakeholders may focus on the design specifications of the solution rather than the requirements that any solution must address.

Strengths

• Provides a visual representation for the future state. • Allows for stakeholders to provide input and feedback early in the design process.

Functional Prototype

A model created to test software functionality, qualities of the system for the user (for example, appearance), and workflow. It is also referred to as a working model and is used both to simulate business processes and business rules and to evaluate software function calls.

Usability Prototype

A product model created to test Usability Prototype how the end user interacts with the system without including any of the properties (for example, appearance, configuration).

Visual Prototype

A product model created to test the visual aspects of the solution without modelling the complete functionality.

Workflow Modelling

Depicts a sequence of operations that are performed and usually focuses solely on the human aspect.