Use cases can help a lot both when creating and evaluating a design. The usability expert is supposed to know as much as possible of the application context while performing the heuristic evaulation.
Wikipedia explains it better than me: "Often the heuristic evaluation is conducted in the context of use cases (typical user tasks), to provide feedback to the developers on the extent to which the interface is likely to be compatible with the intended users’ needs and preferences." http://en.wikipedia.org/wiki/Heuristic_evaluation I tried to make an informal evaluation on the mockup, and I couldn't ascertain which different data flows were supposed to be performed on the dialog. I can't say whether the panels have a good or bad structure without knowing which primary task the user should accomplish using them. Maybe the design is good for some basic tasks, and fails in a terrible way for another one. I think some user cases were already mentioned in this thread before, that's why I asked if they were summarized together in some place. On 17 May 2010 16:05, Andreas Nilsson <[email protected]> wrote: > > Isn't this a heuristic evaluation, rather than a user-case based one? > http://www.useit.com/papers/heuristic/heuristic_list.html > - Andreas > _______________________________________________ > usability mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/usability > _______________________________________________ usability mailing list [email protected] http://mail.gnome.org/mailman/listinfo/usability
