# data[].attributes.body
B032410099

This lecture gives a clear overview of expert-led evaluation methods like heuristic evaluation and cognitive walkthroughs. It highlights their efficiency in spotting usability issues using Nielsen’s heuristics and WCAG standards. While tools like Google Analytics and A/B testing aid decisions, they have ethical and interpretive limits. Though cost-effective, these methods depend on expert judgment and don’t fully cover emerging tech like voice interfaces. Combining them with user feedback would give a fuller picture.

# data[].attributes.body
B032410099

The Week 13 lecture provides a comprehensive yet practical guide to UX requirements gathering, covering functional, data, user, and usability needs effectively. Its use of personas, scenarios, and contextual inquiry helps teams empathize with users, while creative methods like design fiction encourage innovative thinking. However, it could improve by addressing requirement prioritization, diverse user inclusion, and iterative adaptation more explicitly. Overall, it’s a strong foundation that would benefit from deeper real-world applicability and inclusivity.

# data[].attributes.body
The week's lecture provides a comprehensive toolkit for expert-led UX evaluation methods, though it has some notable gaps. The updated Nielsen heuristics remain practical for quick usability audits, but risk missing nuanced issues without user input. Accessibility evaluation using WCAG guidelines is particularly valuable for compliance-focused teams. Analytics and A/B testing offer scalable solutions, though ethical concerns about uninformed user participation need addressing. Fitts' Law proves useful for interface optimization but has limited application. While cognitive walkthroughs effectively assess learnability, the methods overly rely on expert knowledge, potentially excluding smaller teams. The lack of guidance for emerging technologies like AI and voice interfaces is a significant oversight. These inspection methods work best when combined with user testing to balance efficiency with real-user insights. Large organizations will benefit most from these structured approaches, while smaller teams may find the expert requirements prohibitive. The document succeeds in outlining efficient evaluation techniques but should emphasize more inclusive, user-centered validation to complement expert analyses.

# data[].attributes.body
The week's lecture effectively covers essential UX evaluation methods but has some gaps. The clear distinction between usability testing and experimental research is valuable for aligning methods with goals. Modern approaches like remote VR testing demonstrate adaptability, while traditional lab techniques remain relevant. However, the claim that 5 users suffice oversimplifies sample needs for complex products. The emphasis on ethics (informed consent) is commendable, but accessibility testing deserves more attention. Portable tools like eye-tracking glasses enable realistic studies, though uncontrolled "in-the-wild" research risks bias. Long-term deployment studies provide unique insights lab tests can't match. While robust overall, adding accessibility protocols and clearer sample size guidance would strengthen it. The blend of classic and contemporary methods makes this framework widely applicable across industries. Best suited for product teams needing practical usability insights and researchers conducting controlled experiments.

# data[].attributes.body
This week's lecture provides a strong foundation for design and prototyping but could better address modern digital tools and business realities. The emphasis on iterative prototyping and participatory design reflects industry best practices, particularly for inclusive solutions. While the coverage of physical computing (Arduino, LilyPad) is excellent, it underrepresents contemporary digital prototyping tools like Figma. The ethical consideration of Wizard-of-Oz prototyping demonstrates valuable self-awareness, though accessibility prototyping deserves more attention. The experience map variations and metaphor evaluation criteria offer particularly innovative, actionable guidance. This framework works best for academic or cross-functional teams needing shared prototyping language, but practitioners should supplement it with digital tool knowledge and business constraint strategies. The core philosophy - that prototyping is about learning rather than perfection - remains universally valuable.

# data[].attributes.body
This week 's lecture provides a solid toolkit for data analysis, with strong options like NVivo (qualitative) and R/SPSS (quantitative), though some tools may be overly complex or costly for small projects. Specialized tools like ELAN for interaction analysis are useful but niche. Missing are open-source alternatives (e.g., JASP, Taguette) that could improve accessibility. Ideal for well-resourced teams, but lighter options should be considered for agile workflows. Strengths: comprehensive coverage; Weakness: no guidance on scaling tools to project needs.

# data[].attributes.body
B032410099

https://dreamhoper.wixsite.com/portfolio

