Q1.

Designing a Secure Health App

Scenario: You are designing a mobile healthcare app for patients, doctors, and admin
staff. The app manages health records, appointments, and messaging securely.
Questions:
1. Identify 3–4 main features of the app and explain how security is integrated without
compromising usability.
2. Draw a wireframe or digital prototype showing where biometric login, session
timeout, and encrypted messaging are implemented.
3. Suggest good design vs poor design examples in the app (e.g., confusing menu vs
clear navigation).
4. Identify potential cognitive, social, and emotional issues users might face and how the
app design addresses them.
5. Propose persuasive technologies to encourage healthy habits (e.g., medication
reminders, appointment alerts).
6. Explain how the conceptual model helps users understand app functions
Answers:
1. Main Features and Security Integration

Main Features:

1. Patient Records: View and update medical history.

2. Appointment Scheduling: Book, reschedule, or cancel appointments.
3. Secure Messaging: Patients and doctors communicate privately.
4. Medication Reminders: Notifications for prescriptions.

Security Integration:

 Biometric Login (fingerprint/face): Quick access without typing passwords.

 Session Timeout: Automatically logs out inactive users to prevent unauthorized
access.
 Encrypted Messaging: Messages are encrypted end-to-end, ensuring privacy.
 Two-Factor Authentication (2FA): Optional for sensitive actions like prescription
updates.

Usability Consideration:

 Security features are integrated seamlessly without complex steps.

 Clear icons and prompts guide users, minimizing frustration.

2. Wireframe / Digital Prototype (Description)

Screen 1 – Login:

 Biometric login icon + traditional password option.

Screen 2 – Dashboard:

 Tabs for “Records,” “Appointments,” “Messages,” “Reminders.”

Screen 3 – Messages:

 Lock icon on chat window → encrypted messaging.

Screen 4 – Session Timeout Warning:

 Pop-up: “Your session will expire in 1 minute. Tap to continue.”

3. Good Design vs Poor Design

Aspect Good Design Poor Design

Navigation Clear tabs with icons and labels Hidden menus, unclear hierarchy
Security Multiple confusing authentication
Simple, minimal steps, clear instructions
Prompts steps
Confirmation after booking, messages No confirmation, users unsure of
Feedback
delivered actions
Helpful error messages (e.g., “Invalid
Error Handling Generic errors, users frustrated
date”)

4. Cognitive, Social, and Emotional Issues

Issue Type Potential Problem Design Solution

Users forget steps or get
Cognitive Clear labels, step-by-step instructions, tooltips
confused
Personal login, session timeout, role-based
Social Multiple users sharing device
access
Visible security indicators, reassurance
Emotional Anxiety about data privacy
messages

5. Persuasive Technologies

 Medication Reminders: Push notifications to encourage adherence.

 Appointment Alerts: Pop-up notifications to reduce missed visits.
 Progress Tracking: Visual charts for health improvements.
 Gamification: Reward badges for completing health tasks.

6. Conceptual Model

 Definition: A representation of how users understand the system and interact with it.
  Role:
o Helps users predict outcomes (e.g., tapping “Messages” opens secure chat).
o Simplifies learning by maintaining consistent structure across screens.
o Aligns mental model of users with system operations, reducing errors.

Summary:

 Main features include Records, Appointments, Messaging, Reminders.

 Security is integrated via biometric login, encryption, 2FA, session timeout without
hurting usability.
 Good design emphasizes clarity, feedback, and error prevention; poor design is
confusing.
 Cognitive, social, and emotional concerns are addressed with clear instructions,
personal login, and visible security.
 Persuasive tech encourages healthy habits.
 The conceptual model guides users to easily understand and navigate the app.

2. Online Learning Platform

Scenario: A university wants an e-learning platform with timed quizzes, instant results,
and progress tracking.

Questions:

1. Perform a task analysis for a student taking a quiz. Include steps for both new and
returning users.
2. Identify interface types that can be used: WIMP, Mobile, Web, Multimedia, or VR.
Justify your choices.
3. Suggest expressive vs frustrating interface elements.
4. Describe how user experience (UX) goes beyond usability in this platform.

Answers:
1. Task Analysis for Taking a Quiz

Step New User Returning User

1 Register / Create account Login using credentials
2 Verify email or identity Direct login to dashboard
3 Navigate to quiz section Navigate to quiz section
4 Select quiz and read instructions Select quiz directly
5 Start quiz Start quiz
6 Answer questions Answer questions
7 Submit quiz Submit quiz
8 View results & feedback View results & feedback
9 Track progress / badges Track progress / badges

