iCoxBox GR1: Project Analysis

Andres Lopez-Pineda, Jesse Riemer, Taylor Gilbert

User Analysis

Rower

  • Physical limitation: No hands available to use interface
  • Motivation: Interested in retrieving relevant information, quickly
  • Environment: Will be used on a boat while rowing

Coxen

  • Physical limitation: No hands during race, since they will be needed for steering
  • Motivation: Interested in retrieving relevant information and saving it for review
  • Environment: Will be used on a boat while steering and communicating with rowers

Coach

  • Motivation: Interested in easily comparing data from multiple races
  • Environment: In a chase boat, so cannot directly interact with other boat, rowers, or coxen.  

    Our analysis is based primarily on interviews with a rower, coxen, and crew coach. In our interviews, they described the constraints on the use of an app like this and provided feedback as to what data is most important (this determined what we decided should be front and center and what can be in another tab on the interface).

Task Analysis

Access boat-related data in real-time   

  • Goal: To monitor the status of the boat in order to communicate that to the rowers
  • Precondition: iPhone is secured to boat, in view of the user
  • Subtasks:
    • Once started, view all relevant information with minimal interaction
      • View pre-written notes
      • View ghost trail of current path and desired path
      • View stroke + accelerometer data
    • Toggle between on-boat and coach modes
      • If in coach mode, use a button to count strokes

Store race data

  • Goal: Save a set of data related to a race
  • Subtasks:
    • Set a ghost route if desired
    • Input notes to be viewed during the race
    • Decide if audio should be recorded
    • Press button to start race
    • View data (as in the task above) during the race
    • View timer for the race
    • Press button to end race
    • Have the data automatically be stored for later use
    • Change the name of the race afterwards

Replay race data

  • Goal: To be able to review race data at a later date
  • Precondition: the user has stored at least one set of race data
  • Subtasks:
    • Choose desired race out of a list of past races
    • View race data at any point in the race, with the different sets of data (stroke rate, timer, audio, etc) time-synced
    • Play/Pause/Rewind playback

Domain Analysis:

  • No labels

1 Comment

  1. Mason Tang

    • Could use more detail about your user classes, what about their technical background? What specific motivations do they have?
    • Will this tool be used after a race as well?
    • Task analysis is too concrete and bound to your mental model of the interface. "Press a button", "toggle mode" are all interface specific actions.
    • Missing coach-related tasks from task analysis?
    • Domain analysis should include the user roles from your user analysis