|
General Notes:
The idea of this phase is
(a) to undertake a heuristic evaluation
of another team's Phase 2.2 prototype, and
(b) to design of a user study around that prototype.
I will let you know
which team's Phase 2.2 you are evaluating,
as well as their contact information,
on Slack in your team channel.
Note that this will not be bidirectional, so you will not be evaluating
the Phase 2 of the team that is evaluating your Phase 2.
The contact person is required to provide the other team with
their Phase 2.2 interactive prototype, the task sceanrios
document, and any necessary directions on how to start the
prototype.
Overview:
The immediate purpose of the evaluation sub-phase of this project
is to give you experience at:
- performing a heuristic evaluation of a prototype with a team
- designing a user study (even though there will be no execution of it)
In addition to turning it in to us on ELMS, your group will also deliver
your report to the team whose Phase 2.2 you are using for your Phase 3.
However, your heuristic evaluation and usability study design (and report)
will be
used to determine your Phase 3 grade. They will not be used
to alter the other team's Phase 2.2 grade. They will, however, be
very useful to the team to better consider their design thinking and
approaches.
For Phase 3 you will need to provide us with several things,
all submitted as a PDF.
- your team members need to undertake a heuristic evaluation
of the prototype provided to you by the other team; this will
require each individual on the team undertaking an evaluation
(the first section of the PDF),
and then the team coming together (I suggest you do this in
a Zoom or other video chat meeting) to combine their findings
into a single report (the second section of the PDF)
- your team will design a user study, providing
us with a detailed description of the plan, complete
with techniques, scripts, etc. and a consent form
-
this semester for social distancing reasons you will then only
"pilot" it online "on" one of the members of your team and
describe that experience from both sides,
reflecting on things like what worked and what didn't in that pilot
(the third section of the PDF)
For the heuristic evaluation, the members of your team will undertake the
role of HCI experts brought in to review a prototype. Because of the
economy of these methods, you are expected to be able to apply them in
your actual work practices. The other team can (and should) provide you
with a list of tasks their prototype supports, but your evaluation can
also address things such as any in the horizontal levels not mentioned
in their tasks if you see them as common tasks or vertical aspects that
you can tell aren't in the current design but you feel need to be.
Recall that an individual heuristic evaluation entry contains:
* a brief description of the usability problem
* the primary heuristic violated (NOTE: That means ONE)
* a severity level for the problem
* a suggestion of an approach to fix it
and that for a full team-based heuristic evaluation, the individual
members create entries, then work as a team to discuss and consolidate
their individual lists into a team report which also contains such
entries. Please realize that the team report is NOT just a concatenation
of the individual lists with duplicates removed,
and that it is important for the combined heuristic report
to read as one coherent report.
The methods used in the usability study you design can include strict
observation, think-aloud, constructive interaction, questionnaires,
and interviews. Your team needs to determine the techniques it feels
will be best used for the user study of the project you are assigned,
but the expectation is a mixture of methods.
The "Who did what" report and salary information
is to be turned in on the same day as Phase 3 is due and will have
its own ELMS entry.
This is likely to be a one to two page summary of who in the
group did what. For each person, explain what portions of the project
they worked on, what they wrote,
portions of code,
documents, etc. This
is a public document that you must all work to agree upon.
This will have a salary section and aim to be forthright.
Grading Note
The elements of this phase will be worth 8 of the 35
percentage points that the team project makes of the
semester grade.
Updates
If any updates to the description are required, they will
be announced on places like Slack.
There have been a few questions about the heuristic evaluation report
here in Phase 3.
Part of a report is the combined/merged collection of fully-formed
heuristics with care taken that it doesn't look like four people's
individual entries tacked together.
A coherent team report would do things such as group issues by heuristic
category, and present things with more impact/priority earlier with that.
There should be something like an "executive summary" either at the start
of the whole report or ahead of each sub-section.
|