# data[].attributes.attachment_link.description
My field of study is in networking field such as vlan, trunking, dhcp, routing protocol and any otherskillsin CCNA Routing & Switching certificate. Besides, I also heve basic knowledge in windows server, c++, Java and Web development skilss. I'm willing tolearn and love to explore to gain more knowledge.

# data[].attributes.body
B032410099

The design, prototyping, and construction phase in HCI transforms user needs into practical solutions. It includes conceptual design (what users can do) and concrete design (visual and interaction details). Prototypes—low or high fidelity—help test ideas, gather feedback, and guide development. Tools like storyboards, metaphors, and experience maps support visualization. Finally, construction involves building systems using hardware kits (e.g., Arduino) or software tools (e.g., SDKs), enabling the move from design to real-world use.

# data[].attributes.body
B032410099

Various tools support data analysis in HCI. Excel, SPSS, R, and Python are used for quantitative analysis, while NVivo and Dedoose handle qualitative data like interviews and observations. Visualization tools like Tableau and Power BI help present insights clearly. These tools assist in understanding user needs and guiding design decisions.

# data[].attributes.body
B032410099

In Human-Computer Interaction (HCI), identifying needs and establishing requirements is a key step to ensure systems are user-centered and effective. This involves understanding what users want to do, how they currently perform tasks, and the context of use. Requirements describe what the system should do or how it should behave, including functional, data, environmental, usability, and user experience needs. Data is gathered through interviews, observations, surveys, and probes. Tools like personas, scenarios, and use cases help bring user needs to life and guide design. This process reduces miscommunication and helps create systems that are functional, usable, and satisfying.

# data[].attributes.body
B032410099

The purpose Identifying Needs is Understand what users want to achieve, how they work, and their environment. We can use the method is Interviews, observations, surveys, task analysis. This is focus to User goals, behavior, and context of use. The purpose of Establishing Requirements is Turn user needs into clear system requirements and type of requirement is Functional – What the system must do. Usability – How easy and efficient the system is. User – Specific user characteristics and needs. Environmental – The context in which the system is used. Accessibility – Inclusive design for all users.

# data[].attributes.body
Identifying needs and establishing requirements is a critical phase in product development that ensures the final solution aligns with user expectations and business goals. This process involves defining functional requirements (what the system should do), data requirements (what information to store), environmental factors (where and how it will be used), and user-centric needs (based on personas and scenarios). Effective techniques for gathering these requirements include interviews, surveys, observations, and analyzing existing documentation, while tools like personas, scenarios, and use cases help bring these requirements to life. By validating requirements early through prototypes or simulations, teams can prevent miscommunication, reduce costly redesigns, and create products that truly meet user needs. This structured approach is particularly valuable for UX designers, product managers, and developers working collaboratively on user-centered solutions.

# data[].attributes.body
B032410099

A Brain-Computer Interface (BCI), also known as a Brain-Machine Interface (BMI), is a technology that enables direct communication between the brain and an external device, such as a computer, prosthetic limb, or robotic system, without relying on traditional neuromuscular pathways (like nerves and muscles).

# data[].attributes.body
B032410099

A haptic device is a tool or interface that allows a user to interact with a computer or digital system through touch and physical feedback (known as haptics).

# data[].attributes.attachment_link.description
As a Year 1 Networking student, I possess a solid foundation in HTML, CSS, JavaScript, C++, and Cisco Packet Tracer. Throughout my studies, have successfully completed various projects in programming, multimedia, and data communication and networking. My goal is to secure an internship at a network-focused company while maintaining a CGPA of 3.7 upon graduation.

# data[].attributes.body
B032410099

Consistency

Keep elements uniform (e.g., colors, fonts, button styles) across the interface to improve usability and learnability.

Visibility

Make important elements (like navigation or call-to-action buttons) clearly visible to the user without unnecessary effort.

Feedback

Provide immediate and clear feedback for user actions (e.g., loading spinners, confirmation messages, error alerts).

Affordance

Design elements so their use is intuitive — e.g., buttons should look clickable, sliders should look draggable.

Simplicity

Avoid clutter. Present only what’s necessary to reduce cognitive load and make the interface easy to understand.

