MDI Terms and Concepts

5.0(1)
studied byStudied by 361 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/99

flashcard set

Earn XP

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

100 Terms

1
New cards
Interaction design
Designing interactive products to support the way people communicate and interact in their everyday and working lives. Often carried out by multidisciplinary teams.
2
New cards
Safety
A usability goal regarding protecting the users from dangerous conditions and undesirable situations.
3
New cards
UX
Stands for user experience, mostly focuses on pragmatic and hedonic aspects of use. Encompasses all aspects of the end-user's interaction with the company, its services, and its products, that is, how a product behaves and is used in the real world.
4
New cards
Pragmatic Design
Includes practical factors such as usability, functionality, and budget constraints while meeting the needs of both the users and the organization. It requires research, planning, testing, and continuous evaluation to create effective, efficient, and sustainable solutions. A question that should be answered is: How simple, obvious, and practical can users achieve their goals?
5
New cards
Hedonic Design
Refers to the emotional or experiential aspect of design that aims to create a positive emotional response in users. It focuses on creating a visually appealing, aesthetically pleasing, and enjoyable experience for the user. In short: how simulating and educative the interaction is.
6
New cards
Memorability
How easy a product is to remember how to use, once learned.
7
New cards
Learnability
How easy a system is to learn to use.
8
New cards
User centred design
Refers to a design approach that focuses on the needs, goals, and preferences of the end-users throughout the entire design process.
9
New cards
Consistency
Designing interfaces to have similar operations and use similar elements for achieving similar tasks.
10
New cards
Usable
A product which is easy to learn, effective to use and provide an enjoyable user experience.
11
New cards
Multidisciplinary teams
Individuals from different disciplines or areas of expertise working together on a project or task.
12
New cards
Utility
Refers to the extent to which a product provides the right kind of functionality.
13
New cards
Effectiveness
A usability goal referring to how good a product is at doing what it is supposed to do.
14
New cards
Human Computer Interaction (HCI)
Mostly concerned with usability, focuses on the study of human-computer interactions and the design of systems and interfaces that are user-friendly and efficient.
15
New cards
Accessibility
Refers to the extent to which all users can use a product. Including people with less than average abilities. Can be achieved by inclusive design of technology and design of assistive technology.
16
New cards
User experience goals
A choice made by your product team about what kind of experience you want your users to have with your product or service. Can be articulated as a range of emotions and felt experiences
17
New cards
Micro-interactions
Moments of interactions at the interface - despite being small - can have a big impact on the user experience.
18
New cards
Visibility
Design principle describes the importance of having information visible at all (or at least the right) time.
19
New cards
Efficiency
Refers to the way a product supports users in carrying out their task.
20
New cards
Participatory design
An overarching design philosophy that places the users as central actors in creating activities.
21
New cards
Iterative design
An approach to design that involves continually refining and improving a product or solution through a series of iterative stages. Because no matter how good the designers are, ideas will need to be revised, likely several times.
22
New cards
Involving users in development
It's the best way to ensure that the end product is usable.
23
New cards
Double diamond of design
Consists of four stages: Discover, Define, Develop, Deliver. It is a visual representation of the design process.
24
New cards
Empirical measurement
Regards identifying specific goals up front that the product can be empirically evaluated against.
25
New cards
Expectation management
The process of making sure that the users' expectations of the new product are realistic.
26
New cards
Stakeholders
The individuals or groups that can influence or be influenced by the success or failure of a project.
27
New cards
User-centred approach
The real users and their goals, not just technology, are the driving force behind product development.
28
New cards
Constraints
Should be used to guide the users and stop them from making mistakes.
29
New cards
Feedback
The user gets information about which action has taken place and what effect on the system the action had.
30
New cards
Mapping
The relationship between a control and the object that is being controlled.
31
New cards
Gulf of evaluation
The distance between the physical presentation of the system state and the expectation of the user.
32
New cards
Forcing functions
Used when the user must perform a response to the system, before it is possible for the user to continue with the current task/function in the system.
33
New cards
Affordance
The way an object looks shows you how to manipulate it. Alternative definition: Determines whether the design of a product or element communicates how it can be used or what options are possible.
34
New cards
Gulf of execution
The difference between the user's formulation of the actions to reach the goal and the actions allowed by the system.
35
New cards
Slip
A type of error made by accident or due to lack of concentration
36
New cards
Checkboxes
A graphical widget that allows the user to answer more than one choice. Used when choices are not mutually exclusive
37
New cards
Radio buttons
Graphical widget that allows the user to choose only one of a predefined set of mutually exclusive options.
38
New cards
Direct manipulation interfaces
Continuous representation of objects. Physical actions instead of complex syntax. Fast, simple, visible operations where it is always possible to undo your last action.
39
New cards
Command line interfaces
Interfaces that are navigated via the use of commands. Good for experienced users that need to be efficient and quick.
40
New cards
Contextual menus
User interface elements that provide a set of options or commands relevant to the context or object that the user has selected
41
New cards
Widget
A standardized display representation of a control.
42
New cards
Icons
For this concept the most important is legibility and interpretation. They are graphical symbols or pictograms used to represent various concepts, actions, or objects in user interfaces
43
New cards
WIMP
Windows, icons, menus and pointing devices. The original Graphical User Interface
44
New cards
Form fill interfaces
Used when structured information is required. Refers to user interfaces that enables users to enter information into various fields within a form, typically on a web page or a mobile app.
45
New cards
Ecological validity
A special kind of validity that concerns how the environment in which an evaluation is done influences or even distorts the results.
46
New cards
Field based evaluation
Good at demonstrating how people use technology in their intended setting. In the wild studies/natural setting.
47
New cards
Inspection methods
Involve reviewing the design or code of an interface or product to identify potential usability issues. Are used in usability evaluation to review and analyze the design or code of a product or system. Is a cheap and quick method when the users are not available and you are short on time.
48
New cards
Cognitive walkthrough
Simulates a problem solving process to see how users progress step by step.
49
New cards
Controlled lab-based evaluation
Evaluation method that is good at revealing usability problems. The environment in which the evaluation takes place often differs from the actual circumstances of which the product is used.
50
New cards
Crowdsourcing in usability evaluation
The practice of obtaining information or input from a large, distributed group of people, often through online platforms or communities. Flexibility, inexpensive and quick.
51
New cards
Formative evaluation
Type of evaluation used during the development process of a product, system or service to assess its performance and identify areas for improvement. Checks that a product in design continues to meet the users needs.
52
New cards
Reliability
How well a method produces the same result on separate occasions
53
New cards
Summative evaluation
Done at the end of a development cycle in order to verify that product fulfills the goals
54
New cards
Usability specification
A summary of task metrics, that is for example the time it takes to complete a task.
55
New cards
Visibility and system status
The system should always keep the user informed about what is going on.
56
New cards
User control and freedom
You should provide the user with clearly marked emergency exits to leave the unwanted states.
57
New cards
Heuristic evaluation
A group of usability experts review a user interface according to a small set of principles.
58
New cards
Flexibility and efficiency of use
Provide accelerators for the more proficient users.
59
New cards
Match between system and the real world
The system should speak the users' language.
60
New cards
Recognition rather than recall
Minimize the user's memory load by making objects, actions and options visible
61
New cards
Aesthetic and minimalist design
Dialogs should not contain information that is irrelevant or rarely needed.
62
New cards
Interviews
Are one of the most commonly used methods for collecting data in HCI researcher. Has: A definite purpose, is planned and organised, and an interviewer is responsible for the topics.
63
New cards
Semi-structured interview
Questions are more open ended, there often is a general framework of topics to be discussed.
64
New cards
Interview schedule
A structured set of questions that guide the interviewer.
65
New cards
Information sheet
A document describing the purpose of the interview, the participant's right to withdraw, and how data will be used after the study
66
New cards
EU General Data Protection Regulation (GDPR).
The storage of data collected during an interview is subject to this regulation inside of the European Union.
67
New cards
Consent form
A document where the participant provides permission for how they will participate in the study and how they want their data to be used. The participant can always withdraw from interview study.
68
New cards
Rapport
Can be built in interview by developing trust and mutual respect. The same goes for mutual understanding and cooperation between a user and a computer system during an interaction.
69
New cards
Requirements
They specify what is needed and how to know if it has been delivered but allow for freedom in how they are implemented. A statement of what a product or system should do or how it will do it. Should consider the needs of all stakeholders. Reduce costs and time in development, reduce confusion in communication, and provide good testing criteria for the final product.
70
New cards
A fit criterion
The measure of whether a requirement has been fulfilled is called.
71
New cards
Functional Requirements
Describes what a system should do and which tasks is should be able to perform.
72
New cards
User characteristics
Describe expected characteristics of the user group.
73
New cards
MoSCow
A prioritization technique used in project management and software development to prioritize requirements or tasks based on their importance or urgency. The name for this technique comes from the first letter of each word in the phrase "Must have, Should have, Could have, and Won't have."
74
New cards
Structured ideation process
Start with making sense of data. A structured problem-solving process based on the concept of time-based Sprints that build on a collection of ideas
75
New cards
Six thinking hats
A well known method to support decision making, communication and creative thinking. Each hat is a mode of thinking
76
New cards
Brainstorm
Designers and stakeholders/users together. Quantity is better than quality and no judgement. Is a creative problem-solving technique used to generate ideas and solutions through a group discussion
77
New cards
Sketching
Creating quick, freehand drawings or diagrams as a means of visualizing and exploring design ideas or concepts, and communicating them to others. Produce, refine and communicate ideas. This should be done early and often in the development process.
78
New cards
Prototype
A way for stakeholders to interact with a design, and test its suitability for their needs.
79
New cards
Wizard of Oz
Is a low fidelity prototyping technique. A person simulating the response of a design or software systems to end-user interaction.
80
New cards
Paper prototyping
Using pen and paper designs to simulate user interaction and flow.
81
New cards
High fidelity prototyping
Useful for testing functionality of a product and selling the design to others. Closer to the final product.
82
New cards
Fidelity
Refers to the level of detail and accuracy with which a design or prototype represents the final product or system.
83
New cards
Low fidelity prototyping
Quick, cheap, and easy to fail and recover. This prototyping technique is a quick way to check the functionality and interaction of an idea.
84
New cards
Storyboarding
Often low fidelity. Is visual representation of a sequence of events or story used to plan and organize a narrative, such as for a film, video game, or user experience
85
New cards
Usability testing
Evaluating a product or service by testing it with representative users. One central component is collecting data about users' performance on predefined tasks. Key issues to consider: The scope (what part you are testing), the purpose, and the tasks the users are to perform.
86
New cards
"think aloud" technique
Users speak what they do/think when testing a product or service. Understanding how the users are reasoning.
87
New cards
Ideation
The formation of ideas or concepts.
88
New cards
Design for error
Errors will happen. It is important to design for errors so it is easy for the user to undo the error
89
New cards
Test metrics
Quantitative measures used to estimate the progress, quality, productivity and health of the software testing process. For example: Number of successful task completions, number of critical errors made, and time on task.
90
New cards
Internet of things
States products can be connected to each other via the internet and interact with each other.
91
New cards
Technology as experience
Framework that accounts for the user experience in terms of how it is felt by the user.
92
New cards
Usability
Ensuring that products are easy to learn, effective to use, and enjoyable from the users perspective.
93
New cards
Outline feedback exchange
Systems that are used to target millions of users before publishing.
94
New cards
Cooperative design
When users and stakeholders are active participants in the design process
95
New cards
A/B testing
Evaluating different design options by presenting them to a pool of users
96
New cards
Highlights
Thumbnails at the top of browser that shows visited and saved sites.
97
New cards
Dialog box
Error messages and so on are presented through these.
98
New cards
Flat menus
A type of menu that displays a small number of options in an interface.
99
New cards
Expanding menus
The options of an interface are expanded so that they can be snown on a single screen.
100
New cards
Cascading menu
Provides secondary menu alongside a primary active drop down menu.