Artifact: User-Interface Prototype










var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_qwxC8N7YEdmjRZts2c4ZjQ", "{0F994CCE-2B28-414A-9D31-DA23C13B95D4}", "{3DF10D00-8C80-4429-92B8-C6A221F0F90C}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_QV4x0AISEdqTna4sZVFRow", "_kjFBYN7HEdm8G6yT7-Wdqw", "{3DF10D00-8C80-4429-92B8-C6A221F0F90C}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qwxC8N7YEdmjRZts2c4ZjQ", "{0F994CCE-2B28-414A-9D31-DA23C13B95D4}", "{3DF10D00-8C80-4429-92B8-C6A221F0F90C}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_kjFBYN7HEdm8G6yT7-Wdqw", "{3DF10D00-8C80-4429-92B8-C6A221F0F90C}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_3lZjkCxqEdqYV4MWf8PiCw", "{3DF10D00-8C80-4429-92B8-C6A221F0F90C}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Artifact: User-Interface Prototype















This artifact is an example of the user interface. It is used to explore and/or validate the user-interface design.


Domains: Analysis and Design
Work Product Kinds: Concept






Purpose



The following roles use the user-interface prototype: user-interface designers, to explore and/or validate the user-interface design before too much is invested in it requirements specifiers, to understand the user interface for a Use Case system analysts, to understand how the user interface impacts the analysis of the system designers, to understand how the user interface impacts and what it requires from the "inside" of the system managers, to plan development and testing activities User-Interface Prototypes can be used to explore an achievable and suitable user-interface design that fulfills the requirements, helping to close the gap between what is required (expressed through requirements elicitation) and what is feasible. The main purpose of creating a user-interface prototype is to be able to "test out" the user-interface design, including its usability before the real development starts. This way, you can ensure that you are building the right system, before you spend too much time and resources on development.



Relationships



RolesResponsible:



User-Interface Designer


Modified By:



User-Interface Designer





TasksInput To:



Class Design


Detail the Software Requirements


Identify Test Ideas


Review the Design


Output From:



Prototype the User-Interface





Process Usage


Analysis & Design
 > 
Design the Database
 > 
User-Interface Prototype


Analysis & Design
 > 
Analyze Behavior
 > 
User-Interface Prototype


Analysis & Design
 > 
Design Components
 > 
User-Interface Prototype


Requirements
 > 
Refine the System Definition
 > 
User-Interface Prototype


Test
 > 
Verify Test Approach
 > 
User-Interface Prototype


Test
 > 
Improve Test Assets
 > 
User-Interface Prototype


Test
 > 
Define Evaluation Mission
 > 
User-Interface Prototype


Test
 > 
Test and Evaluate
 > 
User-Interface Prototype






Tailoring



Representation Options User-Interface Prototypes may be formal or informal, executable or non-executable, low fidelity or high-fidelity prototypes. For example, a User-Interface Prototype may range from a series of pictures represent screen captures of some interactive HTML pages. The format the UI prototype takes is not the issue. What is important to keep in mind is the purpose of the User-Interface Prototype (to explore and/or validate a user-interface design), and what skills are required to produce the prototype (a User-Interface Prototype requires some user-interface design skills). Decide whether a prototype is suitable for your project.  Decide on how much of the user interface to prototype, and the depth and realism of any interactivity.  Decide whether the prototype is purely throwaway, or whether some aspects are intended to evolve into the end product. Keep in mind that in order to achieve the goal of early testing of the user interface, the prototype must be significantly cheaper to develop than the real system, while having enough capabilities to be able to support a meaningful use test.



More Information



Concepts


Prototypes








©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();