# data[].attributes.body
This week's lecture focuses on data gathering techniques to understand user needs and define system requirements. We'll learn how to plan and conduct sessions, effectively capture data, perform insightful interviews, design effective questionnaires, and apply various observation methods. Key topics include setting clear goals, understanding ethical considerations, and using triangulation to validate our findings.

# data[].attributes.body
BCI, or Brain-Computer Interface, is a technology that lets your brain directly control computers or other devices using your thoughts, without needing to move your body.

# data[].attributes.body
A haptic device is a gadget that lets you feel things in the digital world. It gives you touch feedback, like vibrations or pressure, so you can physically interact with virtual objects or computer systems.

# data[].attributes.body
5 UI Design Principles Made Simple

Visibility: Make sure users can easily see all the important stuff and what they can do.

Feedback: When users do something, the system should instantly show them that it happened.

Consistency: Keep things looking and acting the same throughout the entire system so users don't get confused and can learn faster.

Affordance: Design elements should hint at how they work (like a button looking like it can be pressed).

Constraints: Guide users to the right choices and stop them from making mistakes by limiting what they can do.

# data[].attributes.body
Emotional interaction is how we show, notice, and react to feelings when we communicate. It includes things like how we talk, our facial expressions, gestures, and the tone of our voice, all of which help us connect with others or with technology like computers and AI.

# data[].attributes.headline
MUHAMMAD FATEH ALI BIN MUHAMMAD MAJDI |B032410645|

# data[].attributes.subject
MUHAMMAD FATEH ALI BIN MUHAMMAD MAJDI |B032410645|

# data[].attributes.headline
MATHANABHARATHI A/L KRISHNAN (B032410807) 

# data[].attributes.subject
MATHANABHARATHI A/L KRISHNAN (B032410807) 

# data[].attributes.attachment_link.title
Mathanabharathi a/l Krishnan - Portfolio

# data[].attributes.attachment_link.description
Hello! I’m a 22-year-old passionate Computer Networks undergraduate at Universiti Teknikal Malaysia Melaka (UTeM). My enthusiasm lies in learning new technologies, solving problems, and contributing to exciting projects that bridge innovation with functionality. This digital portfolio showcases my academic journey, personal growth, and technical experiences. Enjoy exploring!

# data[].attributes.attachment_link.description
A Computer Science (computer Networking)Student

# data[].attributes.headline
MUHAMMAD LIWALNNASRI BIN LATIFF (B032410110)

# data[].attributes.subject
MUHAMMAD LIWALNNASRI BIN LATIFF (B032410110)

# data[].attributes.body
This stage involves creating early models of the product. Prototypes can be low-fidelity (paper sketches) or high-fidelity (interactive digital designs). It helps visualize ideas and test them before full development.

# data[].attributes.body
Tools like Microsoft Excel, SPSS, Google Forms, or data visualization software (like Tableau) help in organizing, analyzing, and interpreting user data collected from surveys, interviews, and observations.

# data[].attributes.body
After gathering data, this part focuses on turning those insights into clear, structured requirements. This guides the system’s design and ensures it meets user expectations and goals.

# data[].attributes.body
This step involves understanding the users, their environment, and what problems need solving. It includes interviews, observations, and collecting background information to know what users really need.

# data[].attributes.body
BCIs are systems that allow direct communication between the brain and a computer. They help users control devices using brain signals, often used for assistive technology in medical fields.

# data[].attributes.body
A haptic device is a tool or interface that gives physical feedback (like vibrations or force) to users. It simulates the sense of touch, often used in VR, mobile phones, or surgical simulations.

# data[].attributes.body
Five common design principles are:

Visibility: Users should know what actions are possible.

Feedback: The system should respond clearly to user actions.

Consistency: Similar actions should look and behave similarly.

Affordance: Design should suggest how it is used (e.g., a button looks clickable).

Simplicity: Interfaces should be clean and not overload users with choices.

# data[].attributes.body
Emotional interaction refers to how users emotionally connect with a system, product, or interface. It involves designing with feelings in mind—like joy, frustration, or trust—to create more human-centered and meaningful experiences.

# data[].attributes.body
Nyx - Portfolio & Agency Framer Template

# data[].attributes.attachment_link.title
Nyx - Portfolio & Agency Framer Template

# data[].attributes.attachment_link.description
Nyx is a sleek, modern portfolio and agency Framer template. Perfect for personal portfolios, design studios, and creative agencies.

# data[].attributes.body
https://anisftini.github.io/portfolio/

# data[].attributes.attachment_link.description
fascinated by computers and coding. I love solving problems with logic and building new programs. My goal is to use technology to create innovative solutions that help people.

# data[].attributes.headline
MUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.subject
MUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.body
https://eliyanarasid-b032410136.netlify.app/

# data[].attributes.headline
NUR IRDINA SYAMIMI BINTI HAMIZI (B032410164)

# data[].attributes.subject
NUR IRDINA SYAMIMI BINTI HAMIZI (B032410164)

# data[].attributes.body
https://irdinasyamimi.github.io/irdinahamizi-portfolio/

# data[].attributes.attachment_link.description
I’m passionate about building fast, secure, and stable networks. Whether it’s cabling, configuring switches, or optimizing wireless signals. I’m up for the challenge! My goal is to become a professional Network Engineer who can design, maintain, and secure efficient infrastructures.

# data[].attributes.headline
MOHAMMAD FAIQ BIN MOHD NAZARY (B032410169

# data[].attributes.subject
MOHAMMAD FAIQ BIN MOHD NAZARY (B032410169

# data[].attributes.attachment_link.description
I’m a passionate and dedicated student currently pursuing a Bachelor’s Degree in Computer Networking at UTeM. My journey in technology includes web development, networking, system design, and creative media work.

# data[].attributes.body
In Week 13, the focus is on designing the user interface, creating prototypes, and starting system construction. The design phase involves planning layout, navigation, and interaction based on user requirements. A prototype is then developed, which can be a low-fidelity sketch or a high-fidelity interactive model to test ideas. This allows users to give feedback before full development. Once the prototype is approved, the actual construction or coding of the system begins based on the final design.

# data[].attributes.body
In Part 3, the focus is on identifying tools that can support the analysis of collected data. Tools like spreadsheets (e.g., Microsoft Excel or Google Sheets) help organize and sort information easily. For more detailed analysis, qualitative tools like NVivo or ATLAS.ti are used to analyze interviews, notes, and open-ended responses. Survey platforms like Google Forms or SurveyMonkey can automatically generate summaries and charts. These tools help convert raw data into useful insights that guide the design process more effectively.

# data[].attributes.body
In Part 2, we focus on turning the gathered information into clear and usable requirements. This includes writing functional requirements, which describe what the system should do, and non-functional requirements, which cover performance, security, and design aspects. Scenarios and use cases are created to show how users will interact with the system. These help designers and developers understand user expectations. It is also important to check for any conflicting requirements and resolve them early. Finally, the requirements are reviewed and agreed upon by all stakeholders before the design process begins.

# data[].attributes.body
The first step in identifying needs and establishing requirements is to understand the problem that the system is meant to solve. It is important to involve all stakeholders, including users, clients, and developers, to get a full picture of what is needed. Information is gathered through methods like interviews, surveys, and observations. After collecting the data, it is analyzed to understand the users' goals and tasks. The most important requirements are then prioritized, documented clearly, and confirmed with users to ensure accuracy before moving forward with the design.

# data[].attributes.body
https://abinissri0713.wixsite.com/portfolio my portfolio project .

# data[].attributes.attachment_link.title
Dark Blue Simple Dark Tech and Gaming Bio-Link Website

# data[].attributes.body
Design, Prototyping & Construction is a key topic in HCI that focuses on building user-friendly systems.

Design is the stage where ideas and user interface layouts are planned based on user needs.

Prototyping involves creating a basic version of the system to test and improve design ideas.

Construction is the actual development stage where the final system is built using coding tools.

# data[].attributes.body
This week's lecture focuses on techniques for analyzing data to identify user needs and system requirements. It includes both quantitative and qualitative methods, discusses analytical frameworks, highlights common mistakes, and explains how to present findings effectively.

# data[].attributes.body
Identifying user needs and setting clear requirements in Human-Computer Interaction (HCI) is a crucial step in creating user-focused and efficient interfaces. This process includes collecting user information through techniques such as interviews, surveys, and direct observations to gain insight into their objectives, preferences, and difficulties. Clearly outlining functional, usability, and contextual needs allows designers to build systems that are user-friendly, accessible, and perform well. Incorporating ethical practices, using multiple data sources (triangulation), and conducting pilot studies further enhance the reliability of the findings and reduce misunderstandings. In the end, a thorough requirement analysis bridges the gap between technology and actual user expectations, leading to a better overall experience.

# data[].attributes.headline
FARA NAZZATUL AIN BINTI KAMARUZZAMAN B032410173

# data[].attributes.subject
FARA NAZZATUL AIN BINTI KAMARUZZAMAN B032410173

# data[].attributes.headline
Nuraleesha Sofia Binti Abdul Razak-B032410132

# data[].attributes.subject
Nuraleesha Sofia Binti Abdul Razak-B032410132

# data[].attributes.headline
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.subject
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.body
This week’s lecture talks about the steps after gathering and analyzing user needs. It focuses on how to design the system, create a prototype, and then build the final product. Design is where we plan how the system will look and work. Prototyping means making a simple version of the system to test with users. Construction is the process of actually building the full system. All these steps help make sure the final product matches what users want and works the way it should.

# data[].attributes.headline
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.subject
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.body
This week's lecture covers data analysis techniques for identifying user needs and system requirements. It explores quantitative methods and qualitative approaches. The session also addresses analytical frameworks, common pitfalls, and effective presentation of finding

# data[].attributes.headline
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.subject
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.body
After collecting information from users, the next step is to study and understand the data carefully. This helps us know what users really need and expect from the system. We then organize and decide which needs are most important. From there, we write clear and specific requirements for the system. These include what the system must do (functional requirements) and how well it should perform (non-functional requirements). All these requirements must match the users’ goals and the way they actually use the system. This process is important because it helps guide the design and makes sure the final system works well for the users.

# data[].attributes.headline
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.subject
NUR ELIYANA NATASYA BINTI ABD RASID (B032410136)

# data[].attributes.body
This week’s topic is about how to collect information to understand what users need in a system. Before we create anything, we must know what problems users face and what they want. To get this info, we can talk to them in interviews, give them surveys to fill in, or watch how they work. Each method helps us learn something different. When we do these sessions, we need to plan well and know what we want to ask, prepare properly, and write down what we learn. We also need to be fair and honest, like asking permission before recording or sharing answers. To make sure our data is correct, we can use more than one method and compare the results. All of this helps us build a system that fits what users really need.

# data[].attributes.attachment_link.description
Computer Science (Computer Network) Student

# data[].attributes.body
This week's lecture focuses on design, prototyping, and construction in interaction design. It covers prototyping techniques which is low/high fidelity, storyboards, Wizard-of-Oz, conceptual and concrete design and construction tools such as Arduino, SDKs. The goal is to translate ideas into tangible prototypes and final products.

# data[].attributes.body
This week's lecture covers data analysis techniques for identifying user needs and system requirements. It explores quantitative methods and qualitative approaches. The session also addresses analytical frameworks, common pitfalls, and effective presentation of findings.

# data[].attributes.body
Identifying needs and defining requirements is a vital step in project development. This process ensures the end result meets its objectives and satisfies stakeholder demands. It focuses on analyzing user requirements, setting clear project targets, and converting these insights into specific, practical guidelines.

# data[].attributes.body
Identifying needs and establishing requirements is a foundational step in user-centered design (UCD) and research. It involves gathering data to understand user behaviors, preferences, and challenges, which then informs the design of solutions. The process includes:

Data Gathering: Using techniques like interviews, questionnaires, and observations.

Analysis: Interpreting the collected data to extract meaningful insights.

Requirement Specification: Translating insights into clear, actionable requirements.

The methods for collecting data:

Interviews

Questionnaires

Observation

Ethnography

# data[].attributes.body
A Brain-Computer Interface (BCI) is a technology that enables direct communication between the brain and external devices without using muscles or nerves. It translates brain signals into actionable commands.

1. Signal Acquisition

Electrodes (invasive/non-invasive) detect brain activity (ex. EEG, fMRI).

2. Signal Processing

Algorithms decode brain signals (ex. "move left" or "type ‘A’").

3. Output Execution

Translated signals control devices (ex. robotic arms, wheelchairs, or software).

# data[].attributes.body
B032410130

Identifying needs and establishing requirements is a crucial process in any project, ensuring that the final product or system effectively addresses the intended purpose and stakeholder expectations. It involves understanding user needs, defining project goals, and translating these into clear, actionable requirements.

# data[].attributes.body
B032410130

This week lecture is focus on data gathering tecnique and identifying needs and establishing requirements involve understanding what users need and turn it to system goals. Its also conduct a survey such as google form, interview for collecting data for a research.

# data[].attributes.body
B032410130

A Brain-Computer Interface(BCI) is a system that allows direct communication between the brain and an external device, bypassing the body's natural pathways like muscles and nerves.

# data[].attributes.body
Kok Jia Hui - B032410121

Chiam Jing Wen - B032410130

Siew Hoi Wei - B032410135

Wong Chee Yong - B032410099

# data[].attributes.body
This week lecture is focus on requirements gathering (techniques for gathering, analyzing, and validating user requirements in system development). It covers methods like interviews, surveys, and observations, and emphasizes organizing and prioritizing requirements. The goal is to ensure clear, complete, and user-approved requirements before design begins.

# data[].attributes.body
This week lecture is focus on data gathering techniques for identifying needs and establishing requirements. It covers planning and running sessions, capturing data, conducting interviews, designing questionnaires, and observation methods. Key issues include setting goals, ethical considerations, and triangulation.

# data[].attributes.body
the focus is on analyzing gathered data to develop clear and specific design requirements. This includes organizing and prioritizing user needs, defining functional and non-functional requirements, and ensuring they align with user goals. It helps guide the design process and ensures the final product meets real user expectations and context of use.

# data[].attributes.body
Identifying needs and establishing requirements involves understanding what users need and turning those needs into clear system goals. It ensures the design is useful, user-friendly, and fits the user's context.

# data[].attributes.headline
FALISHA ESHAL BINTI ISMALIZAL B032410172 

# data[].attributes.subject
FALISHA ESHAL BINTI ISMALIZAL B032410172 

# data[].attributes.body
A Brain-Computer Interface (BCI) is a technology that enables direct communication between the brain and a computer system, without using traditional input methods like a keyboard or mouse. It works by detecting and interpreting brain signals (usually through EEG sensors) and translating them into commands for a device or software. In HCI, BCIs are especially useful for people with physical disabilities, allowing them to control computers, prosthetics, or other devices using only their thoughts.

# data[].attributes.headline
FALISHA  ESHAL BINTI ISMALIZAL B032410172 

# data[].attributes.subject
FALISHA  ESHAL BINTI ISMALIZAL B032410172 

# data[].attributes.body
A haptic device is a type of hardware that provides physical feedback to the user through the sense of touch. It allows users to feel vibrations, pressure, or movements when interacting with a system or virtual environment. In Human-Computer Interaction, haptic devices enhance user experience by making interactions more immersive and realistic. Examples include game controllers that vibrate, touchscreens with textured feedback, or surgical simulators that mimic real tissue resistance.

# data[].attributes.headline
FALISHA ESHAL BINTI ISMALIZAL B032410172 

# data[].attributes.subject
FALISHA ESHAL BINTI ISMALIZAL B032410172 

# data[].attributes.body
Consistency – Keep design elements (like buttons, fonts, layout) uniform across the interface to help users learn and predict system behavior easily.

Feedback – Provide clear responses to users’ actions (e.g., loading indicators, confirmation messages) so they know the system is working.

Visibility – Important functions and information should be easily noticeable without the user needing to search.

Affordance – Design elements should visually suggest how they are used (e.g., buttons should look clickable).

Error Prevention and Recovery – Minimize the chance of errors and provide easy ways for users to correct them when they occur.

# data[].attributes.headline
FALISHA ESHAL BINTI ISMALIZAL B032410172

# data[].attributes.subject
FALISHA ESHAL BINTI ISMALIZAL B032410172

# data[].attributes.body
Emotional interaction in Human-Computer Interaction (HCI) refers to how users emotionally connect with a system or product during use. It focuses on designing interfaces that not only function well but also evoke positive feelings like trust, satisfaction, or joy. Understanding users’ emotions helps designers create more engaging and meaningful experiences, as emotions influence decision-making, usability perception, and overall user satisfaction. A well-designed emotional interaction can improve user loyalty, while negative emotions may lead to frustration and product rejection.

# data[].attributes.body
TAN JING YI B032410145

NUR SYARI FARHANAH BINTI AFRIZAL B032410174

NUR AMANINA BINTI MOHD TAJAUDDIN B032410137

NUR IRDINA BINTI IDROS B032410163

# data[].attributes.body
1) ADAM DANIAL BIN RUDY AZDEE (B032410142)

2) MUHAMMAD AIMAN NAJMUDDIN BIN SUHAIMI (B02410134)

3) IMAN MUHAMMAD DANIAL BIN MOHAMMAD FAHRI (B032410124)

4) WAN MOHAMMAD AMMAR ISKANDAR BIN WAN ABDULLAH (B032410141)

# data[].attributes.body
Francis Chuah Kang Yi  B032410122

Tan Jun Wei  B032410154

Lim Wei Jian  B032410159

Ahmmed Md Reza  B032420172

# data[].attributes.body
Chong Zin Wen B032410081

Chang Wei Xian B032410117

Yong Vee Keat B032410114

Lee Wei Le B032410106

# data[].attributes.body
1. Identifying Needs

This step is about understanding the problem you are trying to solve and what the users really need (not just what they say they want).

Key Activities:

User research: interviews, surveys, observations, focus groups.

Contextual inquiry: studying users in their natural environment.

Task analysis: understanding what tasks users need to perform.

Stakeholder analysis: considering the needs of everyone involved (not just end users).

Goals:

Discover user goals, frustrations, and preferences.

Understand the environment where the product will be used.

Avoid making assumptions based on the designers' perspective.

Example:

Designing a mobile banking app:

Need: Secure access anytime and anywhere.

Insight: Users often try to check balances in low-signal areas.

Design consideration: Must work well with poor internet or offline caching.

2. Establishing Requirements