Key Point: New users have additional steps for registration, while returning users can
directly access quizzes.
2. Interface Types & Justification

Interface Type Use in Platform Reason

WIMP (Windows, Icons, Familiar interface, easy navigation,
Desktop version
Menus, Pointer) supports mouse/keyboard
Mobile Interface Smartphones / tablets Accessible anywhere, responsive design
No installation required, platform-
Web Interface Browser-based access
independent
Video tutorials, Makes learning engaging and
Multimedia Interface
animations interactive
Optional for labs or Provides immersive learning
VR Interface
simulations experiences

3. Expressive vs Frustrating Interface Elements

Type Example
Expressive Clear buttons, color-coded progress bar, instant feedback messages
Frustrating Hidden navigation, unclear error messages, slow loading pages, small text

4. How UX Goes Beyond Usability

 Usability: Ensures tasks are easy, efficient, and error-free (e.g., easy navigation,
clear instructions).
 UX: Includes emotional, cognitive, and motivational aspects:
o Engaging visuals and multimedia increase motivation to learn.
o Progress tracking, badges, and feedback create a sense of achievement.
o Personalized recommendations improve user satisfaction and retention.

Key Point: UX is not just about completing tasks; it’s about how users feel and interact
with the platform.

Summary:

 Task analysis shows differences between new vs returning users.

 Interface types (WIMP, Mobile, Web, Multimedia, VR) enhance accessibility and
engagement.
 Good design is expressive, bad design is frustrating.
 UX goes beyond usability, covering motivation, emotions, and satisfaction.

Q3. Smart Home Device

Scenario: You are designing a smart thermostat that adapts to user preferences.

Questions:
 1. Suggest functional, data, environmental, user, and usability requirements.
2. Draw a hierarchical task analysis (HTA) for setting a temperature for the first time
vs. regular adjustments.
3. Identify potential emotional responses and design improvements to make the
interface user-friendly.

Answers:

1. Requirements

Type Example Requirement

Adjust room temperature automatically based on user preferences and
Functional
schedules.
Store temperature settings, schedules, and sensor readings (current
Data
temperature, humidity).
Device operates in living rooms or bedrooms with varying lighting, noise,
Environmental
and connectivity.
Homeowners of varying ages and tech skills; family members may share the
User
device.
Interface should be intuitive, minimal steps, with clear visual feedback and
Usability
error prevention.

2. Hierarchical Task Analysis (HTA)

Goal: Set thermostat temperature

Plan 0:

 New User: 1 → 2 → 3 → 4 → 5
 Returning User: 1 → 2 → 5

Steps:

0. Set Temperature
├─ 1. Power on device / open app
├─ 2. Select mode (Heating / Cooling / Auto)
├─ 3. Set desired temperature
├─ 4. Configure schedule (if first-time user)
└─ 5. Confirm and save settings

Explanation:

 New users configure mode, temperature, and schedule.

 Returning users can quickly adjust temperature using saved preferences.

3. Emotional Responses & Design Improvements

 Emotional
Problem Design Solution
Response
Difficulty understanding Use clear icons and labels for
1. Confusion
modes Heating/Cooling/Auto
Too many steps for first-time
2. Frustration Provide step-by-step guided setup
setup
Fear of energy waste or Show real-time feedback and
3. Anxiety
device malfunction confirmation messages
Quick adjustments and Include shortcuts and default
4. Satisfaction
automation preferences for convenience

Key Design Principles:

 Minimal cognitive load

 Clear visual feedback
 Guided setup for first-time users
 Quick access for returning users

Summary:

 Functional, data, environmental, user, and usability requirements are aligned to make
the thermostat intuitive and secure.
 HTA shows different flows for new vs returning users.
 Emotional responses are addressed by clear labels, feedback, and guided setup.

Q4. University Self-Service Cafeteria (Credit System)

Scenario: A cafeteria allows users to pay via credit card or campus card.

Questions:

1. Suggest functional, data, environmental, user, and usability requirements.

 2. Select data gathering techniques to understand student behavior: questionnaires,
interviews, observation, or studying documentation.
3. Prepare a structured interview question set for feedback on usability.
4. Prepare a task description and task analysis for a student buying food as a new vs
returning user.

Answer:

1. Requirements

Type Example Requirement

