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 | |||
![]() |
8.1 | 14 | |
15 | |||
![]() |
9.1 | 16 | |
![]() |
10.1 | 17 | |
18 | |||
19 | |||
![]() |
4.1 | 20 | ==== GOOD EVALUATION ==== |
![]() |
1.2 | 21 | |
![]() |
5.1 | 22 | * Establishing convincing arguments for your design solution |
![]() |
6.1 | 23 | |
![]() |
5.1 | 24 | * By conducting complementary and regular evaluations at different stages |
25 | of your design process using the appropriate evaluation methods | ||
26 | (e.g. summative, formative, expert-based, observational, ...) | ||
![]() |
6.1 | 27 | |
![]() |
5.1 | 28 | * Evaluations should result in insights regarding possible problems and |
29 | their causes in order to support refinement of your design specification | ||
![]() |
6.1 | 30 | |
![]() |
5.1 | 31 | * Look at user experience in its full breadth: Effectiveness, efficiency, |
32 | satisfaction, learnability, mood, connectedness, ... | ||
![]() |
1.2 | 33 | |
![]() |
3.1 | 34 | |
![]() |
4.1 | 35 | |
![]() |
5.1 | 36 | |
37 | |||
38 |