Lec 19: Case Study on Prototype Evaluation - II

Design and Implementation of Human-Computer Interfaces: Prototype Building and Evaluation

Overview of the Lecture

• The lecture continues the discussion on prototype building and evaluation, specifically focusing on heuristic evaluation methods.

• Recap of previous discussions about building a calendar application aimed at helping students manage academic activities.

Functional Hierarchy of the Calendar App

• The app supports four top-level functions: display calendar, set reminders, set background, and synchronize.

• Emphasis on creating a prototype that supports three main functions: setting backgrounds, setting reminders, and displaying calendars.

Prototype Details

• Introduction to a medium fidelity vertical prototype built using Figma; it includes various views such as month view, specific date view, year view, and background view.

• Although designed as a vertical prototype for screen transitions, it will also be evaluated as a horizontal prototype focusing on specific interfaces.

Interface Walkthrough

Year View

• In the year view interface, users can see months listed at the top; selecting a month displays corresponding days.

Month View

• Users can select specific dates to view scheduled events. For example, selecting July 12 shows courses and assignments due that day.

Event Management

• Users can create events by selecting a date; an interface allows inputting event details like name, start time, end time, and description with options to save or delete.

Background Customization

• The background view allows users to change themes (e.g., dark theme or custom selections from their device).

Additional Views

• Deadline views show all deadlines for selected dates while timetable views present schedules for specific days.

Error Prevention Features

Heuristic Evaluation of a Prototype

Overview of Heuristic Evaluation

• The discussion begins with the importance of closing the app before confirmatory messages appear, leading into an evaluation of the prototype using Nielsen's 10 heuristics.

Nielsen's 10 Heuristics

• The ten heuristics include:

• Visibility of system status

• Match between system and real world

• User control and freedom

• Consistency and standards

• Error prevention

• Recognition rather than recall

• Flexibility and efficiency of use

• Aesthetic and minimalist design

• Help users recognize, diagnose, and recover from errors

• Help and documentation

Detailed Analysis by Designer

Visibility of System Status

• The designer emphasizes that users should be kept informed about system status through timely feedback. Key features include:

• Highlighted current date for easy identification.

• Intuitive month navigation via dragging.

Match Between System and Real World

• The design uses familiar language and visual cues to enhance user understanding:

• Color coding (red for deadlines, green for success).

User Control and Freedom

• Users need clear options to exit unwanted states easily. Features supporting this heuristic include:

• Multiple themes allowing user preference.

Consistency and Standards

• Consistent color coding across different views supports user familiarity. However, there is no mention of adherence to established standards.

Error Prevention

• The designer incorporates prompts for confirmation during changes to prevent errors. Additional measures include:

• A dedicated view for accurate time entry when creating events.

Recognition Rather Than Recall

Design Principles in User Interface

Recognition Over Recall

• The designer emphasizes that input fields contain descriptive text, aiding user recognition rather than requiring recall. This design choice enhances usability by making it easier for users to understand what information is needed.

Flexibility and Efficiency of Use

• The application features a simple interface perceived as accessible for all user categories—novice, intermittent, and expert. The designer believes this uniformity allows any user to navigate the system effectively.

Aesthetic and Minimalist Design

• The designer advocates for minimal dialogue content, ensuring only relevant information is presented. This approach prevents overwhelming users and encourages continued engagement with the application.

Error Recognition and Recovery

• Users can delete events with a confirmation prompt, allowing them to revert changes easily. The design includes indicators for potential errors when setting deadlines, helping users recognize issues promptly.

Help and Documentation Support

• The calendar mimics familiar functionalities, reducing the need for extensive documentation. Precise titles serve as implicit guidance, while brief explanations are provided where necessary to assist users in understanding various functions.

Evaluation of Heuristic Principles

Heuristic Evaluation Process

• A heuristic evaluation involves 3 to 5 domain experts assessing the interface against established heuristics. Each evaluator compiles reports identifying concerns regarding usability.

Findings from Evaluator One

• Visibility of system status was deemed unsatisfactory; no feedback is given upon event creation success or failure.

