GR4 - Computer Prototype

Stephen Chang, Sarah Han, Samvaran Sharma

Platform and Software Requirements

This works best in Chrome, but should work in other modern browsers too. 

Source code and all files are downloadable here (as of build at 11:59am, 4/15): http://samvaran.scripts.mit.edu/bracketracker.zip

Instructions

View the site at BrackeTracker

In order to test out the site, we suggest running through the tasks set forth in the GR3 Paper Prototyping, which encompasses the scenarios laid out in GR2. 

In particular, in order to see the "join tournament" page - try searching "Office Ping Pong" and clicking on the first result that shows up. 

Shallow Features

Feature

Notes

Login

Not Implemented

Settings,Friends,Profile Pages

Not implemented. These weren't integral parts of the site.  The social aspect of inviting friends to join the website is not the focus of this site.

Sending/Receiving Email Invites

Not Implemented.  Not integral to functionality of website.

Viewing Tournament Status

Many of the tournaments are static pixel images.  Only Round Robin Tournament is functional.

Updating single and double elimination tournaments

The process of updating single and double elimination tournaments is similar to updating a round robin tournament.  We felt that updating a round robin tournament is indicative of the entire process.

Password Protected Tournaments

All the tournaments you can join are not password protected.  By clicking on a tournament that you cannot join, you can see the Password prompt.

  • No labels

4 Comments

  1. Unknown User (leibatt@mit.edu)

    Hi! Cool concept. Here is my feedback: LeilaniBattleHW2BrackeTracker.pdf

    --Leilani

  2. Phillip W Mercer

    bracketracker_eval.pdf

  3. Unknown User (alexwang@mit.edu)

    Hi BrackeTracker. Good job! I hope my comments help.

     BrackeTracker Heuristic Evaluation.pdf

  4. Sacha Zyto

    Wiki presentation: nice and clear, and good explaination of shallow vs. deep parts
    Fidelity: very good: looks like a final implemantation, and covers the scenarios
    Usability: if user isn't a tounament not an admin, the design should make it clear what actions are allowed and what actions aren't: for example user can't edit the score of a mathc where s/he sisn't participate, but that's not visible enough.
    - There's a lot of available screen real estate: homepage should have a 1 sentence desciption of what the site does.
    Overall: Very good. Cool  aesthetic touches (color scheme, logo)