Other Group Evals and This Week's Group Meeting

Brent J. Dahlen (dahlen@cs.umn.edu)
Tue, 3 Mar 1998 16:27:30 -0600 (CST)

Date: Tue, 3 Mar 1998 16:27:30 -0600 (CST)
From: "Brent J. Dahlen" <dahlen@cs.umn.edu>
To: "Sun 1:00 Group 7" <ameet@wonderwonks.com>, asbu0003@itlabs.umn.edu,
Subject: Other Group Evals and This Week's Group Meeting
Message-Id: <Pine.GSO.3.95q.980303161204.12098A-100000@asimov.cs.umn.edu>

Hi all,

*Individual Critiques of Other System*

Several of you have submitted critiques on the "other group"
formatted in all sorts of different application types. For
simplicity (and to save me time!) please resubmit these as
plain text. (If you've already sent me a copy as text, then
PLEASE don't resend it.) Perhaps an even better solution for
the few of you who have sent your critiques as Word97 files or
others--print out a hardcopy and give it to me during your
meeting this week.

*This Week*

The following needs to be done by your group meeting this week:

- Group Heuristic Eval (if not already done). Merge the individual
heuristic papers, listing problems and solutions. Take care to
list duplicate problems only once and come up with a solution
that your whole group can agree upon. Reorganize as necessary.

- Group User Evaluations:
o Based on Observations. List problems you witnessed while
testing users on your system. Give group solutions for
o Based on Other Group's Critiques. Merge and list problems
the other group members have individually written down and
then come up with solutions to these as a group. State
whether you are using the other group member's solution
or one of your own.

- Summary/Prioritized Problem List. Provide a summary of what your
group has learned by going through the walkthrough, heuristic,
and user testing evaluations. Talk about the impact each has
had on your design and what you have learned in general about
interface testing/evaluation methods. Finally, list in order
those problems you a) have implemented solutions for, b) will
implement solutions for in the coming week, and c) won't be
able to implement solutions for. Remember to identify your
solutions in the prioritized problem list. (Just list them
as problem/solution pairs--no further analysis is necessary.)