Student name Phan Nguyen Khanh Nguyen

Student ID ITCSIU21209

IT158IU - HUMAN COMPUTER INTERACTION (2023/2024)

Assisting tools for aging population

Length requirement: 4000 words
Number of words of this report: 4404 words
Members & contributions in the project
Name & ID Contributions

Phan Nguyễn Khánh Nguyên - ITCSIU21209 UI designer,UX Research, Interviewer,

Low-fi mockup smart watch device, Mid-fi
prototype, High-fi prototype[ Home,
Medications management, Schedule]

Lê Thu Hoàng - ITCSIU21063 UI designer, UX Research, Low-fidelity

mockup mobile device, Mid-fi prototype,
High-fi prototype[feature: Auth page, Docs
saver, Profile, AI assistant]

1 Introduction
● Interactive Figma file

This report presents the design, development, and usability testing of MedBuddy, a
mobile application designed to assist the aging population in managing their healthcare
needs. Our primary target audience is older adults who may face challenges in organizing
medications, tracking medical appointments, accessing medical documents, and staying
informed about their health.
MedBuddy aims to address these challenges by providing a user-friendly and accessible
platform with the following key features:

● Medication Management: Users can easily create and manage medication

schedules, set reminders, and track their medication adherence.
● Medical Document Storage: The app allows secure storage and organization of
important medical documents, making it simple for users to access their records
when needed.
● AI-Powered Chatbot: MedBuddy incorporates an AI-powered chatbot to answer
users' health-related questions, provide medication reminders, and offer
personalized health tips.
 ● Appointment Scheduling and Reminders: Users can schedule medical appointments
and set reminders automatically by AI or themself to ensure they don't miss
important visits.

Meeting User Needs and Wants:

MedBuddy is designed to meet the specific needs and wants of older adults by:

● Simplicity and Ease of Use: The app features a clean interface, large fonts,
high-contrast colors, and intuitive navigation.
● Accessibility Features: MedBuddy incorporates accessibility features such as voice
control and screen reader compatibility.
● Personalized Support: The AI chatbot provides personalized reminders, answers to
common health questions, and helpful tips.
● Peace of Mind: By centralizing medication management, medical records, and
appointment scheduling, MedBuddy provides users with greater control and peace
of mind.

Competitor Analysis:
While there are existing medication reminder apps and health management platforms,
MedBuddy differentiates itself by:

● Focus on Older Adults: The app is specifically designed to meet the unique needs
and preferences of older adults with an emphasis on accessibility and ease of use.
● AI Chatbot Integration: The integrated AI chatbot provides a personalized and
interactive layer of support that goes beyond basic reminders.
● Medical Document Management: MedBuddy's ability to store and manage medical
documents distinguishes it from simple medication reminder apps.
2 User Experience Design
2.1 User Personas
1. User Persona 1
● Name: Hoang Nam Tien
● Age: 60
● Family: Married
● Occupation: Business man
● Motivation: Tien is a busy businessman, prioritizes staying healthy to avoid
disruptions in his work and family life. He also recognizes the importance of accurate
data in drug trials and wants to ensure his medication adherence contributes
valuable results. Reducing stress by remembering medications and appointments
brings him peace of mind.
● Goal:
○ Take medication on time.
○ Need to be reminded about upcoming appointments.
● Frustrations:
○ Too busy with work.
○ Not good at keeping track of daily medication so that drug trials provide
accurate results.

2. User persona 2
 ● Name: Alex Turner
● Age: 80
● Family: Widower
● Occupation: Retired
● Motivation: Alex Turner desires to maintain his independence by managing his own
health. He seeks clear information about his medications to make informed
decisions. Alex is open to embracing technology, particularly when it offers features
like an AI assistant that can answer his health questions directly, potentially reducing
loneliness by providing a sense of companionship and support.
● Goal:
○ Overcome initial anxieties about using technology.
○ Simple instruction and receive straightforward answers about his
medications.
● Frustrations:
○ Being overwhelmed by technology, presented with too much information at
once.
○ Lack of readily available assistance or unclear instructions for getting help.

