• Created by Unknown User (mpolanco@mit.edu), last modified by Unknown User (abw333@mit.edu) on Apr 20, 2013 14:38

Project Home

Requirements

For best results, please use Google Chrome on Mac OS X when evaluating our prototype. Large screen sizes should be used to view it so that all elements fit on the page.

Instructions

SETistics Computer Prototype

Limitations

  • Previous commands can not be deleted from the stack yet.
  • Visual icons for each field of a command is depicted as the same picture for each individual field. This will later be implemented such that each image corresponds to a specific input option.
  • The live video feed is currently substituted with a feed from a previous match. 
  • Automatic pausing and playing of the video feed is not implemented. It will pause when the user is entering a statistic and it will resume when the user is done.
  • No labels

5 Comments

  1. Unknown User (chenix@mit.edu)

    Great job, guys! My heuristic evaluation here: heuristic evaluation for setistics.pdf

  2. Unknown User (lsyang@mit.edu)

    Good job guys, please find my heuristic evaluation here. Heuristic evaluation_Shiyang Liu.pdf

  3. Xingyi Li

    Cool concept and prototype! Here is my heuristic evaluation HW2.pdf

  4. Unknown User (jks@mit.edu)

    • Wiki presentation: 
      • About this comment: "Visual icons for each field of a command is depicted as the same picture for each individual field..." - I don't see any visual icons for the shot input fields.
    • Fidelity: 
      • Great initial computer prototype, which seems to cover the breadth required for recording individual volleyball statistics, although it's unclear whether the interface will be efficient enough to record stats in real-time.
      • Lacking a bit of fidelity in look:
        • You refer to icons in your Wiki write-up, but none are visible.
        • The court diagram looks like a low-res screenshot.
    • Usability: 
      • Most important: it's time to be concrete about what the interface should enable. Does the user have to record every shot in the game, or just the decisive ones that end in a point one way or the other? If it's the former, then you need to focus on the most efficient way to enter statistics. To that end...
      • Drop down menus are pretty useless, since expert users will enter by hand and they get in the way of tabbing from input-to-input. Instead, display a quick example, or enable autocomplete.
      • Redundancy between player # and shot from field. Is the 'shot from' field supposed to be player numbers, or labeled areas of the court? Unclear.
      • Options for 'result' are confusing. When is a 'dig'-type shot not 'dug'? Should this just be point or not point?
      • Pausing the video to enter statistics doesn't seem like an efficient enough solution. There's probably between 5-10 shots per point, and recording each one takes at least a couple seconds. It will be easy to fall behind. Is there an easier way to keep up with the point? E.g., just click on each player that touches the ball, assume that digs occur when the ball goes from side to side, and clarify blocks or kills at the end of a point.
    • Suggestions going forward:
      • Narrow your focus on recording stats only for YOUR team, unless that renders the application completely useless, based on your needfinding.
      • A way to save / export statistics.

  5. Unknown User (rnaphtal@mit.edu)

    Apologies on this being late. Good work!

    SETisticsHW2.pdf