Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Engineering and Design > HCI 7) Engineering > Flashcards

HCI 7) Engineering Flashcards

1
Q

Aspects of Engineering - Building the right thing

A

Clarifying the task, including arriving at a solution-neutral problem statement.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Solution-neutral problem statement

A

Statement that specifies the problem, leaving the solution completely open.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Aspects of Engineering - Building the thing right

A

Understanding requirements and managing changes throughout a project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Aspects of Engineering -
Verification and validation

A

Ensuring requirement are met and that a system is fit for purpose.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Aspects of Engineering -
Systems

A

Understanding how interactive systems interact with other systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Aspects of Engineering -
Understanding risks

A

Ensuring risks are understood and managed, and users are protected from harm.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Aspects of Engineering -
Managing the process

A

Following a systematic design engineering process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Aspects of Engineering -
Approaches to HCI design problems

A

Modelling interaction using some formal model to allow for inference, optimization, and verification.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Example:
Door handle system components

A

Fittings, screws, a plate, a handle, and its interaction with another system, the door, which interacts with various other systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Properties of systems -
Complexity

A

They have many dependencies with other systems and entities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Properties of systems -
Multiple levels

A

Ranging from low-level hardware interaction to interfacing with software libraries.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Properties of systems -
Coupled

A

They depend and rely on each other in various ways.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Properties of systems -
Emergent properties

A

They give rise to effects that are more than the sum of their parts.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Interactive Systems -
Functions

A
  • Receive and respond to input events via its sensors
  • Perform computations
  • Maintain and update its state
  • Display its output
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Interactive Systems -
Properties

A
  • Coupled system connecting the user with a compute
  • Reliant on subsystems including sensors, displays and computations
  • Embedded within a wider system providing context for interaction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Systems approach

A

A systems approach allows designers to reason about systems.
Considers design across the entire life cycle of the system: design, implementation, management, maintenance, and disposal.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Systems approach principles -
Define, revise and pursue the purpose

A

Refine the problem and identify the cost, performance, timescale and risk involved when designing the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Systems approach principles -
Think holistic

A

Systems have boundaries. They are embedded within other systems and integrate multiple systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Systems approach principles -
Follow a systematic procedure

A

Systems are planned, designed, and built.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Systems approach principles -
Be creative

A

Use innovative and conventional thinking to understand what the system must achieve.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Systems approach principles -
Take account of the people

A

People are part of the systems, and they are critical for the success of systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Systems approach principles -
Manage the project and relationships

A

Systems need to be designed to take all relevant factors into consideration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Systems Approach - Failures

A
  • Consider the environment the system operates in
  • Understand the non-technical factors (organizational, political, economic)
  • Address planned and unplanned interactions between system components
  • Part of wider user experience system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Task Diagram

A

