Week 7: Working on Prototype

As I was working on the prototype - I came up with an updated classes structure. The current version is available below

And - as I was coming up with game description, revisited survey questions from the video prototype - I had to change the logic a bit.

Here are my final hypothesis:

Hypothesis #1: 

Increasing game complexity in sets of 10 questions will sustain kids interest in the game and make it fun. 

Pass Criteria: A test will fail if a test participant fails to answer correctly from the very beginning until the end of the set. Thus - waiting for 10 questions to pass to assess the results would be too long, as kids get dissatisfied with continuous failure. 

Fail Criteria: Results are distributed evenly - and participants failing the first 2 questions may provide correct answer at the end of the game.

Hypothesis #2: 

On average it will take a user 3 - 5 seconds to respond a question. If it takes more than 5 seconds - a user is unlikely to provide a correct answer at all and there is a need to change the question or provide support/positive reinforcement.

Pass Criteria:

If answering a question takes longer than 5 seconds - and users do not provide correct results - the hypothesis is right.

Fail Criteria: 

If answering a question takes longer than 5 seconds - and users still provide correct results - the hypothesis is wrong. 

The main change is that I have to store game results somehow - since my analysis is purely close-ended questions. So, I decided to add the option to "Store results" to make sure I get the data I can interpret later.

Will be wrapping it up soon...