Unit I

1.​ Explain evaluation execution cycle

The interactive cycle can be divided into two major phases: execution and evaluation. These can
then be subdivided into further stages, seven in all. The stages in Norman’s model of interaction
are as follows:
1. Establishing the goal.
2. Forming the intention.
3. Specifying the action sequence.
4. Executing the action.
5. Perceiving the system state.
6. Interpreting the system state.
7. Evaluating the system state with respect to the goals and intentions.

➢​ Establishing the Goal

○​ The user decides on a high-level objective (e.g., "I want to send an email").
➢​ Forming the Intention
○​ The user determines the specific action required to achieve the goal (e.g., "I need to open
my email application and compose a message").
➢​ Specifying the Action Sequence
○​ The user plans the step-by-step actions needed (e.g., "Click on the email app, select
'Compose,' type the message, and hit send").
➢​ Executing the Action
○​ The user physically carries out the planned steps (e.g., clicking buttons, typing text).
➢​ Perceiving the System State
○​ The user receives feedback from the system (e.g., a confirmation message appears after
sending the email).
➢​ Interpreting the System State
○​ The user understands the feedback and determines if the system is behaving as expected
(e.g., checking if the email was sent successfully).
➢​ Evaluating the System State with Respect to Goals and Intentions
○​ The user compares the observed outcome with their initial goal (e.g., confirming that the
correct email was sent to the intended recipient).

Significance of the Model

●​ Helps in designing user-friendly interfaces by ensuring clear feedback and predictable actions.
●​ Identifies possible gulf of execution (difficulty in translating goals into actions) and gulf of
evaluation (difficulty in understanding system feedback).
●​ Supports iterative usability testing to refine user interactions.

2.​ What is ergonomics

➢​ Ergonomics refers to the study and design of systems, interfaces, and workplaces to optimize
human well-being and overall system performance.
➢​ In Human-Computer Interaction (HCI), ergonomics focuses on designing interfaces that consider
human physical and cognitive abilities to improve efficiency, safety, and comfort.

Physical Aspects of Interfaces While Designing a System

➢​ Arrangement of Controls and Displays

○​ Controls (e.g., buttons, switches, touchscreens) should be easily accessible and logically
placed.
○​ Displays should be clear, visible, and easy to interpret to reduce cognitive load.
➢​ Surrounding Environment or Physical Environment of the Interaction
○​ The workspace setup, including desk height, screen position, and chair ergonomics,
affects user comfort and efficiency.
○​ Proper ventilation and workstation placement are essential for a comfortable working
environment.
➢​ Health Issues
○​ Physical Position: Poor posture can cause musculoskeletal disorders (e.g., back pain, wrist
strain). Adjustable chairs and monitor stands help maintain a neutral posture.
○​ Temperature Issues:
■​ Air Conditioning (AC): Ensuring an optimal room temperature prevents discomfort
and fatigue.
■​ Machine Heat Handling: Machines that generate excessive heat (e.g., CPUs,
medical devices) should be positioned to prevent overheating and user
discomfort.
○​ Lighting:
■​ Proper lighting reduces eye strain and headaches.
■​ Avoid glare from screens or bright reflections.
○​ Noise:
■​ A noisy environment can impact concentration and productivity.
■​ Soundproofing or noise-canceling headphones can help in high-noise areas.
○​ Time Factor:
■​ Prolonged exposure to certain environments (e.g., long hours in an X-ray room)
can have health effects.
■​ Regular breaks and protective measures help reduce risks.
➢​ Use of Colors
○​ Colors impact visibility, readability, and psychological response.
○​ Example Uses:
■​ Red: Alerts and warnings
■​ Green: Success or safety indications
■​ Blue: Calm, productive environment
■​ High contrast for readability (e.g., black text on a white background)
➢​ By integrating ergonomics into system design, user comfort, efficiency, and safety are enhanced,
leading to better performance and reduced health risks.

3.​ Explain different types of interaction styles

Types of Interaction Styles in HCI
➢​ Command Line Interface (CLI)
○​ Users enter text-based commands to perform tasks, requiring precise syntax.
○​ Efficient for experts, allowing quick automation, scripting, and system control.
➢​ Menus
○​ Displays a structured list of options that users select via clicks or navigation keys.
○​ Found in software applications, websites, ATMs, and mobile apps for easy access.
➢​ Natural Language Interface (NLI)
○​ Allows interaction through spoken or written human language, making systems more
user-friendly.
○​ Used in AI-based applications like Siri, Alexa, chatbots, and voice assistants.
➢​ Q/A and Query Dialogue
○​ System prompts users with questions, and responses guide the next step.
○​ Common in search engines, customer support bots, and troubleshooting systems.
➢​ Form Fills and Spreadsheets
○​ Users enter structured data into predefined fields (forms) or table grids (spreadsheets).
○​ Used in Google Forms for surveys, databases, and Excel for financial analysis.
➢​ WIMP (Windows, Icons, Menus, Pointers)
○​ A graphical user interface where users interact with windows, icons, and menus using
pointers.
○​ Found in modern operating systems like Windows, macOS, and mobile UIs.
➢​ Point and Click
○​ Users navigate by clicking interactive elements like hyperlinks, buttons, and icons.
○​ Common in web browsing, online shopping, and graphical applications.
➢​ 3D Interface
○​ Uses three-dimensional environments for immersive user interaction.
○​ Used in virtual reality (VR), gaming, architectural design, and medical simulations.

4.​ Explain paradigm for interaction

A paradigm refers to a point of view or a framework that shapes how we understand, interpret,
and approach a topic.
In Human-Computer Interaction (HCI), paradigms guide the way interactive systems are designed
to improve usability and efficiency.
Paradigms of Interaction
1. Batch Processing
●​ Groups multiple processing jobs and executes them sequentially without user interaction.
●​ Example: Early computing systems where users submitted jobs in batches for processing.
2. Time-Sharing
●​ Allows multiple users to interact with a single computer simultaneously by dividing
processing time.
●​ Example: Mainframe computers in the 1960s supporting multiple users.
3. Networking
●​ Enables multiple computers to communicate and share resources.
●​ Example: The internet, LANs, and cloud computing.
4. Graphical Displays
●​ Introduced visual interfaces, replacing text-based interactions with graphical elements.
●​ Key Features:
○​ Visibility of objects.
○​ Incremental action and rapid feedback.
 ○​ Replacing language-based commands with visual actions.
●​ Example: GUI-based operating systems (Windows, macOS).
5. Microprocessors
●​ The invention of small, powerful processors enabled personal computing.
●​ Example: Development of PCs, embedded systems in smart devices.
6. World Wide Web (WWW)
●​ Revolutionized interaction by providing a platform for global communication and
information exchange.
●​ Example: Websites, online applications, e-commerce.
7. Ubiquitous Computing
●​ Integrates computing seamlessly into everyday life.
●​ Example: Smart assistants (Google Assistant, Alexa), self-driving cars, IoT devices.
Paradigms for interaction shape the evolution of HCI by introducing new technologies that
redefine human-computer relationships, improving usability, efficiency, and accessibility.

5.​ What is design and explain three categories in design

6.​ Explain difference between local structure and global structure
Local Structure
●​ Focuses on the detailed design of individual interface elements within a screen.
●​ Local structure improves usability at a micro level, focusing on specific elements.
●​ Ensures usability, efficiency, and proper placement of components like buttons, menus, and
forms.
●​ Affects how users interact with specific elements rather than the entire system.
●​ Helps in designing user-friendly and accessible components.
●​ Example: The placement of a search bar or form layout on a webpage.
Global Structure
●​ Defines the overall organization, navigation, and connectivity of different sections.
●​ Global structure ensures a macro-level seamless user experience across the system.
●​ Ensures users can move smoothly between different pages or features.
●​ Helps users understand the system’s hierarchy and workflow.
●​ Focuses on the logical arrangement of menus, links, and content sections.
●​ Example: The navigation system of an e-commerce site, guiding users from homepage to
checkout.
7.​ Explain process of designing with proper diagram
8.​ Explain different factors to be considered in screen design and layout

Factors to Consider in Screen Design and Layout

●​ Clarity and Simplicity

○​ Keep the design clean and minimal to avoid clutter.
○​ Use clear labels, icons, and readable fonts for better understanding.
●​ Consistency
○​ Maintain a uniform style across all screens (color schemes, fonts, button placements).
○​ Users should feel familiar with the interface across different pages.
●​ Visual Hierarchy
 ○​ Arrange elements based on importance using size, color, and contrast.
○​ Important elements (e.g., call-to-action buttons) should stand out.
●​ Navigation and Flow
○​ Ensure intuitive navigation with clear menus, breadcrumbs, and links.
○​ Users should easily move between screens without confusion.
●​ Readability and Typography
○​ Use legible fonts, appropriate sizes, and proper line spacing.
○​ Avoid using too many different fonts or small text.
●​ Color and Contrast
○​ Choose a pleasing color scheme that enhances visibility and user comfort.
○​ Maintain contrast between text and background for better readability.
●​ User Control and Flexibility
○​ Provide options like undo, redo, and easy exits to enhance user control.
○​ Users should be able to modify settings and personalize their experience.
●​ Feedback and Responsiveness
○​ The system should provide instant feedback (e.g., loading indicators, confirmation
messages).
○​ Buttons and controls should respond quickly to user actions.
●​ Accessibility
○​ Design for all users, including those with disabilities (colorblind-friendly themes, screen
reader support).
○​ Ensure compatibility with assistive technologies.
●​ Use of White Space
○​ Adequate spacing between elements improves visual clarity and reduces cognitive load.
○​ Helps in organizing content effectively.
●​ A well-designed screen layout ensures usability, efficiency, and user satisfaction by focusing on
clarity, consistency, navigation, and accessibility.

9.​ Explain software lifecycle using validation and verification model

Software Lifecycle Using Validation and Verification Model

The Software Development Life Cycle (SDLC) follows a structured approach to designing,
developing, and maintaining software. The Validation and Verification (V&V) Model ensures that
the software meets both requirements and user expectations by continuously checking each
phase of development.

1. What is Verification and Validation?

●​ Verification: Ensures the software is being built correctly by checking if each phase meets
the specified requirements.
●​ Validation: Ensures the right software is built, meaning it fulfills user needs and
expectations.

Phases of Software Lifecycle with V&V Model

1. Requirements Analysis
 ●​ Verification: Check if the gathered requirements are complete, consistent, and feasible.
●​ Validation: Ensure that the requirements accurately reflect what the end users need.

2. System Design

●​ Verification: Review design documents, architecture, and technical specifications to ensure

alignment with requirements.
●​ Validation: Confirm that the design will meet user needs when implemented.

3. Implementation (Coding)

●​ Verification: Perform code reviews, unit testing, and static analysis to ensure proper
coding standards.
●​ Validation: Ensure that the developed modules work as expected through functional
testing.

4. Integration and Testing

●​ Verification: Test how different components integrate and communicate properly.

●​ Validation: Perform system testing to check if the software behaves as intended in
real-world scenarios.

5. Deployment and Maintenance

●​ Verification: Verify if the deployment process follows best practices and the software is
installed correctly.
●​ Validation: Gather user feedback to confirm that the software solves the intended
problem effectively.

Key Differences Between Verification & Validation

●​ Verification ensures correctness at each phase of development, preventing defects early.

●​ Validation ensures the final product meets user expectations and functions correctly in
the real world.

Using the Validation & Verification Model in the software lifecycle improves software quality,
reduces errors, and enhances user satisfaction by continuously checking both correctness and
usability at every phase.

10.​Describe in brief usability engineering

(Refer assignment)
11.​What are different techniques of prototype
12.​What are different criteria for choosing user

Selecting the right users for testing and designing Human-Computer Interaction (HCI)
systems is crucial for ensuring usability and effectiveness. The criteria for choosing users include:

1. User Expertise Level

●​ New Users: Have little or no prior experience; require intuitive and guided interfaces.
●​ Intermediate Users: Familiar with the system but may need some assistance.
●​ Expert Users: Highly skilled and prefer advanced features and shortcuts.

2. Age Group
 ●​ Interfaces should be tailored to different age groups (children, adults, elderly).
●​ Example: Kids may need simple visuals, while seniors may require large fonts and high contrast.

3. Technical Proficiency

●​ Users with varying levels of tech-savviness should be considered.

●​ Example: A system for IT professionals differs from one designed for general consumers.

4. Accessibility Needs

●​ Consider users with disabilities (e.g., visual, hearing, or motor impairments).

●​ Ensure compliance with accessibility standards like WCAG (Web Content Accessibility Guidelines).

5. Cultural and Language Background

●​ Systems should be adaptable for users from different regions, languages, and cultural
backgrounds.
●​ Example: Multi-language support in software.

6. Frequency of Use

●​ Frequent Users: Need efficiency, shortcuts, and customization options.

●​ Occasional Users: Require simple interfaces with clear instructions.

7. Task Requirements

●​ Users should be chosen based on their specific tasks and needs in the system.
●​ Example: A medical application should involve doctors, nurses, and hospital staff in testing.

8. Physical Environment

●​ Users who work in different environments (e.g., offices, factories, outdoor areas) require tailored
interfaces.
●​ Example: Factory workers may need rugged touchscreens with high brightness.

Unit II

1.​ Explain what is learnability

➔​ The ease with which new users can begin effective interaction and achieve maximal
performance.
➔​ Learnability concerns the features of the interactive system that allow new users to understand
how to use it initially and then how to attain a maximal level of performance.
➔​ principles that support learnability:
​ Predictability:
Predictability in interactive systems ensures that users can anticipate the outcome of their
actions based on past interactions. It reduces uncertainty, making systems easier to use and
understand. A well-designed interface should provide clear operation visibility, allowing users to
 see available actions without relying on memory. For example, in a drawing application, users
should easily identify which objects can be selected and edited. By enhancing predictability,
systems improve user experience, reducing errors and frustration.

Synthesizability

Synthesizability refers to a user’s ability to assess the effects of past interactions on a

system’s current state. It helps users build a mental model of how the system behaves.
Immediate feedback, known as honesty, enhances usability by instantly showing changes, such as
moving a file visually in a desktop interface. Eventual honesty, where changes are only visible
after further action, can lead to confusion, as seen in older versions of macOS Finder when
creating new folders. Providing clear, immediate feedback ensures users can easily track and
understand system changes, improving overall user experience.

Familiarity
Familiarity refers to how well a system aligns with a user’s prior knowledge and
experiences, making it easier to learn. It often involves metaphors, like comparing word
processors to typewriters, to create intuitive interactions. Effective design also utilizes
affordances, where objects visually suggest their function, such as buttons implying they can be
clicked.
Generalizability
Generalizability is the user’s ability to extend knowledge from one interaction to new but
similar situations. It supports learning across different applications, such as applying the same
copy-paste shortcuts across software. By maintaining consistent behaviors within and across
applications, generalizability enhances usability.
Consistency
Consistency ensures similar tasks and interactions behave predictably, reducing cognitive
load. It can apply to input methods, command names, or visual cues, like color-coded warnings in
aircraft systems. While beneficial, consistency should be balanced, as overly rigid adherence can
sometimes lead to inefficiencies, as seen with early alphabetical keyboard layouts.

2.​ Explain what is Flexibility

Flexibility in interaction refers to the various ways users and systems can exchange information.
Key principles that contribute to flexibility include:

➢​ Dialog Initiative refers to control over interactions between the user and the system. A system
pre-emptive approach restricts user actions, while a user pre-emptive approach maximizes
flexibility. While user-driven interactions are preferred, system control may be necessary for
safety or collaboration (e.g., preventing edits in a shared document).
➢​ Multi-threading allows handling multiple tasks simultaneously. Concurrent multi-threading
supports parallel tasks, while interleaved multi-threading enables switching between tasks
sequentially. Multi-modal systems enhance multi-threading by using different input/output
channels, like combining voice commands with mouse clicks.
➢​ Task Migratability refers to shifting control of a task between the user and the system. Some
tasks, like spell-checking, can be automated but still require user intervention. In safety-critical
 applications, such as aviation, task migratability ensures that control can be transferred
seamlessly when necessary.
➢​ Substitutivity allows users to input or view data in multiple equivalent forms. For instance,
margins in a document can be set in inches or centimeters, and temperature data can be
displayed as numbers or graphs. It also includes equal opportunity, meaning outputs can be
reused as inputs, as seen in spreadsheets or drawing applications.
➢​ Customizability enables users or systems to modify the interface. Adaptability allows users to
personalize input/output formats, while adaptivity refers to system-driven adjustments based on
user behavior. Features like macros, command renaming, and scripting enhance user control over
the interface.

3.​ Explain what is Robustness

➢​ Robustness – the level of support provided to the user in determining successful achievement
and assessment of goals.
Principles are:

➢​ Observability

Observability allows users to assess a system’s internal state through its interface. Key
principles include browsability, which lets users explore without making changes, and defaults,
which reduce effort by providing preset values. Reachability ensures smooth navigation between
system states, aiding flexibility and recovery. Persistence determines how long system responses
remain visible, ensuring important information isn’t lost. Together, these principles enhance
usability by providing clear and accessible feedback.

➢​ Recoverability

Recoverability allows users to correct mistakes by either forward recovery (adjusting from
the current state) or backward recovery (undoing previous actions). It is linked to reachability,
ensuring users can navigate out of errors. The effort required for recovery should match the
impact of the action.

➢​ Responsiveness

Responsiveness measures how quickly a system reacts to user input. Ideally, responses
should be instantaneous or at least provide feedback that the system is processing. Response
time stability is crucial for user experience, ensuring predictable interaction speeds.

➢​ Task Conformance

It ensures that a system supports all necessary user tasks (task completeness) and does so
in a way users understand (task adequacy). It is not enough for a system to implement predefined
functions; it must align with real user needs and even allow new tasks to emerge. The
model-world metaphor helps create an intuitive interface where the user’s mental model
matches system operations, reducing effort in task execution.
4.​ Describe Shneiderman’s eight golden rules
➔​ Shneiderman’s eight golden rules are as follows:
[Link] for consistency in action sequences, layout, terminology, command use and
so on.
[Link] frequent users to use shortcuts, such as abbreviations, special key sequences
and macros, to perform regular, familiar actions more quickly.
[Link] informative feedback for every user action, at a level appropriate to the
magnitude of the action.
[Link] dialogs to yield closure so that the user knows when they have completed
a task.
5. Offer error prevention and simple error handling so that, ideally, users are prevented
from making mistakes and, if they do, they are offered clear and informative
instructions to enable them to recover.
6. Permit easy reversal of actions in order to relieve anxiety and encourage
exploration, since the user knows that he can always return to the previous state.
7. Support internal locus of control so that the user is in control of the system, which
responds to his actions.
8. Reduce short-term memory load by keeping displays simple, consolidating
multiple page displays and providing time for learning action sequences.

5.​ Explain principle for transforming a difficult task to simple one proposed by Norman
➔​ Norman’s Seven Principles for Transforming Difficult Tasks into Simple Ones

1. Use both knowledge in the world and knowledge in the head. People work better when the
knowledge they need to do a task is available externally – either explicitly or through the
constraints imposed by the environment. But experts also need to be able to internalize regular
tasks to increase their efficiency. So systems should provide the necessary knowledge within the
environment and their operation should be transparent to support the user in building an
appropriate mental model of what is going on.

2. Simplify the structure of tasks. Tasks need to be simple in order to avoid complex problem
solving and excessive memory load. There are a number of ways to simplify the structure of
tasks. One is to provide mental aids to help the user keep track of stages in a more complex task.
Another is to use technology to provide the user with more information about the task and
better feedback. A third approach is to automate the task or part of it, as long as this does not
detract from the user’s experience. The final approach to simplification is to change the nature of
the task so that it becomes something more simple. In all of this, it is important not to take
control away from the user.

3. Make things visible: bridge the gulfs of execution and evaluation. The interface should make
clear what the system can do and how this is achieved, and should enable the user to see clearly
the effect of their actions on the system.

4. Get the mappings right. User intentions should map clearly onto system [Link] actions
should map clearly onto system events. So it should be clear what does what and by how much.
 Controls, sliders and dials should reflect the task so a small movement has a small effect and a
large movement a large effect
.
5. Exploit the power of constraints, both natural and artificial. Constraints are things in the world
that make it impossible to do anything but the correct action in the correct way. A simple
example is a jigsaw puzzle, where the pieces only fit together in one way. Here the physical
constraints of the design guide the user to complete the task.

6. Design for error. To err is human, so anticipate the errors the user could make and
design recovery into the system.

7. When all else fails, standardize. If there are no natural mappings then arbitrary
mappings should be standardized so that users only have to learn them once. It
is this standardization principle that enables drivers to get into a new car and
drive it with very little difficulty – key controls are standardized. Occasionally
one might switch on the indicator lights instead of the windscreen wipers, but the
critical controls (accelerator, brake, clutch, steering) are always the same.

6.​ Explain architecture of windowing system

7.​ What is UIMS
➢​ A User Interface Management System (UIMS) is a software framework that helps developers
design, implement, and manage user interfaces efficiently.
➢​ It provides a structured way to separate the user interface (UI) from the application logic,
improving maintainability, reusability, and flexibility.
➢​ The primary goal of UIMS is to simplify the development of user interfaces by handling user
interactions, managing interface components, and facilitating communication between the user
and the application. This ensures that:
○​ The UI can be modified without affecting core application logic.
○​ Interfaces remain consistent across different parts of the application.
○​ Developers can reuse UI components, reducing redundancy.
➢​ UIMS typically consists of three components:
○​ Presentation Component – Handles the visual representation and user interaction.
○​ Dialog Control Component – Manages the flow of interaction between the user and the
system.
○​ Application Interface Component – Connects the user interface with the underlying
application logic.
➢​ Advantages of UIMS
a. Separation of ConcernsUIMS separates UI from application logic, making it easier to update
the interface without modifying the core system.
b. Improved Maintainability:Since UI and logic are independent, fixing bugs or adding new UI
features is easier.
c. Consistency Across Applications:UIMS ensures a uniform user experience across different
modules or applications.
d. Reusability of Components:UI elements can be reused in multiple applications, reducing
development effort.
e. Platform Independence:Many UIMS frameworks allow UIs to be developed once and deployed
on different platforms.
➢​ Challenges of UIMS
 ○​ Complexity: Developing and maintaining a UIMS can be complex.
○​ Performance Overhead: Some UIMS implementations may introduce latency.
○​ Customization Limitations: Predefined UI behaviors may not always suit unique
application requirements.
➢​ A User Interface Management System (UIMS) plays a crucial role in modern software
development by streamlining UI design and interaction handling. By separating UI logic from
application functionality, UIMS improves maintainability, enhances user experience, and supports
consistency across applications. While challenges exist, its benefits make it a valuable approach
for building scalable and adaptable interfaces.

8.​ Explain in brief cognitive walkthrough & model based evaluation technique
Cognitive Walkthrough

●​ Cognitive walkthrough is a usability evaluation method focused on how easy it is for new users
to learn a system through exploration.
●​ It originated from code walkthroughs in software engineering
●​ Evaluators step through a sequence of user actions to identify potential usability issues.
●​ The method requires:
○​ A system prototype or specification
○​ A task description that users need to perform
○​ A list of steps to complete the task
○​ An understanding of user knowledge and experience
●​ Four key questions guide the evaluation:
○​ Does the action achieve the user’s goal?
○​ Is the action visible?
○​ Will users recognize the correct action?
○​ Will users understand the feedback?
●​ Findings should be documented, including usability problems and their severity, to help prioritize
design improvements.

Model-Based Evaluation

●​ A model-based evaluation uses cognitive and design models to assess usability.

●​ It integrates design specification and evaluation within the same framework.
●​ GOMS(goals, operators, methods and selection) model predicts user performance and helps
compare design options.
●​ The key stroke-level model estimates the time required for basic physical tasks.
●​ Design rationale provides a structured way to evaluate design [Link] models help
detect issues like unreachable states and circular dialogs.
●​ State transition networks assist in evaluating dialog designs before implementation.
 9.​ Describe different between heuristic evaluation & use of previous studies

Heuristic Evaluation

➔​ Heuristic evaluation, developed by Jakob Nielsen and Rolf Molich, is a usability inspection
method using predefined principles (heuristics).
➔​ It is flexible and cost-effective, applicable to design specifications, prototypes, and fully
developed systems.
➔​ Multiple evaluators (3–5 recommended) independently critique a system to identify usability
problems.
➔​ Nielsen’s 10 heuristics guide the evaluation, covering aspects like visibility, consistency, error
prevention, and user control.
➔​ Each evaluator assigns a severity rating (0-4) to usability issues based on factors like frequency,
impact, and difficulty of resolution.
➔​ Findings are compiled, and the most critical issues are prioritized for design improvements.
➔​ The method helps detect usability flaws early in development, making it a "discount usability"
technique.

Using Previous Studies in Evaluation

➔​ Experimental psychology and HCI provide valuable empirical data for evaluation.
➔​ Prior research covers generic usability aspects like menu design, command recall, and icon
choices.
➔​ Using existing studies can save time and cost by avoiding repeated experiments.
➔​ However, experimental results may not always generalize across different contexts.
➔​ Experts must carefully review study design, participant demographics, and assumptions.
➔​ Relevance is key—findings from novice users may not apply to expert-focused designs.
➔​ This method relies on expert judgment to ensure appropriate application of past research.

10.​What are factors to be considered in experimental evaluation by user

11.​What are importance of studies of group of people
●​ Evaluating group systems presents additional challenges compared to single-user studies due to
factors like communication complexity, task coordination, and data collection.
●​ Key Challenges in Group Experiments
●​ Participant Groups
○​ Require more participants (e.g., 10 single-user tests need 30 participants for 3-person
groups).
○​ Groups need time to establish rapport, making experiments longer and costlier.
○​ Scheduling is difficult, especially when shared equipment is involved.
●​ Choosing the Experimental Task
○​ Tasks should encourage active cooperation (e.g., creative writing, design,
decision-making).
○​ Must fit the groupware system's capabilities (e.g., requiring video and shared
applications).
○​ Example tasks:
■​ Desert survival task (ranking survival items as a group).
 ■​ Decision games (conflict and cooperation-based tasks).
■​ Time-critical simulations (e.g., ARKola bottling plant study).
●​ Data Gathering Issues
○​ Multiple cameras and logs needed per participant, leading to synchronization challenges.
○​ Possible solutions:
■​ Multi-view recording (each participant’s perspective separately).
■​ Four-into-one video (multiple views on a single screen).
●​ Analysis Challenges
○​ High variability between groups makes statistical significance difficult.
○​ Possible solutions:
■​ Within-group experiments (each group tested under multiple conditions).
■​ Micro-analysis (e.g., timing gaps in conversation for parametric testing).
■​ Anecdotal (qualitative) analysis (e.g., critical incidents and conversation
breakdowns).
○​ Mixed-method approaches (combining qualitative and quantitative) help maximize
insights.
●​ Field Studies vs. Experimental Studies
○​ Field studies: More natural but harder to control variables.
○​ Lab experiments: More controlled but may not reflect real-world behavior.
○​ Ethnography is useful for in-depth analysis of group dynamics in real contexts.
●​ Overall, studying group interactions requires balancing experimental rigor with real-world
applicability, often combining statistical and qualitative insights to draw meaningful conclusions.

12.​Evaluation through monitoring physiological responses

Evaluation Through Monitoring Physiological Responses

Traditional usability evaluations rely on self-reports and observations, but physiological monitoring offers
an objective way to assess user experience. Two main techniques are emerging: eye tracking and
physiological measurements.

1. Eye Tracking for Usability Evaluation

●​ Measures users' gaze patterns to assess cognitive load and screen usability.
●​ Modern non-invasive eye trackers allow usability testing without discomfort.
●​ Key eye movement metrics:
○​ Number of fixations → More fixations indicate an inefficient search strategy.
○​ Fixation duration → Longer fixations suggest difficulty in processing information.
○​ Scan path → Tracks search strategy and cognitive effort.

Challenges & Future Prospects

●​ Expensive technology—not yet widely available.

●​ Interpreting results remains complex.
●​ Expected to become standard in usability labs as technology advances.
2. Physiological Measurements for Emotional Response

●​ Measures stress, engagement, and emotions via body signals.

●​ Common physiological signals:
○​ Heart rate & blood pressure → Indicate stress or frustration.
○​ Skin conductivity (GSR) → Measures arousal & mental effort.
○​ Muscle activity (EMG) → Shows user involvement in a task.
○​ Brain activity (EEG) → Reflects attention, decision-making, and motivation.

Challenges & Research Questions

●​ Difficult to interpret responses (e.g., is increased heart rate due to frustration or excitement?).
●​ How to map physiological data to specific emotions?
●​ How do responses differ for discrete events vs. continuous interactions?

Unit III

1.​ Write a short note on emotional impact as a part of user experience.

➢​ Emotional impact plays a crucial role in shaping the overall user experience. It refers to how a
user feels while interacting with a product, application, or service.
➢​ A positive emotional impact can lead to increased user engagement, trust, and loyalty, helping in
building a reliable and appealing brand.
➢​ On the other hand, a negative emotional impact, such as confusion or frustration, may result in
reduced efficiency and user dissatisfaction.
There are four key factors that contribute to the emotional impact in UX:
❖​ Visual Aesthetics
The visual design—including colors, layout, typography, and imagery—has a powerful
effect on users' first impressions. A visually appealing interface can create feelings of pleasure,
trust, and interest, while a cluttered or outdated design can make users feel uneasy or
uninterested.
❖​ Interaction Design
This refers to how users interact with the interface—how smooth, intuitive, and responsive
it is. Well-designed interactions make users feel in control, satisfied, and confident. Poor
interactions, such as slow response times or unclear navigation, can create irritation and
confusion.
❖​ Content and Storytelling
The content presented—text, visuals, videos, or audio—should be meaningful, relatable,
and engaging. Storytelling adds an emotional layer to content by making users feel involved or
connected. Emotional narratives help deepen user involvement and enhance memory of the
experience.
❖​ Personalization
Personalization involves adapting the experience based on user behavior, preferences, or
demographics. When users feel that a product “understands” them or meets their specific needs,
it fosters a sense of relevance, comfort, and emotional connection.
➢​ Incorporating emotional design into user experience is essential for creating products that not
only function well but also feel good to use. Designing for emotional impact ensures a more
human-centered, memorable, and meaningful interaction that resonates with users at a deeper
level.
 2.​ Explain the UX process Lifecycle
3.​ Write a note on Design diversity
Design diversity in Human-Computer Interaction (HCI) refers to the practice of creating systems,
interfaces and experiences that accommodate a wide variety of users with different abilities,
preferences,backgrounds, and contexts of use. It ensures inclusivity and accessibility in the
digital world.
Key Aspects of Design Diversity:
1. Inclusivity:
o Addresses the needs of diverse user groups, such as children, elderly, and people with
disabilities.
o Promotes universal usability regardless of age, gender, language, or literacy.
2. Cultural Sensitivity:
o Designs should respect and reflect local cultures, customs, and languages.
o Avoids biases or symbols that may not be universally understood.
3. Device and Platform Diversity:
o Interfaces should work across various devices – smartphones, tablets, desktops,
wearables, etc.
o Responsive and adaptive design ensures consistency across platforms.
4. Accessibility:
o Implements features like screen reader support, keyboard navigation, high contrast
modes, and
text resizing.
o Follows accessibility standards like WCAG (Web Content Accessibility Guidelines).
5. Contextual Adaptation:
o Design should consider environmental factors, like lighting, noise, and connectivity.
o Supports both online and offline modes, and works in rural or urban settings.
Benefits of Design Diversity:
• Expands user reach and market potential.
• Enhances user satisfaction and loyalty.
• Demonstrates social responsibility and ethical design.
• Complies with legal requirements for accessibility in many countries.

4.​ Explain multi sensory system and speech synthesis in detail

5.​ Enlist the steps involved choosing a process instance for a project.
●​ Choosing the right process instance for a project is a crucial decision in UX and software design.
It ensures that the development process aligns with the project's nature, goals, and constraints.
The selection involves evaluating various parameters and mapping them accordingly.
Identify Project Parameters
●​ These are the input factors that influence the choice of a process. They help define the context
and requirements of the project.
●​ Key project parameters include:
○​ Risk Tolerance – How much uncertainty the project can handle.
○​ Highlighted Goals – Whether the focus is on speed, cost, quality, or innovation.
○​ Resources Required – Budget, tools, and human resources available.
○​ Type of System Being Designed – Mobile app, web platform, embedded system, etc.
○​ Development Organizational Culture – The working style and values of the team or
company (e.g., agile vs traditional).
○​ Stages of Progress within the Project – Whether the project is in early conception,
development, or nearing completion.
Understand Process Parameters
●​ These are the characteristics of different design or development processes. They represent the
outputs or features that result from choosing a particular process.
●​ Examples of process parameters include:
○​ Flexibility or rigidity
○​ Iterative vs sequential steps
○​ Emphasis on user involvement
○​ Level of documentation
○​ Time and cost constraints

Map Project Parameters to Process Parameters

●​ This step involves aligning the project needs with suitable process characteristics. By evaluating
the fit between what the project demands and what a process offers, the most appropriate
process model or methodology can be selected.
●​ For example:
○​ A project with high uncertainty and evolving requirements might be best suited for an
Agile or Iterative process.
○​ A safety-critical system with strict regulations may require a Waterfall or V-model
approach for detailed documentation and verification.

6.​ Describe the multimodal interaction method

➢​ Multimodal interaction refers to the use of multiple sensory channels—such as sight, sound,
touch, taste,and smell—to interact with computer systems. It is a key principle of universal design
aimed at improving accessibility, user experience, and system usability for a wide range of users.
Key Multimodal Interaction Methods:
1. Visual Interaction:
o The most commonly used channel.
o Includes graphics, text, video, and animation.
o Effective for presenting detailed and structured information.
2. Auditory Interaction:
o Uses sounds, alerts, and speech.
o Helps users stay aware of events, switch attention, or receive emotional cues (e.g.,
music).
o Important for users with visual impairments.
➢​ 3. Tactile (Touch) Interaction:
o Includes haptic feedback, vibrations, and physical input devices.
o Essential for tools requiring physical manipulation like musical instruments or steering
wheels.
o Supports non-verbal communication.
[Link] and Taste:
o Less commonly used but still informative (e.g., detecting spoiled food or environmental
hazards).
o Plays a role in specialized interfaces and sensory simulations.
➢​ Benefits of Multimodal Interaction:
• Enhances User Experience:
Provides a richer, more natural interface similar to real-world interactions.
• Supports Redundancy:
Offers the same information via multiple channels (e.g., captions for audio or voice-over
for visuals).
• Reduces Visual Overload:Spreads information across channels to avoid clutter and errors.
• Improves Accessibility:
Allows users with disabilities to choose their preferred interaction mode
7.​ Write a note on designing website for screen readers
Screen readers are assistive technologies used by people with visual impairments to read
digital content aloud. Designing websites for screen readers is a critical aspect of web
accessibility.
Key Guidelines:
1. Semantic HTML:
Use proper tags (<h1>, <nav>, <button>, etc.) to provide structure.
2. Alt Text for Images:
Provide descriptive alt attributes for all important images.
3. Label Form Elements:
Use <label> tags or aria-label attributes for form controls.
4. Keyboard Navigation:
Ensure all site functionality is accessible via the keyboard (e.g., Tab, Enter).
5. Skip Navigation Links:
Help users bypass repetitive content and jump directly to main sections.
6. ARIA Roles and Attributes:
Use ARIA (Accessible Rich Internet Applications) to enhance screen reader support
where HTML is insufficient.

8.​ Give a brief description of the roots of usability.

➢​ Usability is rooted in how users interact with a system, and it ensures that products are easy to
learn, efficient to use, and satisfying to the user.
➢​ The concept of usability is not limited to visual appeal—it focuses on whether users can achieve
their goals effectively and comfortably.
➢​ The roots of usability are reflected in a cyclical process of user interaction, which includes the
following five key stages:
1. Design
○​ The foundation of usability begins with user-centered design.
○​ Designers plan layouts, navigation, content structure, and interactive elements.
○​ Focus is placed on understanding user needs, context of use, and potential pain points.
○​ Example: Designing a food delivery app’s home screen with easy access to recent orders
and popular cuisines.
2. Implementation
○​ Once the design is finalized, it is translated into a working prototype or actual product.
○​ Developers implement the interface, functionality, and system behavior based on the UX
design.
○​ Example: Coding the navigation bar, search feature, and menu display in the app.

3. Evaluation & Testing

○​ The product is tested with real or representative users.
○​ Evaluation helps identify where users struggle, what works well, and how improvements
can be made.
○​ Example: Conducting usability testing sessions where users try to order food, and
observing where they hesitate or make errors.
4. Analysis
○​ All the data and observations collected from testing are carefully analyzed.
○​ This helps in discovering usability flaws, measuring task success, and prioritizing issues.
 ○​ Example: Noticing that users are taking too long to find the "Order Again" button,
suggesting poor visibility.
5. Feedback
○​ The insights from analysis are turned into actionable feedback to enhance the product.
○​ This creates an iterative loop, where changes are made and re-tested for continuous
improvement.
○​ Example: Moving the "Order Again" button to the top of the homepage and increasing its
size for better visibility.

9.​ Explain the universal design principles

➢​ Universal design refers to the process of creating products that can be used by as many people
as possible in various situations.
➢​ It aims to provide an accessible and equivalent experience to all users, without excluding anyone
based on their abilities.
➢​ In the late 1990s, a group at North Carolina State University proposed seven universal design
principles that help guide the design process for more inclusive products:
○​ Equitable Use: The design should be useful to people with different abilities and should
not exclude anyone. It should offer equivalent use where identical use is not possible,
ensuring that access is fair for all users.
○​ Flexibility in Use: The design should accommodate a variety of abilities and preferences.
It should offer choices in how users interact with it and adapt to their pace and skill level.
○​ Simple and Intuitive Use: The system should be easy to use, regardless of the user's
experience, language, or concentration level. It should support users' expectations and be
organized clearly, with helpful feedback.
○​ Tolerance for Error: The design should minimize the impact of mistakes and provide
safety measures. Potential hazards should be avoided or shielded, and systems should
be designed to "fail safely."
○​ Low Physical Effort: The system should be easy and comfortable to use, reducing
physical strain or fatigue. It should allow for natural posture and minimize repetitive or
sustained physical actions.
○​ Size and Space for Approach and Use: The design should be accessible to all users,
regardless of body size, posture, or mobility. It should be easy to approach and use, with
sufficient space for assistive devices and a clear line of sight.

10.​Describe the concept of touch in the interface

➢​ Touch is a powerful sense that plays a fundamental role in how we interact with our environment.
In digital systems, the integration of touch is referred to as haptic interaction.
➢​ It is unique because it can both send and receive information, making it a two-way sensory
channel.
➢​ Although not yet mainstream in everyday computer interactions, touch-based technology is
growing rapidly in both research and commercial fields.
➢​ Types of Haptic Interaction
Haptics can be divided into two main types based on the nature of sensation:
○​ Cutaneous Perception
■​ Concerned with tactile sensations through the skin.
■​ Often implemented using vibration-based feedback.
■​ Allows users to perceive texture, shape, resistance, and temperature.
○​ Kinesthetic Perception
■​ Related to the movement and position of muscles and joints.
■​ Uses devices that apply physical resistance or force feedback.
■​ Helps in perceiving weight, friction, size, and spatial location.
➢​ Applications of Haptics
○​ Braille Displays
One of the most successful tactile devices for visually impaired [Link] up of
20–80 cells with 6 or 8 pins that rise and fall to represent braille [Link] to read
text on screens through [Link] pins in electronic braille provide additional details like
cursor position or case.
○​ Force Feedback Devices (e.g., PHANTOM by SensAble Technologies)
Allow users to feel 3D virtual [Link] resistance, shape, and texture
through [Link] in training (e.g., surgery simulators) and [Link] realism
and understanding of object characteristics.
➢​ Challenges in Haptic Technology
○​ High Cost and Engineering Complexity
○​ Devices like braille displays are limited by resolution and actuator density.
○​ Creating high-resolution tactile graphics would require thousands of actuators in a small
area.
○​ Force feedback systems are currently expensive, limiting widespread adoption.
➢​ Touch-based interaction significantly contributes to universal design, which aims to make systems
usable for all, including people with disabilities.
➢​ For visually impaired users, touch provides a primary channel of information.
➢​ For sighted users, it adds a richer, multi-modal experience, enhancing engagement and realism.
➢​ The concept of touch in the interface opens up new dimensions in human-computer interaction.
➢​ From assisting users with impairments to enhancing simulation realism, haptics bridges the gap
between digital and physical experiences.
➢​ As hardware evolves and becomes more affordable, touch will play an increasingly central role in
UX design and universal accessibility.
11.​Explain the user experience needed as a business case.
1. Executive Summary
User Experience (UX) is no longer optional—it's a competitive necessity. This business
case presents how investing in UX can solve current user pain points, enhance satisfaction,
improve retention, and ultimately drive business growth. A structured UX process ensures that
products are usable, useful, and desirable, aligning both user needs and business goals.
2. Mission Statement
●​ Goal: To create a seamless, engaging, and accessible experience for our users.
●​ Reason: A well-crafted user experience will increase customer satisfaction, reduce
support costs, and improve conversion rates.
3. Market
●​ The digital market is saturated, and user expectations are higher than ever.
●​ 88% of users are unlikely to return after a bad experience.
●​ Companies investing in UX see up to 400% increase in conversion rates.
●​ Our competitors are already enhancing their UX, making this a strategic priority.
4. Problem Statement
Users are experiencing difficulties navigating the current system due to poor
interface design, lack of personalization, and low accessibility, leading to decreased
engagement, high dropout rates, and reduced customer satisfaction.
5. Proposed Solution & Value Proposition
To resolve these problems, we propose:A complete UX audit,Redesigning the product
flow based on user research,Implementing intuitive and accessible UI elements,Adding
personalization features
○​ Value Proposition:
■​ Investing in UX will result in:
■​ Reduced churn rate
■​ Increased user engagement and loyalty
■​ Higher ROI via increased sales or subscriptions
 ■​ Lower customer support queries
6. Risks
●​ User Interaction Risk: If UX changes are poorly implemented, it may confuse existing
users.
●​ Market Risk: Even after redesign, adoption depends on user behavior and competition.
7. Roadmap (Timeline)
●​ The UX roadmap begins with research, prototyping, and user testing in the first 6 weeks.
This is followed by development, QA, and final launch over the next 6 weeks.
8. Required Resources
●​ Design Tools: Figma, Adobe XD, [Link]
●​ Testing Environment: Devices, software for A/B testing
●​ User Research Tools: Surveys, Interview software
●​ Budget Estimate: ₹[Insert Amount]
9. Team
●​ We will require collaboration across 5 core teams:
●​ UX/UI Design Team – User research, wireframes, visual design
●​ Backend Team – API development, optimization
●​ Frontend Team – Implementation of UI
●​ QA Team – Testing user flows and responsiveness
●​ Product & Marketing Team – Aligning UX with business goals
Investing in UX is not a cost, it's an opportunity. It aligns technology with human needs, boosts business
KPIs, and strengthens brand reliability. With a focused UX strategy, we can turn user satisfaction into
long-term profitability.

Unit IV

1.​ Explain knowledge based analysis in detail.

➢​ Knowledge-Based Task Analysis is a structured approach that focuses on identifying and
organizing the knowledge required to perform a task.
➢​ It does this by cataloging the objects and actions involved in a task and building taxonomies
(hierarchical classifications) to show how these elements relate to each other.
➢​ This method is particularly helpful in:
○​ Designing training materials
○​ Understanding user expertise
○​ Comparing knowledge requirements across different tasks
➢​ Steps in Knowledge-Based Task Analysis
○​ List all Objects and Actions:
Identify every object (physical or conceptual) and every action a user performs in the task.
E.g., in driving a car: steering wheel, brake pedal, indicators (objects); turning,
accelerating, braking (actions).
○​ Create Taxonomies:
Taxonomy = a hierarchical classification of objects or actions (similar to how
biology classifies species).
Helps in understanding the structure of the knowledge domain.
Two main types:
■​ Object taxonomy
■​ Action taxonomy
○​ Use Sorting Tasks (Optional):
Give users a set of items (on cards) and ask them to group them based on similarity.
Helps in building user-centric classifications.
 ○​ Build Hierarchies:
The taxonomy can include:
■​ XOR branches: One and only one category (e.g., "steering control" or "lighting
control")
■​ AND branches: Object belongs to multiple categories (e.g., wipers by position and
function)
■​ OR branches: Object may belong to one or more categories (e.g., a plate used for
dining or preparation)

➢​ Key Benefits of Knowledge-Based Analysis

○​ Clarifies user knowledge: What the user must know to perform tasks.
○​ Supports training: Provides structured content for manuals and courses.
○​ Helps system design: Especially for interfaces and menus.
○​ Promotes task generalization: Enables abstraction of common patterns across tasks.

2.​ Difference between data driven vs model driven inquiry.

Data-Driven Inquiry:
➢​ Focus: Analyzing real user data (e.g., analytics, A/B testing, usability testing) to understand user
behavior and identify areas for improvement.
➢​ Approach: Quantitative and qualitative data is collected and analyzed to gain insights into user
needs and preferences.
➢​ Benefits: Data-driven design can lead to more user-friendly and effective designs, as it is based
on real-world user behavior.
➢​ Examples: Analyzing click-through rates, conversion rates, time on page, or user feedback from
surveys and interviews.
➢​ Limitations: Data alone can be insufficient to understand the "why" behind user behavior and may
not capture the full spectrum of user needs.
➢​ Tool: Analytics tools, A/B testing platforms, usability testing software.

Model-Driven Inquiry:
➢​ Focus: Creating mental models or user flows to understand how users expect things to work and
to identify potential usability issues.
➢​ Approach: Designers use their understanding of user psychology and domain knowledge to
create models of user behavior and interactions.
➢​ Benefits: Model-driven inquiry can help designers create more intuitive and predictable interfaces,
as it is based on a clear understanding of user expectations.
➢​ Examples: Creating user flows, wireframing, or prototyping to test different design options.
➢​ Limitations: Models can be based on assumptions and may not accurately reflect real-world user
behavior.
➢​ Tool: Design software, prototyping tools, user flow diagrams.

3.​Explain a brief detail on the task decomposition method.

4.​Explain in brief the extraction interaction design requirements.
5.​Write a short note on group dynamics.
6.​How does user work activity gathering help in the UX designing phase?
➢​ User work activity gathering in UX design involves understanding how users interact with a
product or service in their daily lives to inform design decisions.
➢​ This process includes observing users, conducting interviews, and analyzing their tasks to gain
insights into their needs, behaviors, and motivations.
 ➢​ Elboration:
1. Understanding User Needs:
The primary goal of user work activity gathering is to identify the user's needs and how
they relate to the product or service. This understanding helps designers create a user-centered
experience that effectively addresses those needs.
2. Research Methods:
Various methods are employed to gather user work activity information, including:
○​ Observation: Observing users in their natural environment while they interact with a
product or service.
○​ Interviews: Conducting one-on-one interviews with users to gain in-depth understanding
of their experiences.
○​ Surveys: Gathering quantitative data through structured questionnaires.
○​ Task Analysis: Breaking down complex tasks into smaller steps to understand the user's
workflow.
3. Analyzing Data:
The collected data is then analyzed to identify patterns, trends, and insights. This analysis
helps designers make informed decisions about design and development.
4. Informing Design:
The insights gained from user work activity gathering are used to inform the design
process. For example, understanding a user's workflow might lead to a redesigned interface that
improves efficiency.
5. Benefits:
User work activity gathering helps designers:
○​ Create products and services that are user-friendly and efficient.
○​ Reduce development costs by avoiding features that are not truly needed by users.
○​ Improve the overall user experience and satisfaction.

7.​ With respect to entity relationship based task analysis, explain the basic types of objects with
examples.
8.​ Enlist the sources of information and data collection.
9.​ Explain the system concept statement in a UX designing process.
➢​ A system concept statement is a brief, focused explanation of a system's purpose, intended
functionality, and how it will address a problem or opportunity, serving as a starting point for
development and communication.
Key Elements of a System Concept Statement:
○​ Purpose: What problem or opportunity does the system aim to solve or address?
○​ Functionality: What are the key features and capabilities of the system?
○​ Target Audience: Who will use the system and what are their needs?
○​ Scope: What are the boundaries of the system, both technically and organizationally?
○​ Value Proposition: How will the system provide value to stakeholders?
○​ Vision: What is the desired future state after the system is implemented?
Purpose of a System Concept Statement:
➢​ Communication:
○​ It helps to communicate the system's purpose and scope to stakeholders, ensuring
everyone is on the same page.
➢​ Focus and Scope:
○​ It helps to define the focus and scope of the system development effort, preventing scope
creep and ensuring that the system addresses the right needs.
➢​ Decision Making:
○​ It provides a foundation for making informed decisions about system design,
development, and implementation.
 ➢​ Contextual Inquiry:
○​ It can serve as a starting point for contextual inquiry, a method used to understand how
users interact with a system in their natural environment.
➢​ Alignment:
○​ It helps to align teams across silos on a shared vision and determine the particulars
needed to execute on the idea.

10.​What is task analysis? Enlist and explain the approaches to task analysis in task models.
➢​ Task Analysis is a foundational process in UX and system design where the tasks users perform
are studied to understand their goals, behaviors, tools, and required knowledge.
➢​ It helps designers break down complex tasks into manageable parts and align system design with
actual user needs.
➢​ Why Task Analysis is Important:
○​ Understand user goals and challenges.
○​ Design user-centered systems.
○​ Create effective training and documentation.
○​ Inform design decisions like menu structure, workflow, or UI layout.
○​ Identify areas for automation or improvement.
➢​ three different approaches to task analysis, which overlap but which lay their emphases on
slightly different areas. These are as follows:
○​ Task decomposition which looks at the way a task is split into subtasks, and the order in
which these are performed.
○​ Knowledge-based techniques which look at what users need to know about the objects
and actions involved in a task, and how that knowledge is organized.
○​ Entity–relation-based analysis which is an object-based approach where the emphasis
is on identifying the actors and objects, the relationships between them and the actions
they perform.

11.​Write a short note on contextual analysis.

●​ Contextual analysis in UI design involves understanding the environment, users, and tasks
related to a product to create a user-centered and effective interface.
●​ It helps designers ensure designs are usable, relevant, and familiar to users, leading to higher
satisfaction and success.
Methods for Contextual Analysis:
●​ Contextual Inquiry: This involves observing and interviewing users in their natural environment
while they are using a product or performing a task.
●​ Field Studies: Researchers can observe users in their natural environment to understand their
behavior and needs.
●​ Surveys and Questionnaires: These can be used to gather data about user demographics,
attitudes, and behaviors.
●​ Usability Testing: Observing how users interact with the product can reveal usability issues and
areas for improvement.
●​ Focus Groups: These can be used to gather insights from a group of users about their
experiences with the product.

Benefits of Contextual Analysis:

●​ User-Centered Design: By understanding the context of use, designers can create products that
are more user-friendly and effective.
●​ Improved Usability: Contextual analysis can help identify usability issues and areas for
improvement.
 ●​ Higher User Satisfaction: By meeting users' needs and expectations, designers can create
products that users are more likely to use and enjoy.
●​ Increased Market Success: Products that are well-designed and meet user needs are more likely
to be successful in the market.
●​ Better Communication: Contextual analysis can help designers communicate their designs to
stakeholders more effectively.
●​ Informed Decision Making: Contextual analysis provides data that can inform design decisions
and help designers make better choices.

Unit 5

1.​ Describe in brief the summative data analysis.

2.​ What are the different types of formative data?
3.​ Explain the following terms used in UX architecture:
a.​ Sketching b. Wireframe c. Prototyping d. Ideation e. User Persona
a. Sketching
Sketching is a quick and low-cost method for visualizing ideas during the early stages of UX
design. Designers use sketches to explore different layouts, interactions, and user flows before
committing to detailed designs. It helps in brainstorming, problem-solving, and communicating ideas with
team members and stakeholders.

b. Wireframe
A wireframe is a basic, visual guide that represents the skeletal framework of a digital interface. It
focuses on layout, structure, and functionality without detailed design elements like colors or images.
Wireframes help map user flows and ensure clarity in content placement and navigation paths.

c. Prototyping
Prototyping involves creating interactive models of a product that simulate user interactions.
Prototypes can range from low-fidelity (paper or static digital versions) to high-fidelity (clickable, realistic
versions). They allow designers to test usability, gather feedback, and refine the experience before final
development.

d. Ideation
Ideation is the creative phase in UX design where diverse ideas are generated to address user
problems and improve experiences. Using brainstorming, SCAMPER, bodystorming, and other
techniques, teams explore a wide range of potential solutions. The aim is to encourage creativity and
innovation, focusing on user needs.

e. User Persona
A user persona is a fictional character that represents a segment of the target audience. It
includes demographic details, goals, motivations, and behaviors. Personas help UX teams empathize
with users, prioritize features, guide design decisions, and maintain a user-centered approach
throughout the project.

4.​ Enlist the contents required in an evaluation report.

Components of a UX Evaluation Report:
➢​ Introduction:
Briefly explains the purpose of the evaluation, the scope of the study, and the target audience.
 ➢​ Methodology:
Describes the specific methods used for data collection and analysis (e.g., usability testing,
heuristic analysis, surveys).
➢​ Results:
Presents the findings of the evaluation, including quantitative data (e.g., task completion rates,
error rates) and qualitative data (e.g., user feedback, observations).
➢​ Analysis and Insights:
Interprets the results, identifying patterns, trends, and key insights about user behavior and
satisfaction.
➢​ Recommendations and Action Items:
Provides concrete suggestions for improving the product or design based on the findings.
➢​ Conclusion:
Summarizes the main points of the report and emphasizes the importance of addressing the
identified issues.
➢​ Appendix:
Includes supplementary materials, such as detailed data tables, transcripts of interviews, or visual
aids.
Types of UX Evaluation Reports:
➢​ Usability Testing Reports:
Focus on evaluating the ease of use and effectiveness of a product or interface.
➢​ UX Audit Reports:
Conduct a comprehensive review of a product's UX, identifying areas for improvement.
➢​ User Research Reports:
Summarize the findings of user research studies, often focusing on understanding user needs
and behaviors.
➢​ Heuristic Evaluation Reports:
Assess a product's usability based on a set of established usability principles.

5.​ What are the different types included in data evaluation in UX.

🔷
data evaluation methods used in UX design, grouped under Quantitative and Qualitative approaches:
Quantitative Methods
These methods focus on numerical data and measurable insights to understand user behavior and
design effectiveness.
➢​ Usability Testing:
Measures how easily users can perform tasks.
Tracks success rates, error rates, and time on task.
➢​ A/B Testing
Compares two or more design versions to see which performs better.
Based on metrics like conversion rate, bounce rate, or click-through rate.
➢​ Surveys and Questionnaires
Collect structured feedback using scales or predefined options.
Useful for gathering opinions from a large audience.
➢​ Web and App Analytics
Tools like Google Analytics monitor user behavior on websites or apps.
Tracks page views, session durations, click paths, bounce rates, etc.
➢​ Heat Maps
Visual representation showing where users click, scroll, or hover.

🔶
Helps identify areas of high engagement or where users drop off.
Qualitative Methods
These focus on understanding user emotions, motivations, and thought processes through in-depth
observation and discussion.
 ➢​ User Interviews:One-on-one conversations to understand user needs, behaviors, and pain points.
➢​ Focus Groups:Guided discussions with small groups of users to gather diverse opinions.
➢​ Diary Studies:Users record their experiences over time (e.g., 1 week or 6 months) to capture
long-term interactions.
➢​ Field Studies:Observing users in their natural environment to see how they use a product in real
life.
➢​ Heuristic Evaluation:Experts review the interface based on established usability principles
(heuristics).
➢​ Card Sorting:Participants organize topics into categories. Helps designers understand how users
mentally group information.
➢​ Tree Testing:Evaluates the structure and navigation of a website without visual design elements.
➢​ Concept Testing:Presenting early design ideas or concepts to users to get feedback before
building.
➢​ User Feedback:Open-ended comments collected via surveys, contact forms, or in-app prompts.

6.​ Explain in brief the design thinking in user experience architecture.

​ Design thinking in UI architecture is a user-centered problem-solving approach that prioritizes
understanding user needs and iteratively creating solutions through empathy, ideation,
prototyping, and testing.
➢​ Design thinking is a human-centered approach to problem-solving that focuses on innovation and
creation.
➢​ It's a non-linear, iterative process that involves understanding users, challenging assumptions,
redefining problems, and creating innovative solutions.
It's particularly useful for tackling complex, ill-defined problems.
➢​ The 5 Stages of Design Thinking:
○​ Empathize: Understand the target users, their needs, and pain points.
○​ Define: Clearly define the problem based on user insights.
○​ Ideate: Generate a wide range of potential solutions.
○​ Prototype: Create tangible representations of the ideas to test and refine.
○​ Test: Evaluate the prototypes with users and iterate based on feedback.
How Design Thinking Benefits UI Architecture:
➢​ User-Centricity:
Design thinking ensures that UI designs are built around the needs and behaviors of real users.
➢​ Innovation:
It encourages a creative and iterative approach to problem-solving, leading to more innovative
and effective solutions.
➢​ Improved User Experience:
By focusing on user needs and testing solutions, design thinking helps create intuitive and
user-friendly interfaces.
➢​ Reduced Development Costs:
Early user testing and iteration can help identify and address potential problems early in the
development process, reducing costs and time.
➢​ Better Problem Solving:
Design thinking helps to move beyond superficial solutions and address the root causes of
problems.
➢​ Collaboration:
Design thinking fosters collaboration among designers, developers, and stakeholders, ensuring
that everyone is aligned on the goals and solutions.
 7.​ Explain the design and prototyping in UX architecture.

8.​ Difference between summative and formative methods.

Aspect Formative Methods Summative Methods

Time Early in the design process Near the end of deployment or when
Introduced the design is mostly complete

Goal To identify and fix usability To assess and confirm if the product
issues meets goals

Purpose To inform design decisions To evaluate if the product is ready for

launch

Method Type Qualitative methods Quantitative methods

Common Heuristic evaluation, user Task completion rate, error rate, user
Methods interviews, cognitive satisfaction surveys, benchmark
walkthrough, paper testing
prototyping

Emphasis Focus on process and Focus on outcomes and achieving

(Function) understanding user needs specific usability goals

Audience Designers, developers, and Stakeholders or decision-makers

usability specialists (e.g., managers, investors)

Example A UX designer conducts paper A usability test is conducted with 100

prototyping with users to users on the final version of the
explore layout options and app to measure how many can
gathers feedback before complete key tasks successfully
coding begins. before product launch.