Once you've identified user needs, you translate them into clear, actionable system requirements.

Two Types of Requirements:

Functional Requirements

What the system should do.

Examples: "The system must allow users to log in with biometrics."

Non-Functional Requirements (Usability/UX)

How the system performs tasks.

Examples: "The system should respond within 2 seconds," or "The interface must be accessible to visually impaired users."

Key Tools:

Personas: fictional users to represent needs and behavior.

Scenarios: stories describing how personas interact with the system.

Use cases: formal descriptions of interactions.

Requirement documentation: capturing requirements in a shared format for design and development.

# data[].attributes.attachment_link.readable_text
Hello, Hi!!
My name is Sasmithaa Shanmugan, and I'm from the beautiful state of Selangor. I'm currently pursuing a Bachelor of Computer Science (Computer Networking) at Universiti Teknikal Malaysia Melaka (UTeM). I have a strong passion for UX and UI design, where I love crafting intuitive, user-centered interfaces and seamless digital experiences.

From wireframes to high-fidelity prototypes, I enjoy bringing ideas to life in ways that are both visually appealing and functionally effective. I'm always eager to learn and grow, whether it's through personal or group projects, exploring new design tools, or collaborating to solve real-world problems. I believe that great design is a blend of empathy, creativity, and continuous improvement and that's exactly what I strive for in every project I take on.

