CS408 Human Computer Interaction GDB No. 1 Spring 2014 Last Date Aug 11, 2014

[Vuhelper]

View more random threads:

• MGT602 Entrepreneurship GDB Solution
• First gdb MGT401 Financial Accounting 23 October 2012
• FIN622 Help fall 2010
• CS610 - Computer Network GDB No. 01 Discussion Fall 2013
• STA301 Statistics and Probability GDB No.01 Discussion ...
• Mgt301 GDB No. 1 November fall 2010
• MTH603 Numerical analysis GDB required
• MGT502 Organizational Behaviour gdb 2011
• gdb 1 solution of mgt101
• Cs506 GDB fall 2011 January 2012 Due dateJanuary 26, 2012

CS408 Human Computer Interaction Graded Discussion Board (GDB) No. 1 Solution and Discussion Spring 2014 Last Date: Aug 11, 2014


You studied “Evaluation methods” like Heuristics, Cognition, Questionnaire etc in this course. All these methods apply on web applications during and after development.

Now days all of you are familiar with Mobile web apps that are used only for single task like weather forecasting etc. Keeping in view the context as described above, environment and nature of application (Multi-touch gestures like swipe and pinch), do you think that existed “Evaluation Methods” are sufficient for good results? Justify your point of view in either case with very solid points. Your answer must be precise; no detail is required in paragraph form.



Solution Is Here

Heuristic Evaluation

Heuristic evaluations were introduced by Nielsen and Molich in 1990 in the influential paper "Heuristic Evaluation of User Interfaces" and later assembled as part of a book (Nielsen 1994). A heuristic evaluation involves having an expert review an interface against a set of guidelines or principles. These heuristics provide a template to help uncover problems a user will likely encounter. Nielsen's 10 heuristics are the most popular but there are actually many more.

Cognitive Walkthrough

A cognitive walkthrough is also a usability inspection method like heuristic evaluation but the emphasis is on tasks. The idea is basically to identify users' goals, how they attempt them in the interface, then meticulously identify problems users would have as they learn to use an interface. The method was also introduced at the same conference as Heuristic Evaluation (Lewis et al 1990). The cognitive walkthrough was an extension of earlier work by Polson and Lewis (1990)

Sponsored Links

[Vuhelper]

i just think that these evaluation techniques are sufficient for good results because we know that the heuristics are specific guidelines and they are different for every S/W product. questionnaires are very good tools from the user's feed back perceptive as we can get users opinions in an objective form, cognition is again very very useful tool for evaluation of the product because in this technique the experts behave as they are the real end users of the product and identify the problems and issues that a user can/will face to fulfill its goal. overall a good product must fulfill the usability goals and i think from these evaluation techniques we can achieve these goals. must listen the related lecture and students are requested to comment on it and discuss if i am right or not

[Vuhelper]

The cognitive walkthrough method is a usability inspection method used to identify usability issues in interactive systems, focusing on how easy it is for new users to accomplish tasks with the system. Cognitive walkthrough is task-specific, whereas heuristic evaluation takes a holistic view to catch problems not caught by this and other usability inspection methods. The method is rooted in the notion that users typically prefer to learn a system by using it to accomplish tasks, rather than, for example, studying a manual. The method is prized for its ability to generate results quickly with low cost, especially when compared to usability testing, as well as the ability to apply the method early in the design phases, before coding even begins.