UI Design - Test 3

Question 1

Requirements Analysis

Answer 1

1. Needs assessment
If we decide to go on:
2. Functional requirements
3. Non-functional requirements
4. Data requirements
5. Environmental requirements (context of use)
6. Social Environmental Requirements
7. Organizational Environmental Requirements

Question 2

Needs Assessment

Answer 2

Burton & Merrill’s 4 steps (1991)

 1) Identify a broad range of possible goals
 2) Rank goals in order of importance
 3) Identify discrepancies between expected and actual performance
 4) Set priorities for action

Question 3

Preference Metrics

Answer 3

(affective data)
commonly use a Likert Scale: _ _ _ _ _ (A lot, A little,)
*often require special statistical measures *
often correlate weekly, if at all

Question 4

SUSS: Subjective Usability (Scales for Software)

Answer 4

a. Valence-> liking or personal preference
b. Aesthetics -> attractiveness
c. Organization -> graphical design + layout
d. Interpretation->
e. Acquisition->
f. Facility -> overall ease of use

Question 5

Performance Metrics

Answer 5

1. Completeness-> given a set series of tasks, how much is done in a certain time period
2. Correctness-> how many were done correctly
3. Effectiveness-> how much work was done correctly out of the total
4. Efficiency-> what was the effectiveness relative to some time period
5. Proficiency-> compared to an expert, what is the efficiency of subject
6. Productiveness-> of all the time spent on the task, how much was productive ((TimeTotal – TimeProductive)/TimeTotal )

Question 6

Predictive Metrics

Answer 6

• predicts how “good” the final product will be.

Question 7

Criteria for a good metric

Answer 7

1. Easy to calculate
2. Apply to passive prototypes as well as active prototypes
3. Must have a strong rationale and conceptual basis
4. Must be able to discriminate between designs
5. Offer guidance for design
6. Must effectively predict actual usability
7. Directly indicate the quality of the design

Question 8

Essential Efficiency

Answer 8

a procedural metric based on essential use cases

EE = 100 * Sessential / Senacted (enacted is often larger)

Question 9

Task Concordance

Answer 9

A measure of how pairs of items are correctly ordered versus incorrectly ordered.

Question 10

Task Visibility

Answer 10

procedural metric based on essential use case. Measures how visible the tools and components of a task are when needed.

• 1.0 - entirely available/visible (i.e. a button that directly performs the task)
• 0.5 - retrievable from a menu
• 0 - if not obvious at all

Question 11

Layout Uniformity

Answer 11

a structural metric that asserts that L.U. is lowered by a highly chaotic interface/design. Good score is 50-85%

Question 12

Gathering Data - Categories

Answer 12

• Structured - all questions set up ahead of time
• Unstructured - some set up ahead of time, some are based upon results, comments.
• Open-ended - elicit responses that the person may want to tell us
• Close-ended - All answers are options

Question 13

Gathering Data - Basic Rules

Answer 13

1. Make them short + sweet, 1 page is best
2. Easy Questions - closed ended, structured
3. Open ended questions - if any at all, should be last
4. Do a pilot study to verify that all questions are understood - usually 7-10 people
5. Can use methods to determine reliability and validity
6. All users complete the instrument
7. Privacy is good if it can be managed
8. Explain your purpose - get buy in
9. Thank them for their participation

Question 14

Surveys - Advantages & Disadvantages

Answer 14

Advantages: cheap, everyone can participate.
Disadvantages: What do we do when things are blank? Responses may be more about how question is worded rather than what were trying to measure.

Question 15

Methods of Gathering Info

Answer 15

• Surveys/Questionnaires
• Interviews (P2P Questionnaires)
• Focus Groups
• Naturalistic Observation - Ethnography
• Studying Historical Documents

Question 16

Usability Testing (Evaluation)

Answer 16

1. Set up goals and measurable objectives
2. Determine the methods for monitoring results to ensure accuracy and reliability.
3. Create any testing instruments and validate with a pilot study.
4. If necessary, train expert evaluators.
5. Set up carefully monitored locations
6. Pick the sample - random samples if possible
7. Run the experiments - be consistent
8. Pool the data and perform statistics
9. Draw conclusions, if possible

Question 17

Expert Evaluation

Answer 17

• a subjective measure of interface analysis by a paid expert
  ○ May find 60%-70% of errors
  ○ Fairly quick
  ○ All you get is a list of errors
  ○ Methods used
  A. Studied Ignorance - look at interface as a rank novice would. (Good method to find immediate errors).
  B. Over the Edge - try to overuse the system and see how it reacts
  Every Mountain - test every menu option, combo of options, buttons, tools, etc.

Question 18

Peer Evaluation

Answer 18

• get your pal at work to test the system
  A. May see things the way a developer does and not
  other users would
  B. Bias - for or against your product
  C. Politics status
  D. Their time costs money too

Question 19

Inspections (Evaluation)

Answer 19

Intended ONLY to identify errors.

- Heuristic Evaluations - evaluates using Jacob Nielsen original 10 heuristics (95% of errors are in those rules)

Question 20

Cognitive Walkthrough (Evaluation)

Answer 20

Tast scenarios identified and success criteria set. Experts watch walk-through and finds problems keeping tasks and users in mind.

Question 21

Collaborative Usability Inspection (Evaluation)

Answer 21

A systematic examination of a finished product, design, or prototype from the point of view of its usability by the intended end users. (Quality Assurance technique)