Section 2 Flashcards
What are the principles of User-Centered Design?
What is the User-Centered Design process and why use it?
What are the goals for each stage of the User-Centered Design Process?
What are good investigation Questions
Identify users
Identify stakeholders
What are the requirements? How do they do it now?
How long does it take?
What do they want?
What do they need?
What have they already tried? Is there another solution?
What is the stage Ideation about?
“To get good ideas… Get lots of ideas”
One of the worst things: go with the first one you have
You can always come back to it later
Volume matters the most
Increase chance of success by considering a huge volume of ideas in a systematic way
What is a prototype?
It’s cheap and fast
Easier for users to react to concrete things rather than abstract concepts
Prototyping brings subtleties and nuances to light
Working against some technical
constraints is good
What are the prototype fundamentals?
Build it fast
Concentrate on unknowns
Don’t be attached to themeasy to throw away
Build multiple concurrentlyeasier to compare pros/cons
Why use the Evaluation stage?
What is wrong with automated software testing?
- Automated processes can find bugs, but not usability issues
Evaluation gives you a way to move forwardWhat needs to be fixed, added, removed?
- Answers to two questions:Did we build the right thing? Did we build the thing right?
Evaluation Drives Iteration
Problem: usefulness/appropriateness
Return to investigation phase
Problem: users don’t understand
Return to ideation phase
Problem: user performance
Return to prototyping phase
What are the steps required to go from functional prototype to release candidate?
These are steps required to go from functional
prototype to release candidate:
- Software architecture
- Programming, building
- Manufacturing
- Help systems
- Manuals
- Training Customer support
- Marketing
- Branding
- Distribution
Good design summary
Design starts with understanding your user, and should keep users’ interests central through entire process
Design is iterative -> trade-offs are difficult to see in advance
Designs are never “perfect” -> they can be improved
In general, who are your users?
People who directly interact with the product/application to accomplish a task
But is that it?
Others
Those who manage direct users
Those who receive products from the system Those who maintain the system
Those who make purchasing decisions Competitors
What are the categories of users?
What are the user factors that affect the development process?
What are the three types of user experience?
Age: reduce number of tasks, simplified interface
Disabilities: larger buttons, sound cues
Gender: spatial vs. temporal relations
Culture: icons, color Experience
Three types of experience:
Novices: highly visible functions, restricted set of tasks, tutorials to more complex tasks
Intermediate: reminders and tips, interface facilitates advanced tasks
Experts: shortcuts visible functions, restricted set of tasks, for efficiency, customizable interface
Who are the stakeholders for an automated check-out system at a large grocery store?
Customers:
Primary users: customers will operate it every time they make purchases
Check out operators:
Primary/secondary users: they interact with the system (often daily) when customers are having difficultly
Managers and owners:
secondary or tertiary users: they may occasionally interact with the system but mostly concerned about satisfied customers, safety and good functionality of system
What are the primary types of requirements?