Hierarchical representation of tasks and the necessary conditions for carrying out the tasks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Information Diagram
Hierarchical representation of documentation (e.g. instructions, dependencies and procedures)
26
Organizational Diagram
Hierarchical representation of people and their roles in an organisation.
27
System Diagram
Representation of how data is transformed through processes and activities in the system. Describes data activities, transformations and mapping out processes.
28
Process Diagram
Serial and parallel processes and activities are structured as an ordered series of steps. Nodes represent steps in a process and links represent conditions to transition between steps.
29
Communication Diagram
Represent flow of information between users. Nodes represent users or user groups, and the links represent the flow of information.
30
AI Systems - Principles
- Privacy - Transparency and explainability - Accountability - Fairness and non-discrimination - Human control of technology - Professional responsibility
31
Analysis paralysis
A state where decision making is halted or slowed, due to fear of making an error or missing out on a superior solution.
32
Interactive Systems - Challenges
- Design fixation - Informed trade-off decisions - Communication between teams - Integration - Risk management
33
Design Engineering - Steps
- Identify purpose of HCI system - Create requirements spec - Arrive at conceptual design - Translate into an embodiment design - Implement into detail design ready for manufacture or deployment - Verify system meets requirements + validate usability for purpose
34
Properties of useful requirements
- Solution independent - Clear - Concise - Testable - Traceable
35
Function analysis systems technique (FAST)
Decomposes higher-order functions into several lower order functions that may be easier to implement. Horizontal: level of abstraction Vertical: time
36
Morphologic charts
Table in which every row maps a specific function to a set of candidate function carriers, often referred to as solutions.
37
Concept evaluation
Score conceptual designs (combinations of solutions) against a relevant criteria. A linear combination of scores (estimated) and criteria weightings (user research)
38
Verification
Process of ensuring requirements are met.
39
Validation
Process of ensuring the system is fulfilling its purpose for the intended users.
40
Types of human error
- Mistakes due to formulation of an incorrect intention - Slips due to failing to carry out the action correctly.
41
Causes of human error
- Lack of knowledge - Inexperience
42
Risk formula
Likelihood (probability) * Impact (expected loss)
43
Risk management process
- Hazard identification - Risk estimation: likelihood/severity - Risk evaluation: risks are acceptable? - Risk control: reduce to acceptable levels - Risk monitoring
44
System mapping
Allows us to describe a system in terms of its processes, people, and flow of information.
45
Design engineering for HCI
Systematic method for designing and building products that has aspects within in it that are applicable in HCI.
46
Design engineering challenges - Design fixation
When we fail to fully explore design options, we often do not end up identifying the best solutions.
47
Design engineering challenges - Making informed trade-off decisions
An integrated system often has many design factors that have a negative correlation. e.g. usability vs security (levels of authentication)
48
Design engineering challenges - Communication
Integrated design of an HCI system needs coordination of multiple people.
49
Design engineering challenges - Integration
Managing multiple technical disciplines, design knowledge, people, business and regulatory concerns into a functioning system.
50
Design engineering challenges - Risk management
Ensuring HCI systems are safe and risk levels are managed.
51
High-level verification methods - Inspection
Using one or several of the five senses to ensure a system possesses a certain quality.
52
High-level verification methods - Demonstration
Ensuring that manipulating the system according to its intended use results in expected outcomes.
53
High-level verification methods - Testing
Checking that feeding predefined inputs yields expected outputs.
54
High-level verification methods - Analysis
Carrying out verification using calculations, models or testing equipment.
55
Structured what-if technique (SWIFT)
Team-based risk assessment method that prompts the team with what-if questions to stimulate thinking about identifying risks and hazards in a system. Columns: identifier, what-if questions, hazards/risks, relevant controls, risk ranking, action notes
56
Failure mode and effects analysis (FMEA)
Used to analyze human error at both the individual and the team level.
57
Aspects of Engineering
- Building the right thing - Building the thing right - Verification and validation - Systems - Understanding risks - Managing the process - Approaches to HCI design problems
58
Properties of systems
- Coupled - Emergent - Complex
59
Systems approach principles
- Think holistic - Define, revise and pursue the purpose - Follow a systematic procedure - Be creative - Take account of the people - Manage the project and relationships
60
Types of diagrams
- Task diagram - System diagram - Process diagram - Organizational diagram - Communication diagram - Information diagram
61
Design engineering challenges
- Design fixation - Making important tradeoff decisions - Communication - Integration - Risk management
62
High-level verification methods
- Inspection - Demonstration - Analysis - Testing
63
Skills, Rules, and Knowledge (SRK) Model
A framework for understanding the performance of skilled users.
64
SRK Model - Skill-based behaviour
Skill-based behaviour emerges following a user having an intention: such behaviour has high automaticity and happens without conscious control.
65
SRK Model - Rule-based behaviour
Rule-based behavior is characterized by the user employing stored procedures or rules of the type ”if X then Y”: such rules can be learned or acquired by experience.
66
SRK Model - Knowledge-based behaviour
The user is faced with unfamiliar situations where the user has not developed any rules or knowledge for how to control the system: the user explicitly formulates a goal and develops a plan to achieve this goal, which may be evolved and carried out in a trial-and-error fashion or by contemplating the consequences of various actions.
67
SRK Model - Traits
- Signals: are low-level continuous control signals (S) - Signs: represent perceived information that guides user's activation of actions (R) - Symbols: relate concepts to functional properties of the system to conceive a plan to achieve a goal

Software Engineering and Design (11 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions