100 likes | 191 Views
Post-hoc testing. IST 331 - Olivier Georgeon April 22 nd 2010.
E N D
Post-hoc testing IST 331 - Olivier Georgeon April 22nd 2010
Human nature is not a machine to be built after a model - and set to do exactly the work prescribed to it - but a tree, which requires to grow and develop itself on all sides, according to the tendency of the inward forces which make it a living thing.John Stuart Mill, On Liberty (1859)
Evolutionist process Design Use
Why post-hoc testing? • Avoid recalls. • Identify target. • Identify need for formation or documentation. • Final setup. • Evaluate the design. • Because all people (including designers) make mistakes (i.e. user-testing can be used as a type of proof-reading). • Provide feedback for the next iteration.
Methods • Same method as preliminary studies • Questionnaires and Interviews • Observational studies • Verbal protocol • Visual protocol • Use unsolicited comments
Activity analysis tools • Noldus • http://www.noldus.com • Interact • http://www.mangold-international.com/ • Abstract • http://liris.cnrs.fr/abstract/
Example Local Youtube
Republic of Ireland [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] 1/10/1973 [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] 4/3/1970 5/20/2007 [7] Irish National Liberation Army (INLA) [8] Saor Eire (Irish Republican Group) [9] Official Irish Republican Army (OIRA)/ [10] Irish People's Liberation Organization (IPLO) [11] Irish Republican Army (IRA) [1] Ulster Volunteer Force (UVF) [2] Ulster Freedom Fighters (UFF) [3] Protestant Extremists [4] Loyalist Volunteer Forces (LVF) [5] Red Hand Commandos [6] Unknown
Conclusion • Interface design is an evolutionist process. • Post-hoc evaluation also matters. • Lot of room for IST research.