GET IN TOUCH

# data[].attributes.attachment_link.description
Hello, Hi!! My name is Sasmithaa Shanmugan, and I'm from the beautiful state of Selangor. I'm currently pursuing a Bachelor of Computer Science (Computer Networking) at Universiti Teknikal Malaysia Melaka (UTeM). I have a strong passion for UX and UI design, where I love crafting intuitive, user-centered interfaces and seamless digital experiences.

# data[].attributes.body
1.FARA NAZZATUL AIN BINTI KAMARUZZAMAN B032410173

2.NURALEESHA SOFIA BINTI ABDUL RAZAK B032410132

3.NUR SUFFIYAH HANNAH BINTI MOHAMAD JAIDI B032410009

# data[].attributes.body
Identifying needs and establishing requirements is an essential early stage in system development. It involves understanding what users need by using methods like interviews, surveys, and observations to define the problem and goals. These needs are then translated into clear system requirements, such as functional (what the system should do) and non-functional (how well it should perform). This step ensures the system meets user expectations and avoids wasted time and cost later on.

# data[].attributes.body
Identifying needs and establishing requirements in Human-Computer Interaction (HCI) is essential for designing effective user-centered interfaces. This process involves gathering user data through methods like interviews, questionnaires, and observations to understand their needs, goals, and challenges. By clearly defining functional, usability, and contextual requirements, designers ensure systems are intuitive, accessible, and efficient. Ethical considerations, triangulation of data sources, and pilot studies help improve accuracy and prevent miscommunication. Ultimately, a well-structured requirement analysis enhances user experience by aligning technology with real-world demands.