3. User persona 3.
● Name: Vivienne Westwood
● Age: 78
● Family: Married
● Occupation: House wife
● Impairment: Low vision
● Motivation: Vivienne Westwood is a housewife with low vision, wants to manage her
health independently, not relying on others for reminders or medical record access. A
user-friendly app can simplify the organization of her health information and boost
her confidence by allowing her to manage her health with greater control.
● Goal:
○ Utilize an app with features designed for user with low vision.
○ Centralize all medical information in a readily accessible format.
● Frustrations:
○ Inaccessible interface(e.g., small fonts, cluttered layout, etc).
○ Having to rely on someone else to read medication and remind taking
medication.

2.2 User Scenarios

Scenario 1: (Free User):
● Tien, a busy businessman, forgets to take his medication amidst his hectic work
schedule.
● He opens the app and receives a timely notification reminding him to take his midday
pills.
● The app displays clear instructions on dosage and potential side effects.
● He feels relieved knowing he's on track with his medication adherence, contributing
to accurate data in his ongoing drug trial participation.
● Later that week, Tien receives a notification about an upcoming doctor's
appointment he nearly overlooked.
 ● With a tap, he adds the appointment to his calendar and sets a reminder within the
app.
● Tien feels a sense of peace of mind with the app managing his medication schedule
and appointments, allowing him to focus on his work and family life.

Scenario 2:(Free User):

● Alex, a recently widowed retiree, feels overwhelmed by the prospect of using a new
app to manage his health.
● He hesitantly downloads the app and is greeted by a simple, user-friendly interface
with large fonts and clear instructions.
● He uploads a picture of his prescription medication using the app's camera function.
● The AI assistant analyzes the image and presents Alex with a clear explanation of the
medication's purpose, side effects, and potential interactions with other medications
he might be taking.
● Alex feels empowered by the easy-to-understand information and appreciates the
independence the app provides in managing his health.
● He decides to explore the app further, intrigued by the possibility of asking the AI
assistant questions in the future.

Scenario 3: (Free & Premium User):

● Vivienne struggles to manage her medications due to low vision.

● She downloads the app and is impressed by the accessibility features, including large
fonts, high-contrast themes, and text-to-speech functionality.
● She scans her prescriptions using the app, and the text-to-speech feature reads the
medication details aloud for her.
● Vivienne feels a sense of relief and newfound independence with all her medical
information organized and easily accessible in one place.
● Interested in additional features, she explores the app's premium membership
option. This tier offers advanced medication tracking with personalized reminders
and medication interaction reports.
● Vivienne decides to upgrade to the premium membership, feeling confident that the
additional features will further empower her to manage her health independently.

2.3 User Requirements

Must Have (M):

● Medication Reminders: Timely notifications for medication intake, including dosage

and visual icon.
● Medical Document Storage: Secure storage for scanned prescriptions, lab results,
and other medical documents.
 ● Accessibility Features: Interface designed for users with visual impairments,
including large fonts, high-contrast themes.
● AI Assistant (Free Users): Ability to answer basic questions about medications based
on uploaded information (e.g., purpose, side effects).

Should Have (S):

● Voice Control: Feature to set medication reminders, navigate the app, and interact
with the AI assistant using voice commands.
● Medication Tracking: Ability to track medication history, record adherence, and view
upcoming refills.
● AI Assistant - Advanced Functionality (Premium Users): Ability to ask more complex
questions about medications and health data, potentially offering insights and
recommendations.
● Appointment Booking: Option to directly schedule appointments with healthcare
providers within the app (Considered for future development)

Could Have (C):

● Integration with Wearable Health Trackers: Ability to connect with wearable devices
to automatically import health data (e.g., blood pressure, heart rate).
● Community Forum: Secure online forum for users to connect and share experiences.
● Telehealth Integration: Feature to connect with healthcare providers virtually for
consultations. (Considered for future development)

Won't Have (W):

● Complex Social Media Integration: Focus on core functionalities related to

medication management and avoid distractions of social media features.
● AI-powered Diagnostics: Avoid integrating features that could be misconstrued as
medical diagnosis, which requires a licensed professional.

2.4 Hierarchical Task Analysis

2.5 Paper prototypes (low-fidelity)
 In the stage of creating the low-fidelity prototype, the design of the app prioritizes
user-centered design principles to ensure a positive experience for senior users
managing their medications. Focusing on the core functionality of creating
medication reminders aligns with their primary need for adherence. The minimalist
interface minimizes clutter and emphasizes interaction through buttons, reducing the
need for complex typing. Additionally, incorporating visual medication icons caters to
users who might prefer visual identification over text descriptions. This user-centered
approach, prioritizing simplicity, clear interaction, and visual cues, lays the
foundation for a comprehensive medication management app