Functional Calculate total cost, process payment via credit/campus card, issue receipt.
Data Store menu items, prices, transaction history, card balances.
Environmental Busy cafeteria with noise, queues, and trays to handle.
Mostly students aged 18–25 with basic tech familiarity; occasional staff
User
users.
Fast, intuitive interface; clear buttons; minimal steps for payment; accessible
Usability
font and visuals.

2. Data Gathering Techniques

Technique Use in This Scenario

Collect feedback on preferences, speed, and satisfaction from many
Questionnaires
students.
Interviews In-depth understanding of pain points with current system.
Watch students interact with self-service kiosks to identify
Observation
bottlenecks.
Studying Analyze past sales reports, transaction errors, and existing
Documentation workflows.

3. Structured Interview Questions

1. How easy was it to select your items from the menu?

2. Did you find the payment process straightforward?
3. Were error messages or instructions clear?
4. How long did it take to complete the transaction?
5. Any suggestions to improve the kiosk interface or experience?

4. Task Description & Task Analysis

Goal: Buy food using the self-service kiosk

New User Steps:

1. Approach kiosk
 2. Register / Log in to campus card
3. Browse menu and select items
4. Add items to cart
5. Enter payment details
6. Confirm order
7. Collect receipt and food

Returning User Steps:

1. Approach kiosk
2. Log in quickly with campus card
3. Select frequently ordered items / browse menu
4. Confirm order and pay
5. Collect receipt and food

Hierarchical Task Analysis (HTA) Example:

0. Buy Food
├─ 1. Log in / Register (New: create account; Returning:
quick login)
├─ 2. Select menu items
├─ 3. Add items to cart
├─ 4. Enter payment info (New user: manual; Returning: saved)
├─ 5. Confirm order
└─ 6. Collect receipt and food

Key Point: New users have extra registration/payment steps, returning users can complete
transaction faster.

Summary:

 Requirements include functional, data, environmental, user, and usability needs.

 Data gathering uses questionnaires, interviews, observation, and documentation.
 Structured interview ensures consistent usability feedback.
 Task analysis differentiates new vs returning users for better design efficiency.

Q5. Hospital Appointment System

Scenario: A hospital wants a system to schedule appointments with doctors.

Questions:
[Link] five key issues in establishing requirements (Who, What, Functions, Constraints,
Success Criteria).
2. Choose suitable data gathering techniques (questionnaire, group interview, observation).
Justify your choice.

3. Explain qualitative vs quantitative data you will collect.

4. Suggest formative and summative evaluation plans to improve usability.

5. Prepare observation types for evaluating user interaction with the system.

Answer: 1. Five Key Issues in Establishing Requirements

Issue Example
Who Patients, doctors, nurses, administrative staff.
Book, reschedule, cancel appointments; receive notifications; access patient
What
history.
Appointment scheduling, reminders, patient record lookup, secure
Functions
messaging.
Constraints Data privacy (HIPAA), working hours, system downtime, multiple devices.
Success Reduced waiting time, accurate bookings, high user satisfaction, minimal
Criteria errors.

2. Data Gathering Techniques

Technique Justification
Questionnaire Collect opinions from many patients on ease of booking and satisfaction.
Group Interview Understand hospital staff workflows and challenges in scheduling.
Watch patients and staff using current appointment system to identify pain
Observation
points.

3. Qualitative vs Quantitative Data

Type Example
Qualitative User feedback, suggestions, difficulties faced, open-ended responses.
Average booking time, number of errors, number of missed appointments,
Quantitative
system usage stats.

4. Formative and Summative Evaluation Plans

Type Plan
Test prototypes with patients and staff during development; fix interface issues;
Formative
improve navigation and notifications.
Evaluate final system after deployment; measure success criteria (time saved,
Summative
satisfaction, error reduction).
5. Observation Types

1. Direct Observation: Watch users interacting with system in real-time.

2. Indirect Observation: Review system logs or video recordings.
3. Participant Observation: Observer interacts with users to understand workflow.
4. Non-Participant Observation: Observer stays passive and records behavior.
5. Covert / Overt Observation: Users may or may not know they are being observed.

Summary:

 Identify key issues with Who, What, Functions, Constraints, Success Criteria.
 Use questionnaires, group interviews, and observation to gather data.
 Collect qualitative feedback and quantitative metrics for improvements.
 Perform formative evaluation during development, summative evaluation after
deployment.
 Use different observation types to monitor user interaction and system effectiveness.

6. Nuclear Power Plant Control System

Scenario: You are designing a control system for a nuclear plant.

