Lesson 3 Flashcards
Is the process of developing a tool from the perspective of how it will be understood and used by a human user.
An iterative design process in which designers focus on the users and their needs in each phase of the design process.
User-centered Design (UCD)
To a system design results in a product that delivers more efficiently, satisfyingly, and user-friendly experience for the user; thus, leading to increased sales and customer loyalty.
Employing UCD
PRINCIPLES OF UCD
2) Maintain consistency
3) Use simple and natural dialogue
5) Provide adequate feedback
7) Let the user take charge
9) Offer Assistance
10. Error-free
1) Design for the users and their tasks
4) Reduce unnecessary mental effort by the user
6) Provide adequate navigation mechanisms
8) Present information clearly
THE PROCESS OF UCD
• Specify the context of use
• Specify requirements
• Create design solutions
• Evaluate designs
Identify the people who will use the product, what they will use it for, and under what conditions they will use it.
Specify the context of use
Identify any business requirements or user goals that must be met for the product to be successful.
Specify requirements
This part of the process may be done in stages, building from a rough concept to a complete design.
Create design solutions
Evaluation - ideally through usability testing with actual users - is as integral as quality testing is to good software development.
Evaluate designs
_ 10 general principles for interaction design. They are called “_” because they are broad rules of thumb and not specific usability guidelines.
Jakob Nielsen’s
heuristics
10 Usability Heuristics for User Interface Design
1) Visibility of system status
2) Match between system and the real world
3) User control and freedom
4) Consistency and standards
5) Error prevention
6) Recognition rather than recall
7) Flexibility and efficiency of use
8) Aesthetic and minimalist design
9) Help users recognize, diagnose, and recover from errors
10) Help and documentation
The first principle is about keeping users informed about their actions and what’s happening at a given interaction.
1) Visibility of system status
This principle claims that a system should always speak the user’s language and follow real-world conventions.
2) Match between system and the real world
A good UI design should never impose an action on the user or make decisions for them. Instead, the system should only suggest which paths the users can take.
3) User control and freedom
This heuristic is about keeping the same language throughout the system to avoid confusing the user.
4) Consistency and standards
This Nielsen heuristic proposes that a good design should always prevent problems from occurring.
5) Error prevention
As seen, Nielsen’s heuristics aim to reduce users’ cognitive load, and this also includes their memory capacity.
6) Recognition rather than recall
Your designs should benefit both inexperienced and experienced users.
7) Flexibility and efficiency of use
As a designer, please don’t consider aesthetics above functionalities.
8) Aesthetic and minimalist design
Your designs should help the user identify and find solutions to eventual problems and errors.
9) Help users recognize, diagnose, and recover from errors
The last of Nielsen’s heuristics concerns documentation that will help users understand how to perform their tasks.
10) Help and documentation
Don Norman’s Principles of Interaction Design
Visibility
Feedback
Constraints
Mapping
Consistency
Affordance
Is the basic principle that the more visible an element is, the more likely users will know about them and how to use them.
Visibility
Is the principle of making it clear to the user what action has been taken and what has been accomplished. Many forms of _ exist in interaction design, including visual, tactile, audio, and more.
Feedback
Is about limiting the range of interaction possibilities for the user to simplify the interface and guide the user to the appropriate next action. This is a case where _ are clarifying, since they make it clear what can be done.
Constraints