2.6 Digital wireframes

The functionalities presented in the medium-fidelity prototype represent a significant

advancement. . This iteration focuses on enriching the user experience by introducing new
functionalities and prioritizing accessibility features. Recognizing the sensitivity of health
information, a secure authentication step is incorporated to ensure user data remains
protected, fostering trust and peace of mind. The medium-fidelity prototype introduces
functionalities designed to empower users in managing their medications. An AI assistant is
introduced allowing users to set reminders, adjust dosages, or access medication
information with ease. To eliminate the need for physical documentation, the app enables
users to import or upload pictures of prescriptions and lab results, creating a centralized,
readily accessible repository for all their health information. The medium-fidelity prototype
explores additional accessibility features with increased text size.

2.7 High-fidelity prototype (mockup)

Building upon the iterative UX design process, the high-fidelity prototype takes user
experience to the next level. It refines the functionalities established in the low-fidelity stage
and the features introduced in the medium-fidelity version. This polished iteration prioritizes
usability for seniors through a user-centered design approach.
The interface utilizes a blue and white color scheme, proven through our research to be
favored by elderly users for its clarity and calmness. Layout adjustments optimize navigation,
with larger, well-labeled buttons minimizing the risk of accidental taps. These design
decisions directly address the needs of senior users, promoting findability and reducing
cognitive load.
Furthermore, the high-fidelity prototype embraces user empowerment by seamlessly
integrating with smartwatches. This functionality allows users to leverage their existing
wearable technology and potentially benefit from real-time health data import. Imagine
medication reminders adjusting based on real-time heart rate data or personalized insights
derived from combined medication and activity tracking. This integration fosters a more
holistic health management experience, a core tenet of user-centered healthcare app
design.
In essence, the high-fidelity prototype represents a significant advancement towards a
comprehensive healthcare management app that prioritizes user experience, specifically
catering to the needs and preferences of senior users.

3 Usability testing
3.1 Protocol
A. Session Location:

● In-person: Sessions will be conducted in a quiet and comfortable location within the
school library, in public places specifically designated for usability testing.
Participants will have access to a dedicated table and a laptop or tablet with the
MedBuddy Figma prototype loaded in a web browser.
● Remote: For remote sessions, participants will join a dedicated Discord voice
channel. Screen sharing will be enabled to observe their interactions with the
MedBuddy Figma prototype.

B. Tasks:
Task 1: Login with Phone Number

● Goal: The participant successfully navigates the Figma prototype to simulate the
login process using their phone number.
● Instructions:
● "Welcome! We're going to test out a prototype of the MedBuddy app in
Figma. Imagine you're using the app for the first time. Let's start by logging in
using your phone number. The app will send you a verification code."
● In-person: The researcher will be present to guide participants and answer
any questions.
● Remote: The researcher will provide clear instructions via Discord voice chat
and use screen sharing to point out key elements of the prototype.

Task 2: Use the AI Chatbot

● Goal: The participant successfully navigates the Figma prototype to interact with the
AI chatbot using both text and voice chat features to ask a question related to their
health or medication.
 ● Instructions:
● "Now, let's try out the 'Buddy Chat' feature. Click on the 'Buddy Chat' section.
Then, type or say a question you would like to ask the chatbot. If it's a voice
question, please click the microphone icon. Let me know what you notice
about the interaction."
● In-person: The researcher will be present to guide participants and answer
any questions.
● Remote: The researcher will provide clear instructions via Discord voice chat
and use screen sharing to point out key elements of the prototype.

Task 3: Add a New Medication

● Goal: The participant successfully navigates the Figma prototype to simulate adding a
new medication to their MedBuddy list by going through all the necessary steps,
including entering the medication name, type, strength, frequency, and dosage.
● Instructions:
● "Imagine you need to add a new medication. Click on the 'Add Medicine'
button. Now, please follow the steps to add a medication, entering the name,
type, strength, and frequency. If you can't actually add the medication
because it's a prototype, let me know what you would do or what you think
would happen next."
● In-person: The researcher will be present to guide participants and answer
any questions.
● Remote: The researcher will provide clear instructions via Discord voice chat
and use screen sharing to point out key elements of the prototype.

