Requirements Part 1 - P3, M2, P6 D2 Refine Designowenfunnell.co.uk/web_docs/lvl3yr2/unit23/Evaluating.pdf · Part 4 –M3 Part 3 –P4, P6 Part 5 –P4, P5, P6 ... Evaluating the

Requirements

Design

DeployEvaluate

Refine

Part 1 - P3, M2, P6

Part 2 – P3, M2, P6

Part 3 – P4, P6Part 4 – M3Part 5 – P4, P5, P6

Part 6 – D2

Evaluating the effectiveness of different designs of Input and Outputs

During the process of designing, building and refining HCI interfaces evaluation are done constantly to check the effectiveness of the design.

Requirements

Design

DeployEvaluate

Refine

Steam Controller

Steam Controller

During the process of designing the ne Xbox One Elite Controller several prototypes were made which were given to user to test.

They gave feedback on the design which then influenced the next design, slowly building the ‘perfect controller’


There are two ways to gather evidence for evaluation.

Quantitative Research Qualitative ResearchInvolves collecting data that can be measured and

counted. The data collected can be usually be presented in the form of graphs, tables and charts.

It is important to use a large enough sample to ensure that you have used sufficient ‘quantity’ for the results

to be valid and not guesswork.

Example: Questionnaire

Involves collecting information about peoples opinions, views and preferences about something.

It allows you to make ‘quality’ judgments about your findings (based on fact, not your own options)

Example: Interview


Quantitative ResearchQuantitative tests can be measured or assigned an actual value. This is sometimes called Usability

engineering in the HCI world. So how long (in seconds) does it take to login in or How many clicks of the mouse are needed to enter data into a page etc.

• Input speeds

• Comparative costs

• Comparison against needs


Quantitative ResearchInput Speed

One of he features that is fundamental to its effectiveness is the speed at which it interacts with the user. Issues of speed include:

• How quickly the user can input a command

• The speed at which the user can (or has to) type in any data (does the GUI ‘time out’ if reaction isn’t fast enough?)

• The speed of throughput (such as the response back from, the interface - Feedback)

• The length of time it takes the user to comprehend the results


Quantitative ResearchComparative Cost

Cost of the interface in comparison to what was used before. Has it speed up or slowed work?

Is it a fast and efficient process compared to manual processes


Quantitative ResearchComparison Against Original Need

How closely does it match the original design?

1. How many features are included

2. How many are partially included

3. How many not included.

4. Does it meet the needs of the client/user.


Here the measures are subjective, they are measures where no values can be given

• User Satisfaction

• Comparisons with other systems

Qualitative Research

You need to use Open rather then Closed questions. A closed question can only be answered with simple close responses such as a yes or no

Open questions lead to more informative answers from the subjects.

Do you like food?What type of food do you like?


User Satisfaction

An essential question is the level of satisfaction by the end user with the HCI built. Simple open questions such as ‘What do you like about XYZ’ or ‘How could XYZ be improved?’ Other things include:

• Knowledge required (Did you user need to know anything. Did they need prior knowledge)

• Skills/expertise required (Where there any extra skills that are required)

• Is it easy to use?

• Are there limitations?

• Does it meet needs?



Comparisons with Other Systems

A good way to gauge a users satisfaction with a system is to get them to compare it with similar systems they have used.

Which system do you prefer A or B?

What parts make A better then B?

In what way is A worse then B?


Requirements Part 1 - P3, M2, P6 D2 Refine Designowenfunnell.co.uk/web_docs/lvl3yr2/unit23/Evaluating.pdf · Part 4 –M3 Part 3 –P4, P6 Part 5 –P4, P5, P6 ... Evaluating the

Documents