Usability Process 1. Specify stakeholder and user requirements
|
Not achieved
Partially achieved
Fully achieved
|
Description: Identify and describe the purpose of the system, this is, the objective(s) that the user wants to achieve using the system.
Example of work product: Purpose(s) of the system.
Example of techniques: Survey, brainstorming, interview, observation.
|
|
Not achieved
Partially achieved
Fully achieved
|
Description: Identify the stakeholder's requirements regarding the behavior and performance of the system. The requirements cover each aspect of the system related to its use and its interface in a context of use.
Example of work product: System performance and behavior requirements desired by the user.
Example of techniques: Survey, brainstorming, interview, observation.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Define an explicitly statement for each usability requirements, regarding its effectiveness, efficiency and user satisfaction based on the context of use analysis. The statements should be measurable objectives.
Example of work product: A list of usability requirements.
Example of techniques: Benchmarking with concurrent systems, synchronic analyzes formal work analyses.
|
Usability Process 2. Understand and specify the context of use
|
Not achieved
Partially achieved
Fully achieved
|
Description: Describe the tasks the users need perform in the system in order to achieve their goals.
Example of work product: A list of user tasks and their characteristics and a list of use cases.
Example of techniques: Survey, interview, observation, formal work analysis, brainstorming with user's task, user's tasks modeling.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Identify relevant characteristics of the users, such as knowledge about the system domain, degree of literacy, physical capabilities, level of experience with the tasks and with the device he will use to interact with the system, motivations in using the system, etc.
Example of work product: User information, user profile, personas.
Example of techniques: Survey, interview, observation.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Identify relevant social and organizational milieu, management structure, communications and organizational practices in the environment in which the system will be used.
Example of work product: Description of social and organizational environment, management structure, communications and organizational practices or legislation.
Example of techniques: Survey, observation, interview.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Identify relevant characteristics of the device with which the users will directly interact, such as memory and process capacity, ways of input and output data, screen size, etc.
Example of work product: Analysis of the device characteristics.
Example of techniques: Review platform documentation.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Identify relevant characteristics of the location, workplace equipment and ambient conditions and its implications for the system design, such as lighting, noise levels, vibration, heat, hazards, dimensions of working and living space.
Example of work product: Description of physical environment characteristics
Example of techniques:Survey, observation, interview.
|
Usability Process 3. Produce design solutions
|
Not achieved
Partially achieved
Fully achieved
|
Description: Analyze the user's tasks in terms of alternative navigation pathways and flowcharts and identifying the main system screens and constraints.
Example of work product: Identification of main system screens, flowchart task, navigation diagram, task hierarchy.
Example of techniques: Conceptual model design, wireframes development, navigation definition, task hierarchy analysis, information architecture definition, card sorting.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Analyze a range of design options for each aspect of the system related to its use and its effect on stakeholders, such as definition of system controls, location and format of display components, use of colors, terminology, fonts, and wording of messages.
Example of work product: Wireframe development, sketches development, storyboarding, use case analysis.
Example of techniques: Analysis of design options.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Apply existing usability knowledge, such as stakeholder requirements, information about the context of use, international standards, usability good practice and style guides to the design of the system and is used to select the appropriate alternatives of design.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Specify the design of all the user-related components of the system. This specification is a description of how the components and the system will be used, such as the kind of systems controls will be used, location and format of display components, colors, terminology, fonts, wording of messages).
Example of work product: Wireframes, sketches, specification of system components behavior, storyboards.
Example of techniques:WWireframe and sketch development, storyboarding.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Refine design through the development of high-fidelity prototypes of all aspect of the system related to its use and its interface.
Example of work product:Definition of the “look and feel”, high fidelity prototypes, and detailed user interface design specification.
Example of techniques: Prototype development.
|
Usability Process 4. Evaluate designs against requirements
|
Not achieved
Partially achieved
Fully achieved
|
Description: Prepare and defined all arrangements necessary to evaluate the prototype or the system, such as definition of which evaluation method will be used, who will be the assessor, place, scripts, questionnaires, cameras and etc.
Example of techniques:Prepare usability evaluation necessary materials, select participants.
Test script, test case, evaluation goals, metrics to be collected.
|
Not achieved
Partially achieved
Fully achieved
|
Description: Prototypes are evaluated against usability knowledge, style guides, standards, guidelines in order to find usability problems and verify if the required good practices has been followed.
Example of work product: List of recommendation changes, list of usability problems found, violated heuristics, degree of severity of the usability problem.
Example of techniques: Usability test with users, heuristic evaluation, cognitive walkthrough, key level stroke model evaluation.
|
Not achieved
Partially achieved
Fully achieved
|
Description: System is evaluated to ensure that it meets the requirements of the users, the tasks and the environment, as defined in its specification.
Example of work product: A pass/fail decision regarding each requirement
Example of techniques: Usability test with users.
|
Contextual information
|
|
|
|
 
 | 
 | 
 | 
 | 
  
|
|
|
  |
  |
|
SUPPORT
|
|