Questions:

1. Identify functional, data, environmental, user, and usability requirements.

2. Choose data collection methods (notes, audio, video) for expert operators.
3. Explain structured and unstructured interviews with examples for gathering
operator insights.
 4. Suggest types of evaluation (formative, summative, expert) and how why, what,
where, and when applies.

Answers:

1. Requirements

Type Example Requirement

Monitor reactor status, control temperature, manage emergency shutdowns,
Functional
log incidents.
Real-time sensor data (temperature, pressure, radiation), system logs, alerts,
Data
operator actions.
Control room with high noise reduction, proper lighting, multiple monitors,
Environmental
secure access.
User Expert operators with specialized training, maintenance staff, engineers.
Interface must be highly reliable, clear, with minimal steps for critical
Usability
actions, easy-to-read displays, error prevention.

2. Data Collection Methods

Method Justification
Notes Record key observations during operator interactions; quick and cheap.
Audio Capture operator explanations during procedures for detailed analysis.
Analyze workflow, control panel interactions, and emergency drills accurately;
Video
useful for training and evaluation.

3. Structured vs Unstructured Interviews

Type Example in Nuclear Plant

Structured Predefined questions: “How often do you perform system checks?”;
Interview “What steps do you follow for reactor shutdown?” Ensures consistency.
Unstructured Open discussion: “Describe challenges you face during emergency
Interview operations.” Allows deeper insights and unexpected information.

4. Types of Evaluation

Type Purpose / Example

Evaluate interface prototypes during design; identify usability issues before
Formative
deployment.
Evaluate final system performance after implementation; measure
Summative
reliability, efficiency, and error reduction.
Expert Specialists review the interface for compliance with safety, usability, and
Evaluation operational standards.

Why, What, Where, When in Evaluation:

  Why: To ensure system safety, usability, and operator efficiency.
 What: Tasks like reactor monitoring, emergency shutdown, logging incidents.
 Where: In control room simulation or real control environment.
 When: During design (formative), after deployment (summative), and periodically
for audits.

Summary:

 Requirements focus on functionality, data, environment, users, usability.

 Notes, audio, and video are suitable for collecting detailed operator insights.
 Use structured interviews for consistent data, unstructured for deeper
understanding.
 Formative, summative, and expert evaluations ensure the system is safe, efficient,
and usable.
 Evaluation follows why, what, where, and when framework for clarity.

Q7. Online Shopping System

Scenario: Design a checkout process for an e-commerce website.
Questions:

1. Perform a task analysis for new vs returning users (adding items, payment, delivery).
2. Identify common interface types and which would improve usability (GUI, Web,
Mobile).
3. Suggest ways to collect feedback (questionnaires, observation, research similar
products).
4. Explain how data analysis, interpretation, and presentation can improve the
checkout process.
Answers:

1. Task Analysis: New vs Returning Users

Step New User Returning User

1 Register / Create account Login with existing account
2 Browse items and add to cart Browse or select frequently bought items
3 Enter billing information Use saved billing info
4 Enter delivery address Use saved address or update
5 Select payment method Use saved payment method
6 Review order Review order
7 Confirm and place order Confirm and place order
8 Receive order confirmation Receive order confirmation

2. Common Interface Types & Usability

Interface Type Use in Checkout Reason

Desktop website Intuitive, easy navigation with visual cues and clear
GUI
checkout buttons
Accessible from multiple devices without
Web Interface Browser-based access
installation
Mobile Quick access, responsive design, mobile-friendly
Shopping via app
Interface forms

3. Ways to Collect Feedback

Technique Example
Ask users about ease of navigation, payment, and delivery
Questionnaires
selection.
Watch users go through checkout process to spot confusion or
Observation
delays.
Research Similar Analyze competitor websites/apps for best practices and pain
Products points.

4. Data Analysis, Interpretation, and Presentation

 Data Analysis: Track metrics like time to complete checkout, abandoned carts, and
error rates.
 Interpretation: Identify patterns, e.g., users abandoning checkout at payment step →
indicates confusing payment interface.
 Presentation: Use graphs, dashboards, or charts to communicate findings to the
design team.

Outcome: Helps simplify steps, improve usability, reduce errors, and increase successful
purchases.
Summary:

 Task analysis distinguishes new vs returning user flows.

 GUI, Web, and Mobile interfaces improve usability.
 Feedback collected via questionnaires, observation, and product research.
 Data analysis helps identify problems and optimize checkout process.