User Centered Design PDF

USER CENTERED DESIGN By Dr. Ahmed Gamal Abdellatif  Outlines 3I INTRODUCTION To UCD II WATERFALL , ITERATIVE, and SPIRAL MODELS III 3 TECHNIQUES FOR UNDERSTANDING USERS & TASKS IV CASE STUDY V 3 REQUIREMENTS ANALYSIS VI DISCUSSION User-C...

USER CENTERED DESIGN By Dr. Ahmed Gamal Abdellatif  Outlines 3I INTRODUCTION To UCD II WATERFALL , ITERATIVE, and SPIRAL MODELS III 3 TECHNIQUES FOR UNDERSTANDING USERS & TASKS IV CASE STUDY V 3 REQUIREMENTS ANALYSIS VI DISCUSSION User-Centered Design (UCD) is a common approach in designing user interfaces that aims to optimize the user experience by involving users in the design process. Here is a brief overview of the standard approach to user-centered design:  Understand Users: Research and comprehend the target users' needs, preferences, and capabilities.  Define Requirements: Specify interface functionalities, interactions, and features based on user insights.  Design: Create prototypes and designs, including wireframes and mockups, to visualize the interface.  Evaluate: Test designs with real users through usability testing and feedback to identify issues.  Iterate: Refine designs based on user feedback and make incremental improvements.  Implement: Develop the final interface following usability and accessibility best practices.  Test: Conduct final tests to ensure the interface meets user needs and functions as intended.  Launch and Monitor: Deploy the interface, gather user feedback, and make ongoing improvements based on usage patterns. TRADITIONAL SOFTWARE ENGINEERING PROCESS: WATERFALL MODEL Why The WATERFALL MODEL is Bad For DCD?  User interface design is risky So we’re likely to get it wrong.  Users are not involved in validation until acceptance testing So we won’t find out until the end.  UI flaws often cause changes in requirements and design So we have to throw away carefully-written and tested code. Also, The waterfall model's linear and sequential nature, limited flexibility, lack of continuous user involvement, and inadequate support for iteration make it less suitable for UCD, which depends on flexibility, iteration, and continuous user feedback to create good UCD products. 5 ITERATIVE DESIGN MODEL 6 SPIRAL MODEL In conclusion, the iterative design model is more focused on continuous user feedback and rapid design iterations. At the same time, the spiral model controls risk management and iterative development based on risk analysis, making them suitable for different design contexts based on the project's requirements and risk profile. Steps for UCD  User analysis: who is the user?  Task Analysis: what does the user need to do?  Domain Analysis: what is the context the user works in(the people and things involved)?  Requirements Analysis: what requirements do the preceding three analyses impose on the design? 8  TECHNIQUES FOR UNDERSTANDING USERS CONTEXT & TASKS  Techniques for Understanding Users:  User Interviews: Conduct one-on-one interviews with users to gather detailed information about their needs, preferences, and pain points.  Surveys: Distribute surveys to a larger user base to collect quantitative data about user demographics, behaviors, and preferences.  Persona Creation: Develop fictional representations of target users based on research data to better understand user goals, motivations, and behaviors.  Contextual Inquiry: Observe users in their natural environment to understand how they interact with a product or perform tasks.  Focus Groups: Bring together a small group of users to discuss their experiences, perceptions, and expectations related to the interface.  User Journey Mapping: Visualize the user's interactions with a product or service across various touch points to identify pain points and opportunities for improvement. 9  USER ANALYSIS 1. Who are the users: novices or experts? 2. What are users trying to accomplish? 3. How often will the user be using the system? 4. Should the design emphasize ease of use and learning or efficiency? 5. What information do they need to accomplish their task? 6. How easily can they identify the information they need and the steps needed to accomplish their tasks? 7. Is the information and task structures accessible to everyone?  Also Designer must analysis the following:  Ethnographics: Age, gender, ethnicity.  Skill level: Novice or Knowledgeable, intermittent user  Mental or Physical abilities  Knowledge  Domain experience: Application experience.  Environment: Noisy, quiet, inside, outside…  Communication patterns. 10  Techniques for Understanding Tasks:  Task Analysis: Break down tasks into smaller steps to understand the sequence of actions users perform to accomplish goals.  Cognitive Walkthrough: Simulate user interactions with the interface to identify potential usability issues and evaluate the interface's learnability.  Card Sorting: Ask users to organize content or features into categories to understand how they mentally structure information.  Prototyping: Create low-fidelity prototypes to test task flows and interactions with users before finalizing the design.  Usability Testing: Observe users as they perform tasks using the interface to identify usability issues and gather feedback for improvement.  Heuristic Evaluation: Use established usability principles (heuristics) to evaluate the interface design and identify potential usability problems. 11  Techniques for Understanding Context:  Field Studies: Conduct on-site visits to observe users in their natural environment and understand how context influences their interactions.  Diary Studies: Ask users to keep a diary of their interactions with a product or service to gain insights into their behaviors and needs over time.  Competitive Analysis: Analyze competitors' interfaces to identify best practices and areas for differentiation in your design.  Stakeholder Interviews: Engage with stakeholders involved in the project to understand business goals and constraints that may impact the design decisions. Finally, by employing a combination of these techniques, designers can gain a comprehensive understanding of users, tasks, and the context in which the interface will be used, leading to the development of user-centric and intuitive interfaces. 12 CASE STUDY :THE OLYMPIC MESSAGE SYSTEM 13 DOMAIN ANALYSIS 14 15 16 REQUIREMENTS ANALYSIS 17 User, task, and domain analysis feed into a more general process called requirements analysis, which creates a description of the system's desired functionality and other nonfunctional properties (like performance, security, and capacity). Without user and task analysis, requirements are incomplete. User and task analysis contribute additional functionality (tasks that users need to do, which may not be evident from the domain analysis alone), as well as nonfunctional requirements about usability (like how efficient certain tasks should be, how learnable, or how memorable) and about other properties of the system as well (e.g., accommodation for users’ physical limitations, like impaired vision). 18  EXAMPLE PROBLEM STATEMENT: Many parents want their kids to have fun, but they don’t wish to worry about if their child is ok or not. Many kids don’t want to have their parents worry about them, but they don’t want to have to answer the phone or text their parents, either because they're too busy to answer, or simply don't want to talk to them in front of their friends. Parents don't want to interfere so much that their kids are annoyed by them, but this happens all too often when parents call frequently asking where their child is and what they are up to. If the child is a teenager, those caring but incessant calls can cause an emotional rift between the child and the parents. CheckIn gives the parents security and the kids safe independence. With CheckIn, a kid can tell their parents they’re ok and tell them where they are simply, efficiently, and without interfering with their current activity. Parents need to be able to set dates and times for reminders and view a log of all of the places where their children have checked in. CheckIn makes it easy for parents and their children to get along. 19  ANALYSIS User Analysis: We have two classes of users: parents and their children. CHARACTERISTICS: 20 PERSONAS: INTERVIEW RESULTS: TASK ANALYSIS 21 22 Thanks for Your Attention 23