Module 3:- Identifying needs and

establishing requirements

Introduction

Discovering requirements is essential in interaction design, focusing on understanding the problem space and
defining what will be developed. Key aspects include:

 Understanding target users and their capabilities.

 Identifying how a product can support users in their daily lives.
 Analyzing users' current tasks, goals, and contexts.
 Recognizing constraints on product performance.

This understanding forms the foundation for product requirements, guiding design and construction. In iterative
development cycles, requirements, design, and evaluation are closely intertwined, with each activity having distinct
goals necessary for producing quality products.

What, How, and Why?

Purpose of the Requirements Activity

The requirements activity is part of the initial phases of the double diamond design process, focusing on exploring
the problem space and establishing product descriptions. Techniques for capturing requirements include:

 Targeted activities.
 Product evaluation and prototyping.

Requirements evolve through stakeholder interactions and are revisited throughout the design lifecycle.

How to Capture Requirements

Requirements can be captured in various forms, such as:

 Prototypes for products like exercise monitoring apps.

 Structured notations for complex systems like process control software.

Explicitly capturing requirements is crucial to avoid losing key information during iterations. Different notations
emphasize various characteristics, leading to diverse representations, including diagrams and user stories.

Why Bother? Avoiding Miscommunication

Clear communication of requirements is vital for creating usable products. Miscommunication can lead to unusable
or inappropriate products, disappointing stakeholders. An iterative user-centered approach helps mitigate
misunderstandings by involving diverse perspectives and ensuring agreement on requirements.

What Are Requirements?

Requirements are statements about an intended product, specifying expected functionalities or performance. They
can vary in precision, from specific metrics (e.g., loading time for a GPS app) to broader user appeal (e.g.,
attractiveness to teenagers). The requirements activity aims to identify, clarify, and capture these requirements
iteratively, including criteria for fulfillment.

Requirements can be expressed using structures like the atomic requirements shell, which includes fields for fit
criteria, customer satisfaction, and priority. User stories are another method for capturing requirements, representing
customer-visible functionality and facilitating discussions among team members.

Different Kinds of Requirements

Requirements can be categorized into functional and nonfunctional types:

 Functional Requirements: Describe what the product will do (e.g., a video game being challenging).
 Nonfunctional Requirements: Describe product characteristics (e.g., compatibility with various
platforms).

Other types of requirements include:

 Data Requirements
 Environmental Requirements
 User Characteristics
 Usability Goals
 User Experience Goals

Data Gathering for Requirements

Data gathering involves understanding intended users, their activities, goals, and the context of use. Techniques
include:

 Interviews
 Observation
 Questionnaires
 Documentation review
 Researching existing products

Using multiple data gathering techniques provides diverse perspectives, enhancing the understanding of
requirements. Examples include using observation for context and interviews for specific user insights.

Activity Example

Consider key requirements for two scenarios:

1. Interactive Product for Navigating a Shopping Center:

o Functional: Locate places and provide routes.
o Data: Access to GPS and shopping center maps.
o Environmental: Design for noisy, busy settings.
o User Characteristics: Diverse user abilities and preferences.
o Usability Goals: Easy to learn and efficient.
o User Experience Goals: Satisfying and helpful.
2. Wearable Product for Measuring Glucose Levels:
o Functional: Measure glucose from blood samples.
 o Data: Display glucose readings accurately.
o Environmental: Usable in various conditions.
o User Characteristics: Novice to regular users.
o Usability Goals: Effective and safe to use.
o User Experience Goals: Clear and unambiguous outputs.

Data Gathering Techniques in Interaction Design

Introduction

Data is ubiquitous in today's world, often leading to the notion that we are overwhelmed by it. Data encompasses
various forms such as numbers, words, measurements, descriptions, and multimedia content that aid in
understanding design, user needs, and behavior. It can be categorized into quantitative data (e.g., time taken to find
information) and qualitative data (e.g., user comments). This chapter focuses on data gathering techniques essential
for interaction design, particularly in discovering requirements and evaluating user reactions.

Data Gathering Techniques

This chapter introduces three primary techniques for data gathering: interviews, questionnaires, and observation.
Each technique can be employed with minimal technical skills and can yield both qualitative and quantitative data.
The chapter also emphasizes the importance of combining these techniques to mitigate biases inherent in any single
approach.

Five Key Issues in Data Gathering

Successful data gathering hinges on five critical issues:

1. Setting Goals: Clearly defined goals guide the data gathering process, influencing the techniques used and
the analysis performed.
2. Identifying Participants: The target population must be defined based on the study goals, with sampling
methods chosen accordingly (probability vs. nonprobability sampling).
3. Relationship with Participants: Establishing a professional relationship between data collectors and
providers is crucial, often formalized through informed consent forms.
4. Triangulation: This involves investigating a phenomenon from multiple perspectives to enhance
reliability, including data, investigator, theory, and methodological triangulation.
5. Pilot Studies: Conducting a small trial run of the main study helps identify potential issues before the
actual data gathering begins.

Setting Goals

Goals for data gathering should be specific and clear, influencing the nature of the sessions and the analysis. They
can be expressed informally or formally, depending on the context.

Identifying Participants

Participants should be selected based on the study's goals, with methods such as saturation sampling, probability
sampling (random or stratified), and nonprobability sampling (convenience or volunteer panels) employed. The
choice of sampling method affects the ability to generalize findings.

Relationship with Participants

Maintaining a professional relationship with participants is essential. Informed consent forms are often used to
clarify the study's purpose and ensure data privacy. This is particularly important when working with vulnerable
populations, such as children or individuals with disabilities.