• Match between system and real world was satisfied; terminology used aligns well with common language.

• User control was not supported due to lack of undo/redo options; consistency issues were noted compared to standard calendar applications.

Positive Aspects Noted by Evaluator One

• Error prevention mechanisms are effective; confirmation prompts help prevent accidental deletions or resets.

• Recognition over recall is supported through descriptive input field texts that guide users during event creation.

Further Evaluation Insights

Findings from Evaluator Two

• Similar concerns about visibility of system status were raised; actions like adding events do not provide clear feedback on success or failure.

Heuristic Evaluation of a Prototype

Evaluator Insights on User Interface Design

• The evaluator notes that cautionary instructions like "delete" and "reset" are indicated in green, while user control features such as saving are supported. A prompt appears to confirm deletion, allowing for event edits post-creation.

• Error prevention is supported through pop-ups that guide users in entering date and time correctly. Familiar icons enhance recognition over recall when adding or managing events.

• However, the system lacks support for helping users diagnose errors; for instance, if a PNG image fails to load as a background, no information is provided about the failure.

• Visibility of system status is not supported during event management actions. While familiar icons are used effectively, inconsistencies exist in button sizes which may confuse users.

• Overall design supports flexibility for both novice and experienced users with an aesthetic focus on minimalism. However, error recovery mechanisms are inadequate since reasons for failed event creation aren't communicated.

Summary of Evaluators' Opinions

• Different evaluators provide varied feedback; common concerns will be compiled to refine the design further. Notably, visibility of system status was consistently flagged as unsupported across evaluations.

• In terms of matching systems with real-world conventions, all evaluators agreed that this aspect was well-supported. User control received mixed reviews but generally leaned towards being supported.

• Consistency and standards were largely deemed unsupported by all evaluators. Error prevention measures were recognized positively alongside other supportive heuristics like flexibility and minimalist design.

Recommendations for Design Refinement

• To address identified issues, it’s suggested to implement visible messages indicating system status after creating or editing events. This could improve user understanding significantly.

• Incorporating undo/redo functionality was highlighted as necessary by one evaluator to enhance user experience during event management tasks.

• Suggestions also include repositioning buttons on the interface to align with user expectations better and displaying error messages when events fail due to missing information.

Conclusion on Heuristic Evaluation Process

• Despite some heuristics being unsupported (like help documentation), the simplicity of the application suggests that extensive documentation may not be required since most functionalities can be intuitively understood by users.

• The evaluation process emphasizes checking design quality against heuristic principles and determining whether improvements are needed based on evaluator feedback regarding usability aspects.

Understanding the Impact of Climate Change

Introduction to Climate Change

• The speaker introduces climate change as a pressing global issue, emphasizing its widespread effects on ecosystems and human societies.

• A brief overview of the scientific consensus regarding climate change is presented, highlighting the role of greenhouse gases in global warming.

• The urgency of addressing climate change is underscored, with references to recent extreme weather events as evidence of its impact.

Causes of Climate Change

• Human activities, particularly fossil fuel combustion and deforestation, are identified as primary contributors to increased carbon emissions.

• The speaker discusses natural factors that influence climate but emphasizes that current changes are predominantly anthropogenic.

• A comparison between historical climate patterns and current trends illustrates the unprecedented rate of change observed today.

Consequences of Climate Change

• Rising sea levels due to melting ice caps pose significant risks to coastal communities worldwide.

• Changes in precipitation patterns lead to droughts in some regions and flooding in others, affecting agriculture and water supply.

• Biodiversity loss is highlighted as a critical consequence, with many species facing extinction due to habitat changes.

Mitigation Strategies

• The importance of transitioning to renewable energy sources such as solar and wind power is discussed as a key mitigation strategy.

• Reforestation efforts are emphasized for their dual benefits: carbon sequestration and biodiversity enhancement.

• Policy measures at local, national, and international levels are necessary for effective climate action; examples include carbon pricing and emission regulations.

Conclusion: Call to Action

• The speaker concludes with a call for collective action from individuals, businesses, and governments to combat climate change effectively.