# data[].attributes.body
1) ADAM DANIAL BIN RUDY AZDEE (B032410142)

2) MUHAMMAD AIMAN NAJMUDDIN BIN SUHAIMI (B02410134)

3) IMAN MUHAMMAD DANIAL BIN MOHAMMAD FAHRI (B032410124)

4) WAN MOHAMMAD AMMAR ISKANDAR BIN WAN ABDULLAH (B032410141)

# data[].attributes.attachment_link.title
HCI_Lab 9_Applying Data Gathering Techniques

# data[].attributes.body
Francis Chuah Kang Yi  B032410122

Tan Jun Wei  B032410154

Lim Wei Jian  B032410159

Ahmmed Md Reza  B032420172

# data[].attributes.attachment_link.title
LAB 9 APPLYING DATA GATHERING TECHNIQUES

# data[].attributes.body
DANISH MUQRISH BIN MOHD NOOR AZMI B032410803

MATHANABHARATHI A/L KRISHNAN B032410807

THARAANIITHARAN A/L MOORTHY B032410076

# data[].attributes.attachment_link.title
LAB 9 APPLYING DATA GATHERING TECHNIQUES - HCI

# data[].attributes.body
This week lecture is focused on identifying user needs and establishing requirements through effective data gathering. Key aspects include setting goals, selecting participants, ensuring ethical practices, and using triangulation and pilot studies. Common methods include interviews (example: structured, semi-structured, or unstructured), questionnaires, and observations (example : direct, indirect, or ethnographic). Each method requires careful planning and can be adapted for different contexts, including remote settings. Combining techniques helps ensure more reliable and insightful results.

# data[].attributes.body
Kok Jia Hui - B032410121

Chiam Jing Wen - B032410130

Siew Hoi Wei - B032410135

Wong Chee Yong - B032410099

# data[].attributes.attachment_link.title
LAB 9_ APPLYING DATA GATHERING TECHNIQUES (G4)

# data[].attributes.body
GROUP MEMBERS :

KALAIMALAR A/P SUBRAMANIAM - B032410791

CHEN MING MIN - B032410800

DARSHINI A/P GOPAL KRISHNAN - B032410799

MARIAYANTI BINTI MAHRUDIN - B032410797

# data[].attributes.attachment_link.title
LAB 9 - APPLYING DATA GATHERING TECHNIQUES (G6)

# data[].attributes.body
MUHAMMAD FATEH ALI BIN MUHAMMAD MAJDI - B032410645

CHAN XI ER - B032410896

MUHAMMAD SYAHMI BAQIR BIN M SAHLAN - B032410789

# data[].attributes.body
1.FARA NAZZATUL AIN BINTI KAMARUZZAMAN B032410173

2.NURALEESHA SOFIA BINTI ABDUL RAZAK B032410132

3.NUR SUFFIYAH HANNAH BINTI MOHAMAD JAIDI B032410009