... | @@ -404,3 +404,49 @@ Other than that it worked ok from what he could tell. |
... | @@ -404,3 +404,49 @@ Other than that it worked ok from what he could tell. |
|
- Ability to add black or white while setting up a match
|
|
- Ability to add black or white while setting up a match
|
|
|
|
|
|
- not only get scores but also matches played
|
|
- not only get scores but also matches played
|
|
|
|
|
|
|
|
User test on final product
|
|
|
|
User 1
|
|
|
|
Info about user: a 21-year-old art student. No knowledge about chess, not very proficient with data technology.
|
|
|
|
The user in a place without Wi-Fi but were sent screenshots of the program and texted back their input.
|
|
|
|
Menu
|
|
|
|
User is initially confused by the program; does not understand how they are supposed to add input. First attempts to write complete sentences, which works for the first prompts due to the program only checking the first letter typed.
|
|
|
|
|
|
|
|
Create Tournament
|
|
|
|
Is confused by what “tables” and “rounds” mean due to lack of knowledge about chess, was frustrated that the program did not explain the terms or the fact that every table needs two players.
|
|
|
|
|
|
|
|
Changes made based on user study
|
|
|
|
Added a prompt when the program first opens that specifies all commands are single character.
|
|
|
|
|
|
|
|
Potential changes based on user study
|
|
|
|
While this user requested information about how chess works and an explanation of terminology used in the program, the team believes most people who organize chess tournaments already possess this knowledge and would not benefit from this, and therefore that adding it to the program would not be an effective use of time.
|
|
|
|
|
|
|
|
User 2
|
|
|
|
Info about user: a 19-year-old programming student. Basic knowledge of chess, proficient with computers.
|
|
|
|
|
|
|
|
Add player
|
|
|
|
User finds it overly complicated having to give the “add player” prompt in the menu for every player, especially considering you need a set number of players based on the number of tables specified at tournament creation. User suggests having it loop add player after specifying number of tables instead of going through the menu first.
|
|
|
|
|
|
|
|
General
|
|
|
|
Program is clean and easy to use, user finds the program to be intuitive outside of the issue raised in the previous point.
|
|
|
|
|
|
|
|
Potential changes based on user study
|
|
|
|
The change to the add player function would probably benefit the program, though it would complicate the “delete player” function and require a significant amount of work. The program works fine as is, so the team believes the team needed to add this feature outweighs the benefit.
|
|
|
|
|
|
|
|
User 3
|
|
|
|
User is a 21-year-old programming student. Fairly knowledgeable about chess but does not play actively, proficient with computers.
|
|
|
|
|
|
|
|
Add players
|
|
|
|
Finds it intuitive to use but thinks it should automatically stop you from adding more players if there are enough.
|
|
|
|
|
|
|
|
General
|
|
|
|
It is possible to have more rounds than the number of tables allow, which causes the program to crash upon attempting to matchmake for the next round only to discover all players have met each other.
|
|
|
|
|
|
|
|
Changes based on user study
|
|
|
|
Both features the user brings up are quite simple to add and gives a significant increase to the quality of the user’s experience, making the program seem finished by diminishing the room for error’s caused by people, and as such the team added this features.
|
|
|
|
|
|
|
|
User 4
|
|
|
|
User is a 20-year-old programming student with limited chess knowledge but proficient with computers.
|
|
|
|
|
|
|
|
General
|
|
|
|
“The program is simple to use and very smooth. There is no problems or bugs, like having to enter the input twice to make it work. Yes. Overall, if I ever had a chess tournament I would use this program.” |