User Requirements

2 and its Analysis

Syllabus

2.1 Introduction to research and analysis tool (freeware) such as FigJam

Oualítative research, Quantitative research. Tools to
2.2 User requirements - Definition, Types of user research -
User/ Expert reviews
collect user requirements -personalobservation, interviews, questionnaire,
client requirements, Competitive analysis,
2.3 User requirement analysis- Understanding target audience and
Affinity mapping, Defining User Persona

2.1 Introduction to User Requirements and its Analysis

for creating an interface that is intuitive.
In user interface (U) design, analyzing user réquírements is crucial
functional, and meets the specific needs of users.
Here's how user requirements analysis is tailored to UI design:

1. Identifying User Requirements for UI Design

goals, technical
User Profiles and Personas : Define target users by understanding their demographics,
to visualize who
skílls, and preferences. Personas are fictional profiles representing typícal users, helping
will ínteract with the UI.
frequency, and their
Task Analysis : Identify what tasks users need to accomplish on the interface, their
complexity. This helps in designing layouts and workflows that simplify task completion.
Context of Use: Understand where, when, and on what devices the users will access the interface. This can
impact design choices such as responsiveness, accessibilíty, and color schemes.

2. Analyzing User Requirements

Functlonal Requirements : These describe specific actions users must be able to perform (e.g., searching,
navigating, filtering data). Functional requirements guide layout decisions and help prioritize which Ul
elements need prominence.
Non-functlonal Requirements : These cover factors like usability, accesibility, performance, and
aesthetic consistency. For instance, requirements for acessibílity may díctate the use of scren-reader
compatible labels and high-contrast colors.
Emotional Requirements: UI design often requires consideration of the user's emotional response.
For example, colors and shapes can evoke certain feelings and influence user engagement.
 UUX Design
2-2 User Requirerments and its Analysis
3. Translating Requirements into UI Speciflcations
Wireframes : Initial sketches that outline the structure and layout of pages
elements. Wireframes represent the basic arrangement of features to without specific design
ensure they align with user needs.
Mockups : Higher-fidelity visual representations that bring color,
typography, and design elements to
wireframes. Mockups help stakeholders visuallze how requirements translate into an
Interactive Prototypes : Allow users to click through elements and simulate real Interface.
are valuable for getting feedback on flow, Interactions. Prototypes
navlgation, and feature placement.
4. Validating UI Requirements
User Testing : Conduct usability testing with real users to observe
on the interface. This helps identify pain points or thelr Interactlons and gather feedback
confusing elements.
A/B Testing : Comparing two variations of a design with
better. This method refines Ul choices based on real user different user groups to see which one performs
responses.
Iterative Feedback Loops : Incorporate user feedback into multiple design
interface continually. Iterative improvements help ensure the Ul meets iterations to refine the
expectations.
evolving user requirements and
5. Documenting UI Requirements
UISpecification Document : This document includes
wireframes, design
component styling), and descriptionsof each element's functionality. AUl guidelines (e.g., ascolors, fonts,
developers to ensure alignment with user requirements. specification serves a guide for
Interaction Design Document : Details interactions such as hover states,
providing clarity on how users should experience the interface. transitions, and animations,

Example Elements in a UI Requirements Docurment

Navigation Structure: Hierarchy and labels for menus,submenus, and links.
Form Elements:Requirements for input fields,dropdowns, and buttons,
considering accessibilityneeds.
Error Handling: How errors will be displayed tousers, such as
error messages for invalid entries.
Feedback Mechanisms : Requirements for showing loading indicators, success
notifications, and confirmations.
Benefits of Effective UI Requirements Analysis
Enhanced User Satisfaction:Awell-analyzed UI meets user needs
experience.
intuitively, leading to a more satisfying
Reduced Development Time : Clear Ul requirements prevent costly redesigns and help
expectations. developers understand
Increased Accessibility and Inclusivity : Including accessibility from the start helps ensure
people of diverse abilities.
the Ul is usable by