Triangulation

Triangulation enhances the validity of findings by using multiple data sources, researchers, theoretical frameworks,
or methods. While true triangulation can be challenging, employing various techniques and analyses is considered
good practice.

Pilot Studies

Pilot studies serve as preliminary tests to ensure the viability of the main study's methods. They help identify
potential issues, such as unclear questions or logistical challenges, before full-scale data collection.

Data, Information, and Conclusions

Understanding the distinction between raw data, information, and conclusions is vital. Data is collected and
analyzed to produce information, which then informs conclusions and actions. For example, in a study assessing a
new screen layout for a leisure center, data might include booking times and user comments, leading to insights
about user experiences and potential design improvements.

Data Recording
Effective data recording is crucial for analysis and sharing results. Various methods exist, including notes,
photographs, and audio/video recordings. The choice of recording method depends on the study's goals, context, and
sensitivity of the situation.

Notes Plus Photographs

Taking notes is a flexible and non-intrusive way to record data. While handwritten notes can be transcribed for
analysis, they may also help researchers focus on key points. However, challenges include potential biases and
difficulties in capturing highlights accurately. Collaborating with colleagues can mitigate some of these issues.

8.3.2 Audio Plus Photographs

Audio recording serves as a less intrusive alternative to note-taking, allowing observers to focus on activities rather
than capturing every spoken word. In interviews, it enables interviewers to concentrate on the interviewee.
Transcription of all data is not always necessary; often, only key sections are needed based on study goals. Audio
recordings can evoke strong memories and provide context for analysis. However, if audio is the primary data
collection method, quality is crucial, especially in remote interviews where connections may be poor. Photographs
often supplement audio recordings.

8.3.3 Video

Smartphones can capture short video clips, which are less obtrusive than professional cameras. However, for long-
duration recordings or complex interactions, professional equipment is more suitable. Systems like GoToMeeting
can record facial expressions and comments, but planning is needed to minimize intrusiveness while ensuring data
quality. Heath et al. (2010) suggest considering the following:

 Camera position: Fixed or roving, depending on the activity and purpose.

 Camera focus: Familiarize with the environment before recording to identify key areas.
  Participant impact: Assess if recording affects behavior, using empirical data.

8.4 Interviews

Interviews are structured as purposeful conversations and can be categorized into four types: open-ended
(unstructured), structured, semi-structured, and group interviews (focus groups). The choice of interview type
depends on the study's purpose and the interaction design activity.

8.4.1 Unstructured Interviews

Unstructured interviews are exploratory and resemble conversations, allowing for in-depth discussion. Interviewers
should have a plan for main topics to ensure coverage while remaining open to new ideas. They generate rich,
complex data but can be time-consuming to analyze.

8.4.2 Structured Interviews

Structured interviews use predetermined questions, ensuring standardization across participants. They are effective
when specific goals and questions are clear. Questions are typically closed-ended, allowing for quantitative analysis.

8.4.3 Semi-structured Interviews

Semi-structured interviews combine open and closed questions, allowing for guided discussion while covering
essential topics. Probing questions help elicit more information without introducing bias.

8.4.4 Focus Groups

Focus groups involve group discussions led by a facilitator, allowing for diverse perspectives. They are useful for
exploring shared issues but can be dominated by vocal participants. The format can be adapted to fit cultural
contexts.

8.4.5 Planning and Conducting an Interview

Planning involves developing questions, organizing documentation, and ensuring recording equipment works.
Questions should be clear, neutral, and avoid jargon. Interviewers should be aware of potential biases in responses.

8.5 Questionnaires

Questionnaires are effective for collecting demographic data and opinions, allowing for large-scale data collection.
They can be distributed electronically, making them accessible to remote participants. Careful design is crucial for
clarity and analysis.

8.5.1 Questionnaire Structure

Questionnaires typically start with demographic questions, followed by specific questions related to the study goals.
A checklist for designing questionnaires includes considering question order, clarity, and length.

8.5.2 Question and Response Format

Different formats can be used, such as checkboxes, rating scales, and open-ended questions. Likert scales and
semantic differential scales are common for measuring opinions and attitudes.
8.5.3 Administering Questionnaires

Ensuring a representative sample and reasonable response rates is essential. Online questionnaires offer advantages
like automatic data compilation but may face challenges in obtaining random samples.

8.6 Observation

Observation is valuable throughout product development, helping to understand user context and evaluate
prototypes. It can be direct (in the field) or indirect (through records). Each type has its advantages and challenges.

8.6.1 Direct Observation in the Field

Field observation provides insights into user behavior and context but can produce large amounts of data that may
be difficult to analyze. A clear focus is necessary to guide the observation process.

8.6.2 Direct Observation in Controlled Environments

Controlled environments allow for detailed observation of individual actions but may not reflect real-world usage. A
script can help standardize participant treatment.

8.6.3 Indirect Observation: Tracking Users’ Activities

Indirect observation methods include diaries and interaction logs. Diaries allow participants to record their activities,
while interaction logs automatically capture user actions. Both methods have advantages and limitations.

8.7 Choosing and Combining Techniques

Combining data gathering techniques provides multiple perspectives and enhances the richness of data collected.
The choice of techniques depends on study goals, participant characteristics, and available resources.

 Interviews: Good for exploring issues but may intimidate participants.

 Focus Groups: Collect multiple viewpoints but may have dominant characters.
 Questionnaires: Reach many people but require careful design.
 Direct Observation: Understand user context but can be time-consuming.
 Indirect Observation: Unobtrusive but may rely on participant accuracy.