SEPA diary Heuristic evaluation

Transcription

1 T Software Project Heuristic evaluation Jon Korgell, 61029B & Niklas Roitto, 58546J RAY/Valimo Electronic Payment System MVJ Valvomo Team CashFlow 4 Dec 2005 Revision 3 1/6 24 Nov 2005 (Revision 1)

2 Document Revisions Revision Date Author Description Krogell & Roitto Initial draft Krogell & Roitto PP iteration delivery Krogell & Roitto I1 iteration delivery 2/6 24 Nov 2005 (Revision 1)

3 Contents 3/6 24 Nov 2005 (Revision 1)

4 1. Introduction The topic of our SEPA is heuristic evaluation. Heuristic evaluation is a usability inspection method, which is done as a systematic inspection of a user interface's design considering its usability. The goal of heuristic evaluation is to find the usability problems in the design so that they can be attended to as part of an iterative design process. Heuristic evaluation is familiar from the course book Usability Engineering (Faulkner). Heuristic evaluation is a suitable topic for many reasons. First of all both participants have prior experience with usability evaluation on behalf of studies. In addition to this Krogell has selected usability as a minor subject in his studies. Because our system will rely heavily on its user interface it is important that we devote enough time to simplify and perfect it. 2. Deployment of the practice The heuristic evaluation will be conducted in the middle of both implementation iterations. We expect to have completed some kind of user interface by then. For the evaluation we will use Jakob Nielsen s 10 usability heuristics, which are: 1. Visibility of system status 2. Match between system and the real world 3. User control and freedom 4. Consistency and standards 5. Error prevention 6. Recognition rather than recall 7. Flexibility and efficiency of use 8. Aesthetic and minimalist design 9. Help users recognize, diagnose, and recover from errors 10. Help and documentation 3. Experiences and changes Here we present the experiences collected in each of the iterations, where the practice was used. Any changes made to the way the practice is used are also described. 3.1 Project planning No evaluations were made in this phase, only planning. 4/6 24 Nov 2005 (Revision 1)

5 3.2 Implementation 1 During this iteration the only GUI usable for testing was a HTML prototype model. This prototype was finished on the last week of the iteration, which left us no time to perform a thorough evaluation. However, the following remarks were made during a quick evaluation: Found problems are classified according to these types: Severe High priority usability problem that needs to be fixed. Medium Usability problem that needs to be fixed. Low Small usability problems that can be fixed if allowed by schedule. Undetermined Usability points that cannot be evaluated at the moment. 1. Visibility of system status Severe: The visibility of system status is not clearly visible anywhere. 2. Match between system and the real world Low: Some unclear terms due to prototype status. 3. User control and freedom Undetermined: Hard to say because of limited prototype functionality. 4. Consistency and standards No remarks. 5. Error prevention Undetermined: Hard to say because of limited prototype functionality. 6. Recognition rather than recall No remarks. 7. Flexibility and efficiency of use Undetermined: Hard to say because of limited prototype functionality 8. Aesthetic and minimalist design Medium: Colouring of the interface needs to be harmonized. Medium: Button fonts and colours need to be revised and streamlined. 9. Help users recognize, diagnose, and recover from errors Undetermined: Hard to say because of limited prototype functionality. 10. Help and documentation Undetermined: No help documentation present. The identified problems will be attended to according to classification in the second implementation phase. 5/6 24 Nov 2005 (Revision 1)

6 3.3 implementation Summary A summary of the experiences. Evaluation of the suitability of the practice to your project, and ideas of the reasons if the practice was not suitable in this project. 4. Sources Jakob Nielsen - Heuristic Evaluation ( 6/6 24 Nov 2005 (Revision 1)