Revised version: 21.01.2009 (final)

Product name and version: M 32 Usability Report on ToDo-List, Chat (and Google calendar and docs - not evaluated).
Organisers of the test: UU
Date of the test: 20.01.2009
Date of the report: 
20.01.2009
Editor: Crina Damşa and Patrick Sins
Contact name(s): C.I.Damsa@uu.nl, P.H.M.Sins@uu.nl

Executive summary

Purpose/objectives of the test: Expert Evaluation
Method 1:Review of documentation
Method 2: Diagnostic test
Number and type of participants: 2

Results in main points, e.g. bullet list

The document reports on an expert evaluation of the ToDo-List and Chat functionalities, conducted at the Utrecht University in January 2009. The two evaluators had been using Knowledge Practices environment M 24.
Two types of evaluations were performed. First, a review of documentation was conducted, for which we employed the list of user tasks that are reported in D2.4 Driving Objectives and High-level Requirements for KP-Lab Technologies as a frame for our analyses. Second, a diagnostic test was conducted on the Chat functionalities. The ToDo-List was evaluated the described above because the development server were prototypes are, was not available for the evaluators during the time period that executed the evaluation. Google docs (proto) and Google calendar (proto) had been postponed therefore the testing of these is postponed also (see KP-Lab (2008e)).

The review of documentation indicated that:

  • The general chat provides a flexible tool for communicating, since chat sessions can be initiated at any moment, regardless the location of the user and the moment at which his/ her contribution was made. In addition, the general chat may be saved, and subsequently retrieved in case users are in need of the information that was exchanged in the chat.
  • The context-based chat can be employed to have more elaborative discussions on a particular artefact (i.e. content item in KPE) by several users at the same time. The strength of this tool is that it can serve to foster synchronous commenting on a particular content item. However, at the same time this functionality overlaps to a great extent with the commenting functionality in the sense that both tools offer the possibility to discuss on a particular content item in an asynchronous way. This may cause confusion and more effort from users to integrate information in the commenting tool with the conversations in the context-based chat tool.
  • In the context of supporting management and organization of collaborative work processes the ToDo List provides support for individuals who are involved in this collaborative process, by scaffolding their planning activities. Indirectly, this tool support individuals in their participation in collaborative work, which is based on combining individual and joint contributions.
The diagnostic test of the Chat indicated:
  • Creating and opening chat sessions (both in the General and Context-based chat) are unproblematic.
  • Inserting and sending chat messages works properly.
  • It is not possible to retrieve the (automatically) saved chat sessions.
  • The system does not display the name of the participants in the chat sessions (especially in the case of the Context-based chat).
  • Adding and removing contacts to the chat contacts list works properly. To make the last operation more user friendly it should be possible to remove contacts directly from the chat contacts list.
  • Slow response when sending chat messages and sometimes (e.g. when closing and reopening a shared space) whole chat disappears.
  • A minimizing function for the chat window should be added



Reference:
KP-Lab (2008e). M33 specification of end-user applications. Deliverable 6.6




This page is a category under: usability and under Category Of Feedback Testing Data

  Page Info My Prefs Log in
This page (revision-5) last changed on 18:24 25-Mar-2017 by EiniSaarivesi.
 

Referenced by
Category Of Feedb...

JSPWiki v2.4.102
[RSS]