BAB 3 THE DESIGN PROCESS PART 1 Flashcards

1
Q

What are the universal methods of design approach? (5)

A

Planning, Scoping, and Defining:

What do we want to do? Determine the goals and scope of the project. (what is wanted/needed)

Exploration, Synthesis, and Design Implications:

Would it work? Would it solve the problem? Explore and synthesize ideas to see if they address the problem. (analysis)

Concept Generation:

Create a prototype and try it out. Develop a prototype to test the concept. (design)

Evaluation, Refinement, and Production:

Build it, test it, fix it. Evaluate and refine the design based on testing. (prototyping)

Launch, Monitor, and Iterate:

See if it works in the real world, with real users, and perform ongoing review and iteration. Launch the product, monitor its performance, and continuously improve based on user feedback. (implement and deploy)

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

What is the difference between features and requirements?

A

Features: Specific functionalities or characteristics of a product.

Requirements: Goals that the system needs to accomplish.

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

Why is it important to distinguish between features and requirements?

A

Focusing on requirements ensures the design process addresses the underlying problem and meets users’ needs effectively, rather than being constrained by specific preconceived solutions.

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

How can feature requests be shifted to requirements?

A

Identify the goals behind the feature requests.

Frame these goals as requirements that need to be met, rather than specific solutions to implement.

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

Can you provide an example of shifting a feature request to a requirement

A

Feature Request: Build an app for new UG1 and MSc students that lists course locations.

Requirement: Provide a way for new students to find course locations, ensuring the system can be used by various user groups, not just UG1 and MSc students.

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

What is a diary study and when should it be used?

A

Diary Study: A method where people record events as they happen.

When to Use:

Rare events: Events that cannot be easily observed.

Easily forgotten events: People often forget these events happen.

Actual frequency important: Accurate recording of how often something occurs.

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

Why might diary studies not be ideal?

A

Behavioral changes: Asking people to track their behavior can cause them to change it.

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

What is a retrospective survey and when is it appropriate to use it?

A

Retrospective Survey: A survey format asking people about past events.

When to Use:

Critical memorable events: Describe a negative software update experience.

Recent somewhat memorable events: Where did you have dinner last night?

Rare impactful events: How did your husband propose to you?

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

Why might retrospective surveys be ineffective?

A

Hard to remember events: People might struggle to recall specific details, such as how many times they crossed a road last month.

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

What is artifact analysis and when should it be employed?

A

artifact Analysis: Studying physical objects left by people to understand their behavior.

When to Use:

Physical spaces: Workflows generate physical artifacts.

Tasks involving artifacts: Goal tasks create artifacts (e.g., Microsoft Word).

Interactions generating artifacts: Emails, social media posts, etc.

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

Why might artifact analysis not always be suitable?

A

Lack of meaningful artifacts: No relevant artifacts available.

Time efficiency: Faster methods to obtain the same information

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

What are focus groups and what are their pros and cons?

A

Focus Groups: Group discussions directed by a researcher.

Pros:

Group opinions on issues.

Efficient for testing early ideas/designs.

Identifying issues or conflicts.

Multi-constituent discussion.

Cons:

Dominance by assertive individuals.

Focus on opinions, not behaviors.

Limited sample size.

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

How should focus groups be designed?

A

Invite target users.

Prepare a list of discussion-promoting questions in advance.

Start with easy questions, then harder ones, and end with easy questions.

Mediate and learn from participants, keeping personal opinions out.

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

What are the uses of focus groups in design?

A

Design requirements: Understand users’ current situation and needs.

Product idea testing: Test product concepts and mock-ups.

Finished product opinion gathering: Determine user feelings and usage of an already released product.

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

What is an interview and what are its key features? (7)

A

Interview: A formal or semi-formal conversation for gathering information.

Key Features:

Assessment of fit for the study.

Personal face-to-face interaction.

Opportunity for clarification and elaboration.

Potential for gaining unexpected insights and new directions.

Subjectivity and personal biases.

Nervousness and anxiety.

Time and resource-intensive.

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

What are the different structures of interviews? (3)

A

Unstructured Interviews:

No advanced planning.

Rich data but not replicable.

Structured Interviews:

Tightly scripted.

Comparable and replicable data.

Semi-structured Interviews:

Script of topics/questions.

Somewhat comparable and replicable.

17
Q

When should unstructured interviews be used, and what are their pros and cons?

A

When to Use: When there is little understanding of the topic.

Pros:

High flexibility.

Participant does most of the talking.

Cons:

High chance of missing important things.

Challenging to identify follow-ups in real time.

Unstructured data, hard to analyze.

18
Q

When are structured interviews appropriate, and what are their pros and cons?

A

When to Use: When the topic is well understood, and structured data is needed.

Pros:

Well-defined script.

Easy replication and analysis.

Cons:

Inflexible, no follow-ups.

Difficulty in identifying correct questions/answers.

19
Q

What is a semi-structured interview, and what are its pros and cons?

A

When to Use: When key areas are known but exact responses are unpredictable.

Pros:

Ensures coverage of key topics.

Some replication possible.

Structured by topic.

Cons:

May miss key ideas not in the script

Limited time for follow-ups.

20
Q

How should an interview be conducted?

A

Overview: Explain research purpose and interview goals.

Notification and Consent: State data collection methods, show equipment, explain data use, and obtain consent.

Simple Questions: Start with easy questions to put the participant at ease.

Main Interview: Focus on the participant, avoid leading questions.

Thank the Participant: End with a chance for additional comments and thank them for their time.

21
Q
A