GR1 - Bracketracker
Stephen Chang, Sarah Han, Samvaran Sharma
User analysis
There are a few personas who represent the main users of our product. To create each persona we have interviewed people who perform user class function:
- the Manager
- the Challenger
- Manager/Challenger
Task analysis
There are a few main tasks involved with the Bracketracker. These tasks include:
- Create a tournament
- Update the tournament
- View your tournament(s)
- Searching for and Joining tournament(s)
- Manage a tournament
Create a tournament:
Goal: To create a new tournament among friends & create a new bracket.
Preconditions:
- type of tournament
Location:
- on website
Frequency of use:
- once
How Learned:
- by experimenting
Possible Errors:
- non-unique name
Update the tournament:
Goal: When a match has been completed the player need to update the scoreboard
Preconditions:
- tournament name
- score
- which game/match
Location:
- on website
Frequency of use:
- multiple times a day
Time Constraints:
- within the time-frame of the tournament
How Learned: - by doing or by watching others
Possible Errors:
- update wrong game
- update the wrong score
Who Else is Involved:
- opponent
Searching for and Joining tournament(s):
Goal: To join an existing tournament.
Preconditions:
- tournament name
- if tournament is joinable
Location:
- on website
Frequency of use:
- once per tournament
Time Constraints: - within the time-frame of the tournament
How Learned: - by doing or by watching others
Possible Errors:
- wrong tournament name
- not permitted to join
Who Else is Involved:
- nobody else
View your tournament:
Goal: To assess the state of the tournament
Subgoals:
- view leaderboard
- view scoreboard
- view current bracket
- view any notifications
Pre-conditions:
- tournament name
Frequency of use:
- multiple times per day
How Learned: - by doing or by watching others
Possible Errors:
- view wrong tournament
Who Else is Involved:
- nobody else
Manage a tournament:
Goal: To ensure the tournament continues in a timely manner.
Pre-conditions:
- desired change
Frequency of use:
- as many as needed
How Learned: - by doing or by watching others
Time scale:
- within the scope of the tournament
Possible Errors: - change the wrong feature
- change the wrong tournament
Who Else is Involved:
- nobody else