The cognitive walkthrough method: a practitioner's guide
Usability inspection methods
Usability in practice: formative usability evaluations - evolution and revolution
CHI '02 Extended Abstracts on Human Factors in Computing Systems
Comparative evaluation of usability tests
CHI '99 Extended Abstracts on Human Factors in Computing Systems
The usability engineering lifecycle
CHI '99 Extended Abstracts on Human Factors in Computing Systems
On the reliability of usability testing
CHI '01 Extended Abstracts on Human Factors in Computing Systems
Moving beyond user participation to achieve successful IS design
Communications of the ACM
Designing the User Interface: Strategies for Effective Human-Computer Interaction
Designing the User Interface: Strategies for Effective Human-Computer Interaction
Applying computational science techniques to support adaptive learning
ICCS'03 Proceedings of the 2003 international conference on Computational science: PartII
The Learners' User Classes in the TERENCE Adaptive Learning System
ICALT '12 Proceedings of the 2012 IEEE 12th International Conference on Advanced Learning Technologies
| Hi-index | 0.00 |
Iterative design is nowadays indicated as the approach that most likely produces a successful system, and the application of usability evaluation methods is identified as the primary key that allow designers to reveal and fix problems early or, to better say, at the right moment during the design of the system. These approaches often overlooks issues that get revealed only when system "goes live", namely system performances and a different attitude of the users towards the system. With respect to these issues, in this paper we discuss the lessons learned from the TERENCE project -- a technology enhanced learning project for improving the text comprehension in children 7-11 years old -- and in particular from a large-scale evaluation. Our experience suggests modifications to the classical UCD lifecycle: on the one hand post implementation activities should be foreseen since the beginning (and assigned reasonable time and appropriate budget), and on the other hand system performance evaluation should be anticipated and integrated in the lifecycle, to be able to predict system behavior and variables that affect it, and consequently produce "performance informed" design iterations (with performances considered at interaction, architecture and coding levels). We also sketch a possible prediction approach.