|
 Perform these activities to learn about the users and the environments in which the new application or website will be used. The insights you gain will inform requirements and content decisions, as well as contribute to improved user interface and creative design. Use the links below for an overview. For details about a role, activity, or artifact in the diagram, click on its icon. More detail: Purpose - How to Staff
|
|
| Purpose |
|
The purpose of this workflow detail is to describe the context in which the system or website will be used (i.e., its context of use). Describe the context of use in terms of the following:
- Characteristics of intended users. Relevant characteristics include knowledge, skills, experiences, education, training, physical and psychological attributes, habits, behavior patterns, cultural preferences, and capabilities (including impairments/disabilities).
- User Tasks (scenario level). Identify the goals of each task users perform and their overall goal for using the system. Task characteristics affecting usability (frequency, dependency, and duration) should be described. Consider legal aspects when applicable.
- Environmental aspects. Describe the environment in which the users will use the system. This includes hardware, software, and supplemental materials. In most cases, a set of products (and their characteristics) should be sufficient.
Understanding the context of use guides early requirements and user interface design decisions, providing a basis for later usability evaluations.
|
| How to Staff |
|
The Role: User Researcher and the Role: Requirements Analyst are responsible for investigating users and their potential needs. The User Researcher often uses human-computer interaction (HCI) techniques when talking with, observing, or surveying end users. HCI techniques may include using focus groups, contextual inquiry, and personas.
The Role: Requirements Analyst works with the User Researcher to understand the users' needs because this is a critical requirements source. The Requirements Analyst has primary responsibility for the Artifact: Actor Catalog and Artifact: Use Case Model, which include information about human users and systems that interact with the application under development. The Role: Usability Evaluator may participate in the research or use its results when planning usability tests.
Depending on the breadth and depth of user research needed, highly skilled people fulfilling the User Researcher role may be able to also fulfill a Requirements Analyst, Information Architect, or Usability Evaluator role during the project.
|
|
|