Task 4: Manage Daily Schedule

● Goal: The participant successfully navigates the Figma prototype to simulate

interacting with the daily schedule features for medical appointments, medication
logs, and medication taken.
● Instructions:
● "Please click on the 'Schedule' button. You'll see different sections for
appointments, medication logs, and medications taken. Explore the different
sections and let me know what you think about the information presented
and the way it's organized."
● In-person: The researcher will be present to guide participants and answer
any questions.
● Remote: The researcher will provide clear instructions via Discord voice chat
and use screen sharing to point out key elements of the prototype.

C. Equipment:
 ● In-person:
● Laptop or Tablet with a web browser to access the MedBuddy Figma
prototype.
● Pen and paper for note-taking (for the researcher).
● Remote:
● Laptop or Tablet with Discord and a web browser to access the MedBuddy
Figma prototype.
● Screen sharing enabled in Discord.
● Screen recording to capture the session.

3.2 Data collection methods

A. Qualitative Data Collection:

● Think-Aloud Protocol (Adapted): While we didn't provide specific tasks, we

encouraged participants to think aloud as they explored the app, saying things like,
"Just tell me what you're thinking and what you're trying to do." This approach,
based on the principles of cognitive walkthroughs (Nielsen & Molich, 1990), helped
us understand their thought process and identify areas of confusion.
● Observations: We took detailed observational notes throughout each session,
recording participants' actions, interactions, expressions of confusion, and any
positive or negative reactions to the app. This observational approach, rooted in
ethnographic methods (Spradley, 1980), allowed us to gain a deeper understanding
of how users naturally interacted with the app.
● Post-Session Interviews: After participants explored the prototype, we conducted
brief semi-structured interviews to gather their feedback and clarify any
observations. This is a common practice in usability testing, as described by Sauro &
Lewis (2016). We asked open-ended questions like:
● What did you find easiest to use?
● What did you find most difficult or confusing?
● What are your overall impressions of the app?
● Did you have any suggestions for improving the app?

B. Quantitative Data Collection:

● User Survey: We administered a structured user survey form at the conclusion of

each testing session. The survey included questions about the participant's
demographics, experience with similar apps, and their overall satisfaction with the
MedBuddy prototype. This survey followed the principles of user satisfaction
questionnaires (Brooke, 1996) and aimed to collect quantitative data about user
 opinions and preferences. Here are some examples of questions included in the
survey:
● How easy was it to find the information you were looking for?
● How clear were the instructions for using the app?
● How satisfied were you with the overall design of the app?
● Would you recommend this app to others?
● Task Completion Time: While we didn't give specific tasks, we did note the time it
took for participants to complete certain actions, such as logging in, adding a
medication, or navigating to the schedule. This approach is consistent with
task-based usability testing (Sauro & Lewis, 2016), allowing us to assess the
efficiency of specific user flows.
● Number of Errors: We recorded the number of errors or usability issues identified
during the session. This data, aligned with the principles of error analysis (Nielsen,
1994), provided insights into the potential for user errors and areas for improvement.

Rationale and Justification:

● Qualitative Methods (Think-aloud, Observations, Interviews): We chose these

methods because they allowed us to gather rich, qualitative data about user
experiences, particularly for older adults who may not be as familiar with technology
and might not easily articulate their challenges.
● Quantitative Methods (Survey, Task Completion Time, Errors): These methods
offered a structured way to collect quantitative data about user satisfaction,
efficiency, and potential for errors.

3.3 Participants
A. Demographics

● Number: Three participants completed the usability testing and evaluation.

