Requirements

For best results, please use Google Chrome on Mac OS X when evaluating our prototype. Large screen sizes are recommended to view all elements of the page at once.

SETistics Site

SETistics Computer Prototype

Workload Distribution

Marcel - Worked with manipulation and display of recorded statistics. Implemented command line feedback.
Pedro - Worked on general layout construction and responsiveness. Also worked to implement a back end for exporting statistics.
Alan - Responsible for most aspects of the command line. Implemented efficiency features as well as drop down menus for command input fields.

  • No labels

1 Comment

  1. Unknown User (jks@mit.edu)

    Overall: Your focus is on efficiency, and you've done a great job at building a CLI-based interface for recording volleyball statistics. Still, the most basic test of its effficiency is if *you* can keep up with a few volleyball points, recording stats on-the-fly. If you can't efficiently record stats, your users will most likely not be able to find it useful.

    • Presentation:
      • Started the presentation late.
      • Guided tour should have been better thought out, demonstrating your interface for recording a set of real volleyball shots.
      • Because it was not demonstrated on a real scenario, did not get the sense that the interface is in fact efficient, even though this has been the primary focus of your project.
    • Usability:
      • Focus of your interface is on efficiency - with that in mind, there seems to be room for improvement:
        • One letter shortcuts should be used where possible. E.g. court locations don't need h and a, shot types (b, d, v (serve), s (set), x (spike)), outcomes (d, k, e)) - note how all letters are accessible with the left hand - can use spacebar to submit.
        • Prioritize required statistics - is shot direction needed? Maybe to simplify and maintain efficiency, just record player-shottype-outcome.
        • If errors are made, might be good to chunk recorded statistics by point. E.g., spacebar could place a divider between recorded stats, to represent the end of a point.
        • If only one hand is needed for most statistics, maybe the mouse can be used to select the player from a court map - might be easier than remembering what number they are.
        • Pausing the video is a good idea, but was not implemented
      • Window resizing, tabbing, F-shorcuts are all good additions.
      • Should have louder feedback on the direction arrow (e.g. yellow, thicker line).
      • Homogenize the layout of recorded stats, and make it a bit more readable, while still matching the order of input. E.g. convert ""h5 sv h1 a2 dg"" to ""h5 | serve from 1 to 2 | dug"".
      • Aggregation for deleting multiple stats.
    • Completeness:
      • Missing the pause while typing feature.
      • No saving/caching of statistics - what if I refresh the browser? Minimal back-end would be nice.