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
Q

Information Diagram

A

Hierarchical representation of documentation (e.g. instructions, dependencies and procedures)

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

Organizational Diagram

A

Hierarchical representation of people and their roles in an organisation.

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

System Diagram

A

Representation of how data is transformed through processes and activities in the system.

Describes data activities, transformations and mapping out processes.

28
Q

Process Diagram

A

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
Q

Communication Diagram

A

Represent flow of information between users.

Nodes represent users or user groups, and the links represent the flow of information.

30
Q

AI Systems -
Principles

A
  • Privacy
  • Transparency and explainability
  • Accountability
  • Fairness and non-discrimination
  • Human control of technology
  • Professional responsibility
31
Q

Analysis paralysis

A

A state where decision making is halted or slowed, due to fear of making an error or missing out on a superior solution.

32
Q

Interactive Systems -
Challenges

A
  • Design fixation
  • Informed trade-off decisions
  • Communication between teams
  • Integration
  • Risk management
33
Q

Design Engineering -
Steps

A
  • 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
Q

Properties of useful requirements

A
  • Solution independent
  • Clear
  • Concise
  • Testable
  • Traceable
35
Q

Function analysis systems technique (FAST)

A

Decomposes higher-order functions into several lower order functions that may be easier to implement.

Horizontal: level of abstraction
Vertical: time

36
Q

Morphologic charts

A

Table in which every row maps a specific function to a set of candidate function carriers, often referred to as solutions.

37
Q

Concept evaluation

A

Score conceptual designs (combinations of solutions) against a relevant criteria.

A linear combination of scores (estimated) and criteria weightings (user research)

38
Q

Verification

A

Process of ensuring requirements are met.

39
Q

Validation

A

Process of ensuring the system is fulfilling its purpose for the intended users.

40
Q

Types of human error

A
  • Mistakes due to formulation of an incorrect intention
  • Slips due to failing to carry out the action correctly.
41
Q

Causes of human error

A
  • Lack of knowledge
  • Inexperience
42
Q

Risk formula

A

Likelihood (probability) * Impact (expected loss)

43
Q

Risk management process

A
  • Hazard identification
  • Risk estimation: likelihood/severity
  • Risk evaluation: risks are acceptable?
  • Risk control: reduce to acceptable levels
  • Risk monitoring
44
Q

System mapping

A

Allows us to describe a system in terms of its processes, people, and flow of information.

45
Q

Design engineering for HCI

A

Systematic method for designing and building products that has aspects within in it that are applicable in HCI.

46
Q

Design engineering challenges -
Design fixation

A

When we fail to fully explore design options, we often do not end up identifying the best solutions.

47
Q

Design engineering challenges -
Making informed trade-off decisions

A

An integrated system often has many design factors that have a negative correlation.

e.g. usability vs security (levels of authentication)

48
Q

Design engineering challenges -
Communication

A

Integrated design of an HCI system needs coordination of multiple people.

49
Q

Design engineering challenges -
Integration

A

Managing multiple technical disciplines, design knowledge, people, business and regulatory concerns into a functioning system.

50
Q

Design engineering challenges -
Risk management

A

Ensuring HCI systems are safe and risk levels are managed.

51
Q

High-level verification methods -
Inspection

A

Using one or several of the five senses to ensure a system possesses a certain quality.

52
Q

High-level verification methods -
Demonstration

A

Ensuring that manipulating the system according to its intended use results in expected outcomes.

53
Q

High-level verification methods -
Testing

A

Checking that feeding predefined inputs yields expected outputs.

54
Q

High-level verification methods -
Analysis

A

Carrying out verification using calculations, models or testing equipment.

55
Q

Structured what-if technique (SWIFT)

A

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
Q

Failure mode and effects analysis (FMEA)

A

Used to analyze human error at both the individual and the team level.

57
Q

Aspects of Engineering

A
  • Building the right thing
  • Building the thing right
  • Verification and validation
  • Systems
  • Understanding risks
  • Managing the process
  • Approaches to HCI design problems
58
Q

Properties of systems

A
  • Coupled
  • Emergent
  • Complex
59
Q

Systems approach principles

A
  • 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
Q

Types of diagrams

A
  • Task diagram
  • System diagram
  • Process diagram
  • Organizational diagram
  • Communication diagram
  • Information diagram
61
Q

Design engineering challenges

A
  • Design fixation
  • Making important tradeoff decisions
  • Communication
  • Integration
  • Risk management
62
Q

High-level verification methods

A
  • Inspection
  • Demonstration
  • Analysis
  • Testing
63
Q

Skills, Rules, and Knowledge (SRK) Model

A

A framework for understanding the performance of skilled users.

64
Q

SRK Model -
Skill-based behaviour

A

Skill-based behaviour emerges following a user having an intention: such behaviour has high automaticity and happens without conscious control.

65
Q

SRK Model -
Rule-based behaviour

A

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
Q

SRK Model -
Knowledge-based behaviour

A

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
Q

SRK Model -
Traits

A
  • 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.
© 2024 Bold Learning Solutions. Terms and Conditions