Download D4.3 - VICON

Transcript
11
12
“The colour highlighting of
the evaluation result
statuses was helpful.”
Comment:
2
2
The user should group colours.
If you can put a filter it will
become handy.
Result Menu: the green
highlighting is not very
important, but the red is
important. So filtering would
be helpful.
Task selection: Check mark
(check icon) for already
simulated tasks.
It is helpful to highlight with
colours, but I need the
connection to the moment in
the 3d animation where the
problems occur.
The highlighting is very good,
but the connection to the 3d
should be there. And more
slowly and one after each
other.
Highlighting in general is of
cause helpful, but I'm not
sure if the colour highlighting
is a good solution I don't
know. Maybe highlighting by
symbols/signs is better.
Symbols and colours
together work best!
In the results list the titles of
the tasks/subtasks should be
presented in a different way
as the tests.
I mean the headlines of the
tasks look the same as other
lines and so on. They should
be better distinguished from
the sub headlines and these
should be different from the
tests.
2
1
3
“The colour coding used for
the highlighting of the
evaluation result statuses
was intuitive.”
Comment:
13
3
“The evaluation results
report was easy to access.”
Comment:
Yes.
O.k. it’s universal.
2
Yea. Because it comes directly
to your face.
D4.3: Evaluation report on how convenient it is
to use virtual user model and adapted prototype
2
It was not clear that I would
get report in form of a text.
So it was not clear, that I
should click on the separate
tests in order to open them.
Final
At the beginning the colours
should be explained. The
colours themselves are
intuitive, but how they were
used was not intuitive. The
colours should be used more
precise.
The difference between red
and yellow. It was actually
also not clear for red
whether the user did it with
difficulties or could not make
the subtask at all.
2
It's o.k. but it could be
better.
After a test is gone from your
point of view, it should be
closed automatically.
Otherwise you end up with a
very long list of opened test
results, which you have to
close first before you can get
an overview again.
Page 109 of 130