Tuesday, November 8, 2011
Week 8: Oct 31th, 2011
Evaluation: Round 1
Early this week, Build 683 was released and a notification was sent out to the evaluators.
Throughout the week, I went on a Caribbean Quest looking for bugs. Not many unknown bugs were found, to my pleasant surprise.
However, the Cog2 meeting on Friday revealed that there was has not been much effort on the Psych department side. Because of this, we decided to delay the close date for bug reports until Tuesday, which would allow them the weekend to investigate further.
Apart from this setback, things are moving forward with the planning of the upcoming evaluations (round 2 - heuristic evaluation). We will be arranging a meeting with Angela, myself and the 2 members of the psychology department to review their objectives and target audience. The goal of this meeting is to focus in on the 'goal' of the games and schedule a time where these professionals can devote a few hours to conduct a structured evaluation of the educational content of the game. My hope is to enable communication, so that simple/cheap usability evaluations can be performed often throughout the iterative development process.
Upcoming evaluations
After reading some further work from Hasiah Mohamed @ Omar and Azizah Jaafar, I have decided to develop a portal in which all expert evaluators can use to conduct their evaluations. Hasiah Mohamed @ Omar and Azizah Jaafar had discussed an extensive system where the surrogate and real users enter their evaluations as input, and through some AHP algorithm, the administration is able to deduce issue ratings, statistics and export multiple reports.
In our case, there are not enough resources to develop such a complex and robust system. However, it may be possible to build a similar system by utilizing the tools that are already being used by the team (Google tools). This type to 'portal' would be a cheap way to enable communication between both departments and facilitate iterative usability evaluations.
I will begin analysis of the feasibility and design of such a system over the weekend.
Early this week, Build 683 was released and a notification was sent out to the evaluators.
Throughout the week, I went on a Caribbean Quest looking for bugs. Not many unknown bugs were found, to my pleasant surprise.
However, the Cog2 meeting on Friday revealed that there was has not been much effort on the Psych department side. Because of this, we decided to delay the close date for bug reports until Tuesday, which would allow them the weekend to investigate further.
Apart from this setback, things are moving forward with the planning of the upcoming evaluations (round 2 - heuristic evaluation). We will be arranging a meeting with Angela, myself and the 2 members of the psychology department to review their objectives and target audience. The goal of this meeting is to focus in on the 'goal' of the games and schedule a time where these professionals can devote a few hours to conduct a structured evaluation of the educational content of the game. My hope is to enable communication, so that simple/cheap usability evaluations can be performed often throughout the iterative development process.
Upcoming evaluations
After reading some further work from Hasiah Mohamed @ Omar and Azizah Jaafar, I have decided to develop a portal in which all expert evaluators can use to conduct their evaluations. Hasiah Mohamed @ Omar and Azizah Jaafar had discussed an extensive system where the surrogate and real users enter their evaluations as input, and through some AHP algorithm, the administration is able to deduce issue ratings, statistics and export multiple reports.
In our case, there are not enough resources to develop such a complex and robust system. However, it may be possible to build a similar system by utilizing the tools that are already being used by the team (Google tools). This type to 'portal' would be a cheap way to enable communication between both departments and facilitate iterative usability evaluations.
I will begin analysis of the feasibility and design of such a system over the weekend.
Subscribe to:
Posts (Atom)