Lecture 4: Data Analysis & Presentation PDF

Lecture 4: Data analysis &Presentation The Process of Interaction Design  Data analysis &Presentation ❑ Data analysis and presentation in Human-Computer Interaction (HCI) is crucial for understanding how users interact with systems and how these interactions can be...

Lecture 4: Data analysis &Presentation The Process of Interaction Design  Data analysis &Presentation ❑ Data analysis and presentation in Human-Computer Interaction (HCI) is crucial for understanding how users interact with systems and how these interactions can be improved to make systems more efficient, effective, and user-friendly. ❑ This process involves collecting, analyzing, and presenting data in ways that help designers and researchers make informed decisions about the design and usability of interactive systems.  A quantitative Data ❑ A discrete quantitative variable is one that can only take specific numeric values number of needle punctures, number of pregnancies number of hospitalizations. ❑ A continuous data is one that in theory could take any value in an interval are body mass, height, blood pressure ❑ Qualitative data with unordered categories is referred to as nominal; qualitative data with ordered categories is referred to as ordinal  Data Analysis Techniques (Quantitative Analysis ) quantitative analysis collects numerical analysis such as frequency, quantity, and magnitude. quantitative analysis aims to provide numerical descriptions and explanations of the data. ❑ Types of analysis Descriptive Statistics Inferential Statistics Time Series Analysis Quantitative Analysis (Descriptive Statistics)  Data Analysis Techniques (Inferential Analysis ) Techniques like t-tests, ANOVA, or regression analysis can be used to identify significant differences or relationships in the data  Data Analysis Techniques (Time Series Analysis) Useful when analyzing user interaction logs over time to identify patterns or trends.  Data Analysis Techniques (Qualitative Analysis ) ❑ Qualitative analysis collects non-numerical data such as opinions, attitudes, and behaviors. ❑ Qualitative analysis aims to understand the meaning behind the data ❑ Types of analysis Thematic Analysis (Identifying common themes in user feedback or observational data) Content Analysis (categorizing user feedback to understand recurring patterns.) Affinity Diagrams (Grouping similar observations or data points to extract insight)  Data Presentation ❑It refers to how data is structured, visualized, and communicated to users through an interface, enabling them to interpret and interact with the information effectively. ❑The design of data representation directly impacts usability, cognition, decision-making, and overall user experience.  Data Visualization Description: Translating raw data into graphical forms such as charts, graphs, and maps that help users quickly grasp insights or trends. Examples: Bar Charts: Used to compare categories or datasets over time. Line Graphs: Effective for showing trends or changes over continuous periods. Pie Charts: Used for representing proportional data or percentages. Heatmaps: Useful for displaying data intensity or frequency (e.g., web click tracking). Data Visualization Data Visualization  2. Multimodal Data Representation Description: Using multiple sensory modalities (e.g., visual, auditory, tactile) to represent data in a way that leverages different human perceptual systems. Examples: ❑Visual and Auditory Alerts: In real-time monitoring, critical data might be represented visually on a screen and accompanied by auditory alarms for immediate attention. ❑Tactile Feedback: Wearable devices (like fitness trackers) use vibrations to communicate activity data, such as step goals or heart rate changes.  3. Icons and Pictograms Description: Representing data or actions using simplified graphical symbols. Icons convey meaning quickly without relying on text. Examples: Weather Apps: Icons representing sun, clouds, or rain help users understand weather conditions at a glance. File Management Systems: Use icons to represent different file types (e.g., folders, documents, images) to enhance data organization and interaction.  4. 3D and Spatial Representation Representing data in three dimensions or using spatial techniques to enhance understanding, particularly for complex datasets. Examples: Medical Imaging: 3D representations of organs or biological systems for diagnosis and surgical planning. Geographical Information Systems (GIS): Using 3D maps to represent terrain, urban structures, or meteorological data.  Temporal Data Representation Description: Representing data over time, which is particularly important for tracking trends, changes, and events. Examples: Timelines: Used for visualizing historical events or project schedules. Animations: Real-time data updating, or representing change over time (e.g., weather changes in a forecast)  Narrative-Based Representation Description: Integrating data into a story or sequence of events that guide the user through the information. Examples: Interactive Stories: News websites or educational platforms that present data in a narrative format, using visualizations, text, and user interactions to tell a story.  Data Presentation ⇒ Use Cases ❑In each use case, the actor represents the individual or system interacting with the data, while the system provides appropriate data representations to meet the actor's goals.  What Are Requirements? ❑ Requirements are conditions or capabilities that a product, system, or project must meet or possess to satisfy the needs or expectations of users, stakeholders, or clients. ❑ They define the desired functionality, behavior, and attributes of a system or solution and serve as the foundation for design, development, and testing processes. ❑ In simple terms, requirements describe what a system or product should do and how it should perform.  1. Functional Requirements ❑ Describe what the system or product must do, including the specific functions, tasks, or operations it should support. Example ❑ A user can log into the system using a username and password. ❑ The system should allow users to generate financial reports. ❑ The application must support data filtering by date range  2. Non-Functional Requirements ❑ Specify the system's qualities or constraints, such as performance, usability, security, and scalability Example ❖The system must respond to user input within 2 seconds (performance). ❖The application should be accessible on mobile devices (usability). ❖Data must be encrypted in transit (security).  3. System Requirements Definition: Detail the hardware, software, or infrastructure that the system needs to operate effectively. Examples: ❑ The system must run on Windows, macOS, and Linux. ❑ The database should support up to 10,000 concurrent users.  4. User Requirements Definition: Represent the needs or expectations of the end users, describing how the system should behave from a user’s perspective. Examples: ❑ The user should be able to search for products by keyword. ❑ The interface should provide clear error messages when input is invalid Exercise Establish both the functional and non-functional requirements for creating GPS Smartwatch Functional Requirements ❑ Receive commands by voice ❑ Telling user his directions using sound ❑ Alert user when misdirection (e.g., use vibration) ❑ Save favorites locations Non Functional Requirements ❑ Light (weight < 30 gm) and Small (area < 10 cm2) ❑ Opened in less than 1 second, and find location in less than 2 seconds ❑ Fashionable ❑ Released in the market before next Summer  Requirements Types Data Requirements ⇒ capture the type, volatility, size/amount, persistence, accuracy, sharing, and value of the required data Environment Requirements ⇒ refer to the circumstances (and the context of use) in which the interactive product will operate Exercise Establish data and environmental requirements for creating GPS Smartwatch Importance of Requirements ❑ Clarify Objectives: Clearly defined requirements help ensure that all stakeholders have a shared understanding of the project goals. ❑ Guide Design and Development: Requirements form the basis for creating designs and developing features that meet user and business needs. ❑ Provide a Basis for Testing: Requirements act as benchmarks to test whether the system or product functions as intended. ❑ Facilitate Communication: They bridge the gap between business stakeholders, users, and the development team, ensuring everyone is aligned. ❑ Manage Scope: Well-defined requirements help prevent scope creep by identifying what the system will and will not include.  Interaction Design Approaches ❑ Interaction Design Approaches refer to different methodologies and strategies used in designing user interfaces and systems that focus on how users interact with products, applications, or services. ❑ These approaches guide designers in creating intuitive, effective, and enjoyable user experiences by focusing on aspects like user behavior, system functionality, and design creativity.  1. User Centered Design User-centered design (UCD) is an iterative design process in which designers focus on the users and their needs in each phase of the design process. Phases in User-centered Design  Phases in User-centered Design ❑ each iteration of the UCD approach involves four distinct phases. ❑ First, as designers working in teams, we try to understand the context in which users may use a system. ❑ Then, we identify and specify the users’ requirements. ❑ A design phase follows, in which the design team develops solutions. ❑ The team then proceeds to an evaluation phase  2. Activity-Centered Design ❑The activity-focused design, or also called human centered design, is about the actions people need or want to take to reach a goal ❑Imagine you were asked to design an app to control lightbulbs from your mobile device. The first step in task analysis is to determine the most important goal or goals of a person who uses the app. Do they want to simply turn the lights on and off? Control them automatically based on the time of day? Connect them to a motion sensor? The second step is to determine the tasks that a person would have to perform to reach those goals. To set the lightbulb to “on” (goal),, turning on the mobile device’s Bluetooth (task), connecting the bulb to the app (task) and turning on the lightbulb in the app (task). Streamlining is the process used to simplify or eliminate unnecessary work-related tasks to improve the efficiency of processes in businesses or organizations. There are many activity-focused approaches to UX design, including task analysis, jobs to be done, activity theory and activity-based design.  Task Analysis ❑ Task analysis is the understanding of a user’s task. ❑ It’s a combination of understanding the user, their task, and their environment ❑ There are two approaches to task analysis, which can however be combined: Cognitive (Examines the mental processes behind task performance, such as decision-making and problem-solving.) Hierarchical (Focuses on breaking down a task into subtasks and actions.)  3. System-Centered Design Definition: This approach focuses on the technical aspects and goals of the system itself rather than on the user's needs or tasks. Example: Designing a backend database management system where the focus is on system performance and data integrity rather than user interaction simplicity.  4. Genius Design Definition: This approach relies on the creativity, intuition, and experience of the designer rather than direct user involvement. Example: A designer creates a unique website interface based on their artistic vision, with minimal user testing, relying on their deep understanding of design principles.  Who Are the Users? ❑ End Users: These are the people who will directly interact with the system or product. ❑ They are the primary focus in most interaction design approaches, especially in User-Centered Design. Example: A person using an app to order food delivery.  Who Are the Users? Stakeholders: These individuals have an interest in the system but may not interact with it directly. Stakeholders can include clients, project managers, investors, or decision-makers within an organization. Example: A restaurant owner who monitors sales through the app but doesn’t use it as a customer.  Who Are the Users? Power Users: ❑ These are highly experienced users who are deeply familiar with the system’s functions. ❑ They often provide valuable insights into advanced features or workflow optimizations. Example: An IT specialist using advanced settings in a database system.  Who Are the Users? ❑ Novice Users: These users are new to the system and may need more guidance, tutorials, or simpler interfaces to understand how to use the product effectively. ❑ Example: A first-time user of a financial tracking tool.  Who Are the Users? Secondary Users: Individuals who interact with the system less frequently or indirectly but still have some level of engagement with it. Example: A teacher monitoring students' progress through an educational platform.  level of user involvement ❑ In interaction design, the level of user involvement can vary greatly depending on the project goals, resources, and the design approach. ❑ These levels typically fall into three categories: High, Medium, and Low involvement, each representing different extents to which users are involved in the design and development process. References Chapter 10, Establishing Requirements, “Interaction Design, Beyond HCI”, 4th edition