H1 | H2 | H3 | H4

Homework 1: Distilling Design Implications
Due date: See class schedule

Note: This is a two-person assignment. Find a partner from the class who is NOT on your project team. You will complete the homework together. Both your names need to appear on the assignment, but only one of you needs to submit the assignment (in PDF format, via canvas). Start each A-I table on a new page. Both of you will receive the same grade for the assignment.

Overview: Two of the important early steps in evidence-based design is to describe the user(s) and to define the context in which the users are situated. Then, crucially, it is important to distill design implications from the context and the user description. These design implications are constraints or requirements that fall out of the context/user findings. Subsequently, once those design implications are identified, the task is more fully detailed and documented, and as you head toward an actual design, the design implications need to get instantiated in design implementations.

In this assignment, you will get practice in identifying user attributes, and then distilling implications from those user attributes. Your task is as follows: for each of the following combinations of user type and context, create an Attribute-Implication table. The A-I table should include (at least) the following categories of user attributes: perception; cognition; (physical) movement; motivations; social attachments. You can add any other categories you see as potentially instructive.

For each category, identify at least three (3) attributes or aspects or descriptions that is applicable for that user class, in that context.

Then, complete each table row with at least one design implication. These design implications should be general enough that they cover a broad range of possible actual implementations, but specific enough that the design implication could be turned into a testable/verifiable design requirement, as part of a contract.

Consider the following example of a partially-completed Attribute-Implication table for the user-context combination of "adult underwater (scuba diving)". Note that a fully completed table would have many attributes for each category, and often many implications for each attribute.

A-I Table: adult underwater (scuba diving)
Category Attribute Implication
Perception Restricted field of view (mask) Do not require peripheral vision
Perception Muffled/diminished hearing Avoid depending on audio signals
Cognition Reduced memory (cold water) Use recognition rather than recall
Cognition Possible distraction (looking at fish) Assess and manage attention
Movement Limited hand dexterity (gloves; cold) Make controls operable with gloves
Movement Variable orientation (hard to remain stationary, neutrally bouyant) Move system with user
Motivations Anxious or nervous (under water!) Makes processes simple and clear
Social Dive buddy present Design may involve two individuals
Social Dive buddy present Enable user time to check on buddy regularly

User-Context Combinations:

  1. Teacher in highschool classroom
  2. Police officer inside patrol car (driver seat)
  3. Adult commuter on bicycle
  4. Child wheelchair user at a stadium
  5. Older adult (65+ years old) in commercial/restaurant kitchen