● Age:
● Range: The age range of participants was 21 to 62 years old.
● Average (Median): The median age of the participants was 22 years old.
(We're using the median because the age range is so wide.)
● Gender: All three participants identified as male.
● Tech Experience:
● Two participants were computer science students with high levels of
technology experience, comfortable using smartphones, apps, and digital
interfaces.
● One participant (age 62) had no prior experience with smartphones or health
apps, representing a less tech-savvy user group.
 ● Other Relevant Demographics:
● One participant (age 21) was a university student living off-campus.
● One participant (age 22) was a recent graduate and living with family.
● One participant (age 62) was retired.

B. Recruitment Process:

● Location: Participants were recruited from various locations to capture a range of

demographics and tech experience:
● The school's library (to reach students).
● A public area with high foot traffic (to reach older adults).
● A Discord server for computer science students.
● Methods:
● Direct Approach: We approached individuals in the public area and provided
a brief explanation of the study, inviting them to participate.
● Direct Messages: We sent direct messages to friends, asking for their
participation.
● Informed Consent: All participants were provided with the Informed Consent Form
and provided their sign consent before participating in the study.
● Evaluation Form: After completing the usability testing session, participants were
given an evaluation form to provide feedback on their experience.
● Incentives: Participants were offered candy as a small token of appreciation for their
time.
3.4 Results
Evaluation form
A. Qualitative Results

● Overall Impressions: Participants generally found the MedBuddy app to have a clean
and visually appealing design. However, several aspects of the app's functionality
caused confusion, particularly for the participant with limited tech experience.
● Login and Onboarding: The login process using a phone number was straightforward
for all participants. However, there were suggestions for improving the onboarding
experience, such as providing a brief tutorial or walkthrough of the app's main
features.
● AI Chatbot: While the concept of the AI chatbot was well-received, participants
encountered challenges using both the text and voice input methods.
● Text Input: The text input field was small, making it difficult for some
participants to see what they were typing.
● Voice Input: The voice recognition was inconsistent, leading to frustration
when the chatbot misinterpreted spoken questions.
 ● Add Medication: Adding a new medication was identified as the most complex task.
● Terminology: Participants were unfamiliar with some of the medical terms
used, such as "frequency" and "dosage."
● Navigation: Navigating the multiple screens required to enter medication
details was confusing.
● Manage Daily Schedule: The "Schedule" feature received mixed feedback.
● Medication Log vs. Logged: Participants were unclear about the distinction
between these sections.
● Visual Clarity: Suggestions were made to improve the visual hierarchy and
make it easier to distinguish between appointments, medications due, and
medications taken.

B. Quantitative Results

● Task Completion Time: Due to the observational nature of the study, we did not
collect precise task completion times.
● Number of Errors: Error rates were not formally tracked. However, observational
notes indicate that the "Add Medication" task had the highest frequency of errors,
with participants struggling to enter information correctly and navigate between
screens.
● User Survey Data: Due to the small sample size (n=3), we are not reporting specific
statistical data from the user survey. However, general trends from the responses
include:
● Perceived Usefulness: Participants generally agreed that the MedBuddy app
could be useful for managing medications and medical information.
● Design Appeal: The app's design was rated as visually appealing.
● Usability Challenges: Participants indicated that some areas of the app were
confusing to use, particularly the "Add Medication" and "Schedule" features.

Moving Forward:
The findings from this usability testing session will be used to guide further iterations of the
MedBuddy prototype. We will prioritize addressing the usability issues identified,
particularly those related to clarity, navigation, and terminology, to ensure the app is
accessible and user-friendly for older adults.

[Report the main qualitative and quantitative results. Provide a summary if you have
extensive data. Include data in full as appendices.]

4 Analysis/Discussion
A. Recommendations for Improvement
Based on the usability testing findings, we recommend the following improvements to
enhance the MedBuddy app's usability, particularly for older adults:

● Simplify AI Chatbot Interactions:

● Larger Text Input: Increase the size of the text input field for better visibility.
● Voice Recognition Enhancements: Explore ways to improve the voice
recognition accuracy of the AI chatbot. Consider providing visual feedback of
recognized words to aid users.
● Redesign Add Medication Feature:
● Simplified Terminology: Replace or clarify medical jargon with more
user-friendly language (e.g., "how often you take it" instead of "frequency").
● Streamlined Navigation: Reduce the number of screens required to add a new
medication or use a stepped approach with clear progress indicators.
● Enhance Schedule Feature Clarity:
● Clearer Section Labels: Use more descriptive labels for the "Medication Log"
and "Logged" sections (e.g., "Medications Due Today" and "Medications
Taken").
● Visual Distinctions: Employ different colors, icons, or font sizes to visually
distinguish between appointments, medications due, and medications taken.

B. Alternative Usability Testing Techniques

In addition to the observational methods and user survey, we could have employed the
following usability testing techniques to further evaluate the MedBuddy app prototype:

● Heuristic Evaluation: In this method, usability experts would evaluate the interface
against established usability heuristics (Nielsen, 1994), identifying potential issues
without involving users directly. This is a cost-effective approach for early-stage
testing.
● Eye Tracking: Eye-tracking technology could be used to track participants' eye
movements as they interact with the app, providing insights into their visual
attention and identifying areas of interest or confusion.
● A/B Testing: For specific design decisions, we could use A/B testing to compare
different versions of a feature or screen (e.g., different layouts for the "Schedule"
section). This would allow us to collect quantitative data on user preferences and
task success rates.

C. Strengths and Weaknesses of Approaches

Technique Strengths Weaknesses
Observational Captures natural user Can be subjective; may not reveal all
Testing behavior; provides rich usability issues.
qualitative data.
User Survey Gather quantitative data; easy Responses may be biased; limited
to administer. depth of insights.
Heuristic Cost-effective; identifies major Relies on expert judgment; may not
Evaluation usability issues early. reflect actual user behavior.
Eye Tracking Provides objective data on Can be expensive; requires specialized
visual attention; reveals areas equipment; may not explain "why"
of focus. users look.
A/B Testing Quantifies user preferences; Can be time-consuming; requires a
compares different design sufficient user base for meaningful
options. results.

D. Limitations
It is important to acknowledge the limitations of our usability testing. Our small sample size
(n=3) and the lack of older adult participants in this round of testing limit the generalizability
of our findings. Future testing should prioritize recruiting a larger and more diverse group of
participants, particularly older adults who represent our target user group.

E. Moving Forward
This usability testing session has provided valuable insights for improving the MedBuddy
app's design and functionality. By implementing the recommended changes and conducting
further testing with a wider range of users, we can create a more accessible, effective, and
user-friendly app that empowers older adults to manage their healthcare needs.

References
● Brooke, J. 1996. SUS - a 'quick and dirty' usability scale. In: Jordan, P.W., Thomas, B.,
Weerdmeester, B.A. and McClelland, I.L. eds. Usability Evaluation in Industry.
London: Taylor & Francis, pp.189-194.
● Nielsen, J. 1994. Usability Engineering. San Francisco: Morgan Kaufmann.
● Nielsen, J. and Molich, R. 1990. Heuristic evaluation of user interfaces. In:
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI
'90). Seattle, WA, 1-5 April. New York: ACM, pp.249-256.
● Sauro, J. and Lewis, J.R. 2016. Quantifying the User Experience: Practical Statistics for
User Research. 2nd ed. San Francisco: Morgan Kaufmann.
● Spradley, J.P. 1980. Participant Observation. New York: Holt, Rinehart and Winston.
● Nielsen, J. 1994. Usability Engineering. San Francisco: Morgan Kaufmann.

Appendices
Appendix A: User Personas

● Include the detailed user persona templates for Hoang Nam Tien, Alex Turner, and
Vivienne Westwood (from Section 2.1).

Appendix B: User Scenarios

● Provide the full descriptions of the user scenarios you developed in Section 2.2:
Scenario 1 (Tien, free user), Scenario 2 (Alex, free user), and Scenario 3 (Vivienne,
free & premium user).

Appendix C: MoSCoW Requirements

● Include the complete MoSCoW (Must have, Should have, Could have, Won't have) list
of features and requirements from Section 2.3.

Appendix D: Hierarchical Task Analysis (HTA) Flowchart

● If you created an HTA flowchart (mentioned in 2.4), include it here.

Appendix E: Paper Prototypes (Low-Fidelity)

● Provide scans or photographs of your paper prototypes/sketches (from Section 2.5).

Label each prototype clearly.

Appendix F: Digital Wireframes

● Include screenshots of your Figma wireframes (from Section 2.6). Organize them
logically and provide clear captions or labels.

Appendix G: High-Fidelity Prototype (Mockups)

● Include screenshots of your Figma prototype, showcasing the final visual design
(from Section 2.7).

Appendix H: Usability Testing Materials

● Informed Consent Form: Include a copy of the Informed Consent Form that you used
(mentioned in your report).
● Evaluation Form: Provide the complete evaluation form that participants completed
(partially shown in Section 3.4).

Appendix I: Usability Testing Data

● Observational Notes: Provide your detailed observational notes from each usability
testing session.
● Evaluation Form Data (Raw): Include a table or spreadsheet with all the raw data
collected from the evaluation forms (including the pages you showed in Section 3.4).