How UX characteristics affect software design
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. A designer reviews a login screen. Which set of UX characteristics is the design checked against?
2. A school app forces students to log in with a 20-character password and a code every time they open it. What trade-off is this?
3. A button has a raised 3D look and a shadow so users know it can be pressed. Which UX characteristic is being applied?
4. A fitness app can export its data as a CSV file that opens in a spreadsheet. Which UX characteristic does this support?
5. True or false: A design review only needs to check one UX characteristic, because the others will look after themselves.
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Affordance review: Does the button look clickable? | AChecklist: affordance, interoperability, security, usability | |
| 2Interoperability review: Can it export to CSV? | BRequire a 16-character password plus a code at every login | |
| 3Trade-off: stronger security can make a system harder to use | CChecks that the solution can exchange data with other software or systems, so an export option is added to the design | |
| 4Reviewing a design against UX characteristics means checking each one in turn | DChecks that controls show users how they can be used, so a design is changed if a button looks like plain text | |
| 5Design decision: remove all passwords because logging in is annoying, so usability is perfect | EUsability is improved by sacrificing security completely, ignoring the trade-off between the two characteristics | |
| 6Review: the app is easy to use, so the UX review is finished | FOnly usability was checked, but affordance, interoperability and security must also be reviewed |
C
Definitions
UX characteristics
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
Button looks clickable: __________
2.
Works with other systems: ________________
3.
Easy one-tap login may weaken ________
4.
Security vs usability is a _________
5.
IF loginSteps _ 3 THEN review usability
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
ux ← [affordance, colour]
B
FOR EACH item IN ux
C
review(design, item)
D
END FOR
Question 2
A
BEGIN review
B
security ← how easy to use
C
usability ← easy to learn
D
END review
Question 3
A
affordance ← hides how to use
B
button ← looks clickable
C
DISPLAY button
Question 4
A
SET app ← budget app
B
IF app blocks all export THEN
C
interoperable ← TRUE
D
END IF
Question 5
A
IF login adds a 2nd step THEN
B
security ← higher
C
usability ← higher
D
END IF
Answer Key
How UX characteristics affect software design
Section A: Quick Questions
Q1
B — Affordance, interoperability, security and usability
Q2
A — Stronger security makes the app harder to use
Q3
B — Affordance
Q4
A — Interoperability
Q5
A — False: the design is reviewed against all of them
Section B: Match the Pairs
Q1
Affordance review: Does the button look clickable? → Checks that controls show users how they can be used, so a design is changed if a button looks like plain text
Q2
Interoperability review: Can it export to CSV? → Checks that the solution can exchange data with other software or systems, so an export option is added to the design
Q3
Trade-off: stronger security can make a system harder to use → Require a 16-character password plus a code at every login
Q4
Reviewing a design against UX characteristics means checking each one in turn → Checklist: affordance, interoperability, security, usability
Q5
Design decision: remove all passwords because logging in is annoying, so usability is perfect → Usability is improved by sacrificing security completely, ignoring the trade-off between the two characteristics
Q6
Review: the app is easy to use, so the UX review is finished → Only usability was checked, but affordance, interoperability and security must also be reviewed
Section C: Definitions
Q1
UX characteristics — Affordance, interoperability, security and usability. Designers review a solution against each one and balance trade-offs, such as stronger security making a system harder to use.Section D: Fill in the Blanks
Q1
Button looks clickable: affordanceQ2
Works with other systems: interoperabilityQ3
Easy one-tap login may weaken securityQ4
Security vs usability is a trade-offQ5
IF loginSteps > 3 THEN review usabilitySection E: Spot the Error
Q1
A — Colour is a UI element, not a UX characteristic. The review list should hold UX characteristics such as affordance and security (as well as interoperability and usability).
Q2
B — Security is about protecting data and access. Ease of use describes usability, so the line should be security ← protects data.
Q3
A — Affordance means a design visibly suggests how it should be used. It should show how to use an element, not hide it.
Q4
B — An app that blocks export cannot share data with other systems, so it is not interoperable. The condition should be that the app exports a standard file such as CSV.
Q5
C — This is the security versus usability trade-off. An extra login step makes the system more secure but harder and slower to use, so usability goes lower.