2.2 Introduction to Research and Analysis Tool (Freeware) such as FigJam

Figlam is a collaborative online whiteboard from Figma, designed for
brainstorming, planning, and research,
particularly for UI/UX design. It's widely appreciated in design and research for its intuitive, interactive
that allows users to brainstorm ideas, map workflows, and collect environment
feedback. As a research and analysis tool, it offers
several useful features, and since it has a free version, it's accessible for teams and
individuals starting out.
TechKaowledge
 UVUX Design Analysls
FigJamfor Research and
2.2.1 Features of
Brainstorming and ldeation : and connectors,
sticky notes, shapes,
Hglam allows teams
brainstormingsesslons, mind
visually using
to map out ldeasmapping and deslgn sprints. making a
Opton for
2. Collaborative Tools: simultaneously, with
users can edit the board live cursors
Multiple
Real-time Collaboration :
the b0ard and use emoji
who is working on what. can comment directly on
members
Comments and
Reactlons : Team

making feedback fun and

interactive. reacia
3. Built-in
Templates Widgets: Figlamincludes templates for common activities like user journey mapping,,empat
andTemplates:
structure their research quickly.
teams
analysis, which can help voting allow for interactive
mapping and SWOT like polls, timers, and
Widgets and Plugins :
Customizable widgets
need directly into Figam. sessiog
to integrate tools they
Users can install plugins
Research Analysis:
4. Visual Mapping for tools to create
flowçharts, which are valuable
for use
Easy drag-and-drop
Flowcharts and Diagrams: visualization.
prioritization,and pracess
journey mapping, feature research findings by grouping similar items, which is especial,
organize ideas or
Afinity Mapping : Helps identify themes and patterns.
qualitative research to
useful in
5. Import and Integration
Options:
Figma allows for easy sharing and transfer of designs. malki
integration with
Figma Integration: Direct
ideal for design teams that rely on Figma for prototyping. notes or h
Figjam and PDFS to add context to research
Import : Users can upload images, screenshots,
File
reference existing designs. streamlinina
collaboration tools like Slack and Google Drive,
works with
Other Integrations : Figlam
workflows for distributed teams.

Research and Analysis?

How FigJam Supports gathered from user interviews, surveys, and
Building : Use FigJam to compile data
segments or
User Research and Persona colors help visually differentiate findings across user
and
usability tests. Sticky notes, tags,
demographics.
are great for organizing competitive research data, using visuals, nota
Competitive Analysis : Figlam boards
strategies, strengths, and weaknesses.
and flowcharts to analyze competitor simplify the process of creating journey te
Mapping : Figlam's templates
Journey Mapping and Experience
research for visualizing a user's experience and identifying pain points.
which are essential in UI/UX
Teams and Individuals
2.2.2 Benefits of FigJam for Small
access
teams to

free version is feature-rich, allowing individuals and smaller

Accessibility : Figlam's TechKaowh
professional-quality tools without high costs.
Pusilgtipt:
 UUX Design 2.4
User Requirernents and its Aralysis
Ease of Use:Figlam has an Intultive Interface that doesn't
option for anyone In a team, regardless of techntcal skils, require extensive design knowledgo, making it a great
Real-TIme Collaboration : For distributed or remote teams, Figlam's
asset for staying aligned during analysis and real-time, interactive environnernt is an
bralnstorming sessions.
Alternatlves FigJam for Free Research and Analysls Tools
to
lfyou're exploring other options, here are some addltional free tools
commonly used for research and analysis
Miro : Slmilar to Figlam, Miro isa digltal whlteboard for
templates and integratlon optlons. bralnstorming and collaboration, offering entensive
Lucldspark : Focuses on collaboratlve dlagramming and bralnstormíng, ldeal for affinity
mapping, and flowcharts. mapping mind
Google Jamboard : Amore basic optlon but highly Integrated with Google
simpler brainstorming and team sessions. Workspace, which is useful for

2.3 User Requirements

User requirements define the specific needs, preferences, and
product, or service. They are essential to ensure the final deslgn aligns expectations
that users have from a system,
with the actual needs of its users, improving
satisfaction and functionality.
2.3.1 Definition of User Reaquirements
User requirements are statements or descriptions that specify
their tasks effectively and efficiently. They serve as a what users need from a system to accomplish
foundation for deslgning features, functions, and interfaces,
ensuring the system meets user expectations. These requirements can range from
should be able to search for files easily") to experiential needs (e.g, "the functional needs (e.g, "users
use").
interface should feel welcoming and easy to

2.3.2 Types of User Research

User research is divided into qualitative and
quantitative research methods. Both types provide unique
insights into user requirements:
.1, Qualitative Research
Definition : Focuses on understanding user behaviors, motivations, and
perceptions. It
involves collecting
non-numerical data toget in-depth insights.
Purpose : To explore user experiences, emotions, and attitudes, helping
and desired features. identify pain points, expectations,
Common Techniques :
Intervlews : In-depth, one-on-one sessions with users to understand their needs, motivations, and
pain points.
Focus Groups : Group discussions that provide insights into
collective user opinions. and reveal
common themes or expectations.
User Observation :Watching users as they interact with a
system in real-world environments to
identify areas for improvement.

TechKaowledge
9u0(ations
 2-5 User Requirements and its Anab.
UWUX Design

2. Quantitative Research
Defnition :Involves gathering numerical data that can be measured and statisticaly analyzed. It is useh
for identifying trends and patterns across a larger user base.
Purpose : To validate hypotheses about user behavior and preferences and to measure the extent of
specifc needs.
Common Techniques:
Surveys and Questionnaires : Structured questions to gather data from a large sample, providing
insights into user preferences and satisfaction levels.
Analytics and Metrics : Tracking data on how users interact with the system (e.g, click rates, time
spent on tasks) to identify usage patterns and common challenges.
Acomparison of qualitative and quantitative research in user research
Table 2.3.1

Aspect Qualitative Research Quantitative Research

Purpose To understand user behaviors, motivations, To quantify user behaviors, preferences, or
and experiences trends
Focus Explores the "why" behind user actions Answers "how many," "how often," or "what"
Data Type Non-numerical, descriptive data Numerical, statistical data
Methods Interviews, focus groups, usability testing Surveys, questionnaires, A/B testing analytics
observation

Data CollectionOpen-ended, flexible responses Structured, predefined questions and metrics

Analysis Thematic, subjective analysis Statistical, objective analysis
Approach
Example Exploring reasons users struggle with a feature Measuring how many users prefer one feature
Scenario through interviews over another via a survey
When to Use When discovering new insights or When validating findings or measuring user
understanding motivations preferences with statistics
Outcome Deep insights into user attitudes and Quantifiable metrics for user behavior or
experiences satisfaction
Example of Use Conducting in-depth interviews to understand| Using a survey to
determine what percentage
why users find a certain feature confusing. of users prefer the new design over the old
one.

2.3.3 Tools to Collect User Requirements

There are various tools and techniques to gather user
goals:
requirements,each suited to different research types and

Tech Kaowledge
P u i atien
 UVUX Design
2-6 User Requirements and its Analysis
1. Personal Observation

Descriptlon : Observing users in thelr natural environment as they

particularly useful for identifying usabilty Issues and Interact with a system. This is
understanding workflows.
Advantages : Provides authentlc Insights without user blas or
not verbalize. Interpretatlon; can reveal gaps users may
Use Case : For tasks involving physlcal
products or where users' natural workflows are cruclal.
2. Interviews

Descriptlon : Conducting one-on-one sessions with users to

challenges. InterviewS can be structured, discuss their needs, expectations, and
semi-structured, open-ended.
Advantages : Offers deep, qualitative insights
or
into user preferences and problems; helps
motivations and specific requirements. to uncover
Use Case: Useful when detailed, specific
information about user behavior or motivation is needed.
3. Questionnaire

Description : Aset of structured questions that users answer,

collect quantitative data, such as satisfaction ratings or typically in written form. Questionnaires can
usage patterns, as well as some qualitative data.
Advantages : Efficient for collecting data from a large number of users;
statistically analyzed. quantitative questions can be
Use Case: Ideal for validating trends or
features. hypotheses, and for collecting broad user feedback on product
4. User/Expert Reviews

Descriptlon :Involves getting feedback from either real users (user

reviews) on the design, usability, and functionality of asystem. reviews) or domain experts (expert
Advantages : Offers feedback based on real experience; expert reviews can
in thedesign phase. highlight potential issues early
Use Case :Useful for evaluating prototypes or early
design stages, ensuring the design aligns with usablity
best practices.
Summary Table of User Requirement Collection Methods
Table 2.3.2
Method Type Data Collected
Purpose Example Use Case
Personal Qualitative Behavioral, Understand real- Observing users in a
Observation contextual world workflows workplace to see
interactions with a tool.
Interviews Qualitative Detailed needs, Deep insight into One-on-one sessions with
motivations user expectations users of a web app to
understand needs.
Questionnaire Quantitative/Qualitative Ratings, opinions,Validate trends, Surveying users
preferences gather broad data preferred features for a
software product.

Trch Knowledgi
Publitatians
 User Requirements and
its Ara y5s
2-7
UUX Design
Purpose Example Use Case
Method Type Data Collected
analysis of
User/Expert Qualitative Feedback, Improve usablity, Expert
gather expertise prototype Ul for usab.lity
Reviews usability improvements.
recommendations

2.4 User Requirement Analysis

needs and expectations ínto speciHG, actionable
User Requirement Analysis focuses on translating user
understanding the target audience, evaluating client
requirements for a product or service. This process involves
personas. Let's explore each step in detail.
requirements, analyzing competitors, and organizínginsights into user
2.4.1 Understanding Target Audience and Client Requirements
1. Understanding the Target Audience
age, gender, occupation, locatíon, and education
User Demographics: ldentify key demographics such as
users.
level. This helps tailor the design and functionality to the specific needs of these
including usage frequency,
Behavioral Patterns : Study how users typically interact with similar products,
preferred features, and general tech proficiency.
This is important to design
Psychographics : Understand user interests, values, goals, and lifestyle.
experiences that align with users' needs and aspirations.
2. Understanding Client Requirements
(e.g., improving user retention,
Business Goals and Objectives : Determine the client's core goals ensures the
requirements with these goals
expanding market reach, or increasing sales). Aligning the user
design supports the client's objectives.
timeline, or platform restrictions. These
Technical Constraints : Assess any limitations, such as budget,
constraints impact the scope and feasibility of specific features.
expectations, priorities, and any
Stakeholder Interviews : Interviewing key stakeholders clarifies their
needs with user needs.
concerns they might have. This helps in balancing business
2.4.2 Competitive Analysis
the same industry to understand what
Competitive analysis involves studying other products or services within
valuable insights for positioning and feature
works well and where improvements can be made. It provides
differentiation.
Direct competitors are those that offer similar
1. ldentify Competitors : List direct and indirect competitors. the same user needs.
that fulfll
products or services, while indirect competitors might offer alternatives
essential features, unique
2.Evaluate Key Features and Functions : Review competitors' products to identify
functionalities, and usability standards. Take note ofaspects that users might find essential.
layouts, and interactios
3. Assess User Experlence (UX) and Ul Design : Analyzing competitors' design styles, distinctive
patterns provides a reference for industry standards, ensuring that your design remains familíar yet
or where unique features
4. Identify Gaps and Opportunities : Look for areas where competitors may fall short
feature to introduce.
can add value. For example, if competitors lack personalization, this could be a valuable
compein
5. Benchmark Performance Metrics: ldentify metrics like user engagement, reviews, and ratings for
products. This gives an understanding of what users expect and helps prioritize features.
TechKasulety
Pssiic atis
UUX Design
2-8 User Requirements and its Analysis
2.4.3 Affinity Mapping
Affinity mapping Is a technlque used to
structured way. It helps in identifying themes andorganize ldeas, findings, and Insights from research in a
visually
survey results. patterns qualitative data, such as user
In
Interview responses or
1, Gather Inslghts:
Collect user feedback, observations, and
focus groups). Ideas from varlous sources (e.g,
interviews, surveys,
2. Group Slmilar ldeas: Use sticky notes or digital tools to
user feedback about"ease of cluster related insights into categories. For
navigation" and"intuitive design" can be grouped under example,
3. Identify Key
Themes: From the grouped data, ldentify "Usability.
overarching themes that
and preferences. For instance,
common themes might include "Performance," reflect user needs, challenges,
4.
Prioritize Findings : Prioritize insights based on "Customization," or "Accessibility."
which features or improvements are critical for relevance and frequency. Affinity mappíng helps highlight
the majority of users, aiding in
2.4.4 feature prioritization.
Defining User Personas
User personas are fictional yet
representative profiles that embody the characteristics, goals, and
different user types. They help guide design
decisions by keeping the target audience at the
challenges of
1. Data
Collection : Gather data from user research to create forefront.
psychographic, and behavioral data tÏ ensure personas are realistic.personas. Use insights from demographic,
2. Persona Attributes:
Basic Information: Name, age, occupation,
location, and a brief background. This helps the team
the persona as a real person. visualize
Goals and Needs : Outline the persona's key goals in
using the product. These goals should align with the
requirements identified during user research.
Pain Points and Challenges: Describe
common problems the persona faces, which the product aims to
solve. This helps prioritize features that address these issues.
Preferred Features : Specify what the persona values in a product, such as
ease of use, performance, or
customizability.
Personality and Motivation : Briefly describe motivations, attitudes, and behavior
towards technology
and similar products.
3. Creating Different Personas :Create multiple personas if your target audience is diverse.
Each persona should
represent a unique segment of your audience, such as "Tech-savvy Professionals" or "Occasional Users."
This
helps in addressing the varied needs of different user groups.
4. Use Personas In Decision-Making : Throughout the
design process, refer back to personas topensure the
product's features, design, and functionality align with real user needs. This keeps the focus on
creating user
centered solutions.

Tech Kaouledgi
Puication9
 User Requirements andits
UWUX Design
2-9 Arayis
Summary Table of User Requlrement Analysis Techniques
Example Use Case
Technique Purpose
app for young professionals h
demographics, Deslgning a mobile preferences
Understanding TargetDefine user

Audience behaviors, and preferences analyzing their tech

soclal media platforms to improve
Competitive Analysis ldentify key features and usabílity Analyzíng
engagementfeatures
standards; spot gaps
website
Afinity Mapping Organize insights into themes and Groupíng feedback
on a redesign to
híghlight usability issues
patterns
e-learning platform,Ike
User Create representative profiles to Developing personasfor an Professional"
Defining "Working
Personas guide design decisions "College Student" and

Revlew Questlon

in user-centered design.
enhance the research and analvsis process
Q.1 Explain how a tool like FigJam can analysis. DeScnibe each featura
features of FigJam that make it useful for conductíng user research and
Q.2 List three
briefly. essental.
product design and explain why they are
Q.3 Define user requirements in the context of example of When each toe
qualitative and quantitative research in user research. Provide an
Q.4 Diferentiate between
might be appropriate. understanding user needs.
to collect user requirements, explaining how each is effective in
Q.5 Describe two tools used
user requirements? Provide an example.
Q.6 How does conducting user/expert reviews help in gathering
requirements?
target audience when analyzing user
Q.7 What is the importance of understanding the requirements?
Q.8 Explain competitive analysis in user
research. How does it help in defining user
in organizing user requirements?
What is affinity mapping, and how does it assist
used in user requirement analysis.
Q.10 Define a user persona and explain how it is
O00