Wiki source code of Measuring Instruments
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
1.2 | 1 | |
![]() |
6.2 | 2 | |
3 | |||
![]() |
8.1 | 4 | == Basics== |
![]() |
6.2 | 5 | |
![]() |
8.1 | 6 | === Decide framework=== |
![]() |
6.2 | 7 | |
![]() |
9.1 | 8 | ==== DETERMINE THE GOALS==== |
![]() |
6.2 | 9 | |
![]() |
10.1 | 10 | * What are the high-level goals of the evaluation? |
11 | * Who wants it and why? | ||
12 | * The goals influence the approach used for the study. | ||
13 | |||
![]() |
11.4 | 14 | |
15 | ==== EXPLORE THE QUESTIONS==== | ||
16 | |||
![]() |
11.1 | 17 | Define (sub)goals & (sub)research questions. |
![]() |
8.1 | 18 | |
![]() |
11.4 | 19 | |
20 | ==== CHOOSE EVALUATION APPROACH & METHODS==== | ||
21 | |||
![]() |
11.1 | 22 | The evaluation approach influences the methods used, and in turn, |
23 | how data is collected, analyzed and presented | ||
![]() |
8.1 | 24 | |
![]() |
11.4 | 25 | |
26 | ==== IDENTIFY PRACTICAL ISSUES==== | ||
27 | |||
![]() |
11.1 | 28 | For example: |
![]() |
11.2 | 29 | * Select users. |
30 | * Stay on budget. | ||
31 | * Stay on schedule. | ||
32 | * Find participants. | ||
33 | * Select equipment. | ||
![]() |
11.1 | 34 | Perform a pilot (trial) study! |
![]() |
9.1 | 35 | |
![]() |
10.1 | 36 | |
![]() |
11.4 | 37 | ==== DECIDE ABOUT ETHICAL ISSUES==== |
![]() |
10.1 | 38 | |
![]() |
11.4 | 39 | |
40 | |||
41 | ==== EVALUATE, ANALYZE, INTERPRET AND PRESENT THE DATA==== | ||
42 | |||
43 | |||
![]() |
11.3 | 44 | The approach and methods used influence how data |
45 | is evaluated, analyzed, interpreted and presented. | ||
![]() |
10.1 | 46 | |
![]() |
11.1 | 47 | |
![]() |
11.4 | 48 | === IMPACT framework=== |
![]() |
19.1 | 49 | * Intention: Clarify objectives and hypotheses/claims |
50 | * Metrics & measures: What, how and why | ||
51 | * People: Target group & participants | ||
52 | * Activities: Derive activities from use cases | ||
53 | * Context: Social, ethical, physical, etc. aspects | ||
54 | * Technologies: Hardware and software | ||
![]() |
11.1 | 55 | |
![]() |
11.4 | 56 | |
![]() |
20.1 | 57 | |
![]() |
21.1 | 58 | ==== Formative evaluation==== |
![]() |
23.1 | 59 | Focuses on the various processes of the human-technology interaction. |
60 | Derive open questions from your design specification. | ||
![]() |
21.1 | 61 | ==== Summative evaluation==== |
![]() |
23.1 | 62 | Focuses on the overall effects of the human-technology interaction. |
![]() |
24.1 | 63 | |
64 | |||
![]() |
28.1 | 65 | === Data === |
![]() |
29.1 | 66 | [[image:Data Type.png]] |
![]() |
24.1 | 67 | ==== Qualitative Data==== |
68 | • Words | ||
69 | • Drawings | ||
70 | |||
![]() |
26.1 | 71 | ==== Quantitative Data==== |
![]() |
24.1 | 72 | • Numbers |
73 | • Statistics | ||
74 | |||
![]() |
13.1 | 75 | == GOOD EVALUATION == |
![]() |
1.2 | 76 | |
![]() |
5.1 | 77 | * Establishing convincing arguments for your design solution |
![]() |
6.1 | 78 | |
![]() |
5.1 | 79 | * By conducting complementary and regular evaluations at different stages |
80 | of your design process using the appropriate evaluation methods | ||
81 | (e.g. summative, formative, expert-based, observational, ...) | ||
![]() |
6.1 | 82 | |
![]() |
5.1 | 83 | * Evaluations should result in insights regarding possible problems and |
84 | their causes in order to support refinement of your design specification | ||
![]() |
6.1 | 85 | |
![]() |
5.1 | 86 | * Look at user experience in its full breadth: Effectiveness, efficiency, |
87 | satisfaction, learnability, mood, connectedness, ... | ||
![]() |
1.2 | 88 | |
![]() |
3.1 | 89 | |
![]() |
4.1 | 90 | |
![]() |
5.1 | 91 | |
92 | |||
93 |