Study Document PDF

Week 1 - Interviews User Needs & Interviews Key Concepts Understanding User Needs: Focus on user perspectives for effective design. Methods for User Focus: Interviews, workshops, low-fi prototyping, and evaluations. Importance of Including Users: Ensures that the delivered produ...

Week 1 - Interviews User Needs & Interviews Key Concepts Understanding User Needs: Focus on user perspectives for effective design. Methods for User Focus: Interviews, workshops, low-fi prototyping, and evaluations. Importance of Including Users: Ensures that the delivered product matches user expectations. Interviews Purpose: To gain insight into user needs, operations, and processes. Planning: ○ Define target interviewees: users, stakeholders. ○ Prepare questions: What do they do? How do they do it? What information do they need? Process: ○ 5 Steps: 1. Introduction: Goals, ethical considerations, consent. 2. Warm-up: Easy questions to build rapport. 3. Main Session: Logical and clear questions (closed/open-ended). 4. Cool-off: Simple questions to ease tension. 5. Closing: Summarize insights, thank participants. Key Interview Tips Avoid jargon, compound sentences, leading questions, and biases. Use tools like audio/video recording or note-taking for data capture. Summarize interview data effectively by identifying common patterns and examples. Application Example Case Study: Developing an app for personalized children's stories using AI and parental voice mimicry. ○ Requires interviewing a parent and a child (non-reader). ○ Focus on: User experience (UX) goals: nurture, relatedness, and joy. Practical features like highlighted text and automated page-turning. Individual Project  Analyze user groups. Conduct interviews with two individuals. Define UX goals and write a detailed report. W2_1_h2024_User Group Analysis Purpose of User Group Analysis Understand user needs by analyzing specific groups. Helps create targeted designs by identifying user characteristics and contexts. Key Components: 1. Who: Background information on the user group (age, gender, education, abilities, computer knowledge). 2. Why: Primary goals and motivations for using the system. 3. What: Technical equipment and tools users will interact with. 4. Where: Physical and social environments where the system will be used. 5. When: Frequency and duration of system use. 6. Importance: Prioritizing user groups to focus design efforts. Steps for Group Analysis: Identify user groups and their defining characteristics. Conduct interviews and summarize results. Create user stories and tasks to reflect user needs and goals. Individual Project Tasks: Interview one parent and one child (preferably non-reader). Set UX goals for each group and analyze findings in a report. Example project idea: A children’s storytelling app using AI to mimic a parent’s voice. W2_2_h2024_UX Goals Purpose of UX Goals Define and measure the intended user experience. Influence design decisions by setting emotional and functional benchmarks. What are UX Goals?  Based on ISO 9241-210: Focus on perceptions, emotions, and usability. Types: ○ Momentary UX: Immediate impressions. ○ Episodic UX: Experiences over a specific timeframe. ○ Cumulative UX: Long-term perceptions shaped by repeated interactions. Desirable vs. Undesirable UX Factors: Desirable: Fun, engaging, rewarding, motivating, surprising. Undesirable: Frustrating, boring, annoying, patronizing. Designing for Specific UX Goals: Example: A parking system in Reykjavik analyzed for workflow and design flaws. ○ Issue: Redundant steps like turning on the screen before starting. ○ Improvement: Streamline steps and create intuitive icons. Application in Projects: Define UX goals (e.g., security, joy, competence) for specific user groups. Use these goals to guide design and measure success in prototypes. Connections Between W2_1 and W2_2 User Group Analysis feeds into UX Goals by identifying user needs and challenges. Both documents emphasize the importance of understanding users in depth—context, equipment, and motivations—before setting experience goals. Real-world examples, like the AI storytelling app and the Reykjavik parking system, illustrate the application of these principles. Comprehensive Summary for Week 3 (W3 Files) W3 Content Overview Week 3 focuses on applying user-centered design principles through interviews, analyzing gathered data, and translating findings into actionable insights like UX goals and user stories. Key methods and concepts are outlined below. Key Topics and Insights 1. Importance of User Inclusion Early involvement ensures designs meet real user needs and expectations. Methods like interviews, observations, and workshops help capture the context of use and goals. 2. Conducting User Interviews Purpose: Understand user needs, challenges, and tasks in real-world settings. Steps: 1. Preparation: Define objectives, target groups, and interview structure. 2. Execution: Build rapport with introductory questions. Use both open-ended and specific queries. Record responses (audio, notes). 3. Post-Interview: Summarize and identify patterns. Highlight key user needs and behaviors. 3. Summarizing Findings Organize results from interviews and user observations into clear user profiles. Examples: ○ Define user goals like "ease of navigation" or "streamlined workflows." ○ Identify frustrations and areas for improvement. 4. UX Goals Derived from interview data to guide design decisions. Example Goals: ○ For Children: 1. Engagement: Fun and interactive storytelling. 2. Ease of Use: Simple navigation with visual cues. 3. Learning Support: Highlighted words for reading practice. ○ For Parents: 1. Control: Ability to select and manage content. 2. Safety: Secure settings and content filtering. 5. Defining User Stories Use format: "As a [user group], I want to [achieve goal] so that [reason]." Examples: ○ "As a parent, I want to record my voice reading a book so my child can feel connected." ○ "As a child, I want to choose stories using images so I can read independently." 6. Low-Fidelity Prototyping Early-stage design focused on structure and functionality, not aesthetics. Used to: ○ Validate navigation and interaction flows. ○ Gather quick feedback for iterative improvements. 7. Happy Paths Definition: The ideal sequence of steps a user takes to complete a task without errors. Importance: ○ Helps visualize smooth system usage. ○ Guides the design of user-friendly interfaces. 8. Steps to Build Effective Prototypes 1. Use UX goals as a blueprint. 2. Incorporate findings from interviews and user stories. 3. Ensure prototypes address both functional and emotional needs of users. 4. Test with real users to refine designs further. Study Notes for Exam Understand how to: ○ Conduct and summarize user interviews. ○ Translate interview findings into UX goals and user stories. ○ Create and test low-fidelity prototypes. ○ Define and utilize happy paths in design. Focus on connecting user needs to actionable design solutions. Comprehensive Summary for Week 4 (W4 Files) Group Assignment 1: Low-Fidelity Prototyping​W4_1_h2024_Group assign…​W4_1_h2024_Group assign… Purpose: Conduct a collaborative project to develop and test low-fidelity prototypes. Build on findings from user group analysis, interviews, and UX goals set individually. Key Components: 1. Summarizing Interview Results: ○ Identify user needs and patterns from collected data. 2. Defining UX Goals: ○ Establish goals tailored for different user groups. ○ Example: Children may prioritize enjoyment, while parents focus on control and security. 3. Exploring Existing Designs: ○ Analyze similar designs for inspiration and best practices. 4. Defining Tasks: ○ Create tasks that align with user stories to guide prototype functionality. 5. Happy Paths: ○ Outline ideal user workflows without errors. 6. Low-Fidelity Prototyping: ○ Use tools like sketches or basic wireframes to design interfaces. 7. Testing: ○ Evaluate the prototype through user feedback, focusing on ease of use and task success. Grading Criteria: Quality of results, adherence to project descriptions, and team collaboration are emphasized. Late submissions face penalties. Additional Notes: Group assignments are integral for future roles and learning the complete design cycle. Tasks and Happy Paths​W4_1_h2024_Group assign…​W4_1_h2024_Group assign… Defining Tasks:  Tasks should be realistic and fit the user's situation. Example: For a recipe app, a task might be, "Find a recipe for Monkfish." Tasks must state what should be done, not how. Happy Paths: Focus on seamless workflows where users complete tasks without encountering issues. Include logical navigation steps and interface feedback. Collaboration and Submission​W4_1_h2024_Group assign…​W4_1_h2024_Group assign… Group Formation: Teams consist of 3–4 members. Group assignments should be completed collaboratively, leveraging diverse insights from members. Submission Rules: Use predefined group names for project submissions. Ensure all members contribute equally. Feedback and Improvements: Review the feedback from individual tasks to improve prototypes. Study Focus for Exam: Be proficient in: ○ Summarizing user data to define UX goals. ○ Creating user tasks and prototyping workflows (happy paths). ○ Applying iterative design processes through feedback. Understand how group assignments integrate multiple UX design principles. This summary provides a thorough understanding of the Week 4 content, emphasizing teamwork, user-centered design, and low-fidelity prototyping. Let me know if you need additional clarifications or detailed examples! Comprehensive Summary for Week 5 (W5 Files) 1. Website Design​W5_1_h2024_Website desi…​W5_1_h2024_Website desi…: Purpose: Understand fundamental principles of web and app design. Utilize low-fidelity prototypes for structuring and testing. Key Topics: 1. Designing the Structure: ○ Focus on content organization (site maps, wireframes). ○ Prioritize user tasks over aesthetic elements. ○ Use grid layouts for consistent and responsive designs. 2. Helping Users Know Where They Are: ○ Use breadcrumbs and clear navigation headers/footers. ○ Highlight the user's location on the site for orientation. 3. Helping Users Navigate: ○ Use internal, outbound, and inbound links effectively. ○ Design menus with clear labels and intuitive placement. ○ Include navigation aids like buttons, drop-down lists, and search functionalities. 4. Designing for Mobile Devices: ○ Consider different screen sizes and resolutions. ○ Implement mobile-first designs where interaction is optimized for touch. Tools and Resources: Guidelines for web usability: www.usability.gov​:contentReference[oaicite:2]{index=2}. 2. Testing Low-Fidelity Prototypes​W5-2-Testing Low-Fideli…​W5-2-Testing Low-Fideli…: Goals: Validate design functionality before high-fidelity iterations. Identify usability problems and refine tasks for better alignment with user needs. Five Acts of Prototype Testing: 1. Friendly Welcome: ○ Build rapport with users to ensure honest feedback.  ○ Clarify the purpose of testing (e.g., improving the design, not evaluating the user). 2. Context Questions: ○ Gather insights into the user's background, preferences, and needs. 3. Prototype Introduction: ○ Explain the prototype's scope and limitations. ○ Encourage users to think aloud while interacting with the prototype. 4. Task Execution: ○ Provide realistic, goal-oriented tasks (e.g., "Find restrictions for visiting Geysir"). ○ Observe and document user behaviors, frustrations, and successes. 5. Debrief: ○ Collect feedback on likes, dislikes, and suggestions for improvement. Data Collection: Record user interactions (notes, quotes, observations). Use post-it notes to document positive (+) and negative (-) feedback. Reporting Results: Identify usability issues such as confusion, inability to complete tasks, and excessive time requirements. Present findings in an actionable format to guide future design iterations. 3. Connecting Prototypes and Tasks​W5-2-Testing Low-Fideli…​W5-2-Testing Low-Fideli…: Task Creation: Tasks should align with user stories but provide specific, testable scenarios. Example: ○ User Story: "As a user, I want to find a recipe for Monkfish." ○ Task: "Use the app to locate a Monkfish recipe for a dinner party." Design Alignment: Ensure prototypes are built to facilitate task completion. Refine tasks iteratively based on user feedback during testing. Exam Study Notes: 1. Focus on principles of website structure, navigation aids, and responsive design. 2. Understand the Five Acts of Prototype Testing and how to derive actionable insights.  3. Practice creating tasks that are specific, realistic, and aligned with user goals. This summary synthesizes Week 5 content into practical study material for exams. Let me know if you need further clarification or more examples! Comprehensive Summary for Week 6 (W6 Files) 1. Group Assignment 2: Intermediate Prototyping and Error Messages​W6_1_Group Assignment 2…​W6_1_Group Assignment 2… Purpose: Transition from low-fidelity to intermediate prototypes. Incorporate results from previous testing to refine designs. Include error messages to address user deviations from the happy path. Key Components: 1. Intermediate Design: ○ Add details such as colors, fonts, shapes, and interactivity. ○ Balance between simplicity and usability without overcomplicating the design. ○ Prototypes can include clickable elements to simulate user interactions. 2. Error Messages: ○ Should be polite, precise, and constructive. ○ Address user issues and guide them back to the happy path. ○ Use visual cues like colors to indicate severity. 3. Testing Intermediate Prototypes: ○ Conduct usability testing with real users. ○ Focus on task completion rates, user satisfaction, and feedback on new design elements. 4. Submission and Grading: ○ Projects must be submitted using predefined group names. ○ Grading emphasizes quality, adherence to guidelines, and timely delivery. ○ Collaboration is crucial; group members must contribute equally. 2. Steps for Prototyping​W6_1_Group Assignment 2…​W6_1_Group Assignment 2…: Stages: 1. Low-Fidelity: ○ Basic wireframes and sketches. ○ Focus on structure, not aesthetics. 2. Intermediate Design: ○ Add visual and functional details while ensuring usability. ○ Make prototypes partially interactive for testing specific flows. 3. Detailed/High-Fidelity: ○ Mimics the final product with full interactivity and realistic aesthetics. ○ Used for advanced usability testing and presentations. Key Benefits of Prototyping: Encourages team collaboration and stakeholder engagement. Allows early detection of design flaws. Helps prioritize user needs and refine goals. 3. Key Design Elements for Intermediate Prototypes​W6_1_Group Assignment 2…​W6_1_Group Assignment 2…: 1. Grouping and Layout: ○ Use Gestalt principles (proximity, similarity, closure) for intuitive interfaces. ○ Example: Group related tasks or information in visually distinct areas. 2. Colors and Accessibility: ○ Use colors strategically to enhance readability and highlight critical elements. ○ Consider users with color blindness; use patterns or shapes in addition to colors. 3. Typography and Text: ○ Ensure text legibility with appropriate font sizes, spacing, and alignment. ○ Maintain a consistent tone of voice that aligns with user expectations. 4. Movement and Sound: ○ Subtle animations or feedback sounds can enhance user experience. ○ Avoid excessive or distracting elements. 5. Error Messages and Happy Paths: ○ Design error messages to inform and assist users constructively. ○ Map out happy paths for each primary task to ensure smooth navigation. Exam Preparation Focus: 1. Understand the stages of prototyping:  ○ How low-fidelity, intermediate, and high-fidelity prototypes differ. ○ The importance of transitioning from low to intermediate fidelity. 2. Error Messaging: ○ Characteristics of effective error messages (politeness, clarity, guidance). ○ Techniques for incorporating feedback loops in designs. 3. Accessibility: ○ Principles of accessible design, including visual and auditory considerations. ○ Adapting interfaces for diverse user needs. 4. Testing: ○ Methods for gathering actionable feedback from intermediate prototypes. ○ Metrics to evaluate user success and satisfaction. This summary emphasizes the progression from basic prototypes to detailed intermediate designs, including testing and refinement processes. Let me know if you'd like any section expanded or additional examples provided! Comprehensive Summary for Week 7 (W7 Files) 1. Error Messages and Usability Testing​W7_1_Errormessages Thin… Purpose: To improve system usability by designing effective error messages and conducting usability testing. Key Concepts: 1. Error Messages: ○ Types: Information: Provide general updates or statuses. Warnings: Alert users about potential risks, often with options like "Yes," "No," and "Cancel." Errors: Notify users about issues requiring immediate action. ○ Design Guidelines: Use clear, polite, and constructive language. Avoid error codes unless necessary for maintenance. Provide actionable instructions to resolve the issue. Example: Avoid messages like “Error 11: You are too impatient”; instead, clarify the problem constructively.  2. Severity of Usability Problems: ○ Minor: Minimal user disruption (e.g., slight confusion). ○ Moderate: Delays user tasks and causes frustration. ○ Severe: Prevents task completion entirely. 3. Designing for "Unhappy Paths": ○ Define scenarios where users deviate from the ideal workflow. ○ Create responsive designs that assist users in recovering from errors. 2. Think-Aloud Testing​W7_1_Errormessages Thin… Purpose: Collect real-time feedback on user experiences and identify usability issues. Process: 1. Preparation: ○ Develop realistic tasks for users to complete during the session. ○ Set clear objectives, focusing on problem areas or specific design elements. 2. Execution: ○ Encourage users to verbalize their thoughts, expectations, and frustrations as they interact with the system. ○ Record behaviors, comments, and challenges for analysis. 3. Post-Session Analysis: ○ Categorize observations into usability problems and prioritize based on severity and frequency. 3. Usability Problem Lists​W7_1_Errormessages Thin… Steps: 1. Identify Issues: ○ Compile observations from think-aloud testing or heuristic evaluations. ○ Define each problem clearly, linking it to user struggles. 2. Categorize Problems: ○ Severity (minor, moderate, severe). ○ Frequency of occurrence among users. 3. Collaborative Review: ○ Teams discuss and refine the list, ensuring all significant issues are captured. Outcome:  A structured problem list to guide design improvements and prioritization. 4. Exam Preparation Focus Understand the purpose and structure of error messages: ○ Their types, key design principles, and examples of constructive messaging. Practice conducting think-aloud tests: ○ The process, common pitfalls, and how to extract actionable insights. Learn to create and use usability problem lists: ○ Prioritize based on severity and frequency to guide iterative improvements. Familiarize yourself with the concept of "unhappy paths": ○ How to identify and design for these scenarios. This comprehensive summary provides the foundational knowledge covered in Week 7, essential for exam preparation. Let me know if you need additional details or explanations! Comprehensive Summary for Week 8 (W8 Files) 1. Functional and Non-Functional Requirements​W8_1_Functional Require…​W8_1_Functional Require… Purpose: Establish clear requirements for software design and development, focusing on both functional and non-functional aspects. Key Concepts: 1. Functional Requirements: ○ Define what the system should do. ○ Include features, rules, and expected user interactions. ○ Examples: “It should be possible to borrow a book.” “A user may not borrow more than three books simultaneously.” 2. Non-Functional Requirements: ○ Define how the system should perform. ○ Focus on system attributes rather than functionality. ○ Examples: User Experience (UX): How intuitive and enjoyable the interface is.  Scalability: Ability to support 10,000 concurrent users within two years. Security: Adherence to robust cybersecurity measures. Performance: Speed and reliability under load. 2. Writing and Organizing Requirements​W8_1_Functional Require…​W6_1_Group Assignment 2… User Stories: Structured format: "As a , I want so that." Examples: 1. "As a colorblind city employee, I want to send application results in a visually clear format." 2. "As a citizen with impaired intellectual ability, I want a simple financial assistance application process." Use Cases: Detailed scenarios outlining steps and interactions to achieve user goals. Complement user stories for deeper functional insights. Requirement Lists: Attributes: ○ Incremental numbering for identification. ○ Priority levels (e.g., essential, useful, nice-to-have). ○ Additional notes for context and detailed descriptions. 3. Importance of Non-Functional Attributes​W8_1_Functional Require…​W6_1_Group Assignment 2… Attributes: ○ Reliability: Consistent operation 24/7. ○ Performance: Handling simultaneous requests effectively. ○ Supportability: Ease of maintenance and scalability. Measurable Goals: ○ Examples: "The system should achieve a usability score of 68+ on the SUS scale." "It should handle 10,000 concurrent logins per minute." Exam Preparation Focus: 1. Functional Requirements: ○ Learn to define specific user actions and rules. ○ Focus on crafting clear, testable statements. 2. Non-Functional Requirements: ○ Understand the significance of scalability, usability, and security. ○ Practice writing measurable objectives. 3. Organizing Requirements: ○ Familiarize yourself with user stories, use cases, and requirement lists. ○ Learn to prioritize and link requirements to user needs. This comprehensive summary captures Week 8's focus on defining and organizing requirements, both functional and non-functional. Let me know if you'd like further elaboration or examples! Comprehensive Summary for Week 9 (W9 Files) 1. Introduction to UML and Class Diagrams​W8_1_Functional Require…​W11_2_h2024_the Exam-3 Purpose: To introduce UML (Unified Modeling Language) and its application in system design. Focus on creating class diagrams to document and visualize system structure. Key Concepts: 1. What is UML?: ○ A graphical language for specifying, visualizing, and documenting system designs. ○ Includes use case diagrams, class diagrams, and sequence diagrams. 2. Class Diagrams: ○ Document the static structure of a system. ○ Key components: Classes: Represent entities with attributes and methods. Attributes: Define properties of the class (e.g., name, age). Methods: Define behaviors or functions (e.g., signUp(), logIn()). Relationships: Show associations between classes (e.g., inheritance, composition). Examples:  A User class with attributes (name, email) and methods (signUp(), logIn()). A hierarchical model: Content as a parent class for Movie and TV Show. 2. Class Relationships and Syntax​W8_1_Functional Require…​W4_2_h2024_Tasks and Ha… Class Relationships: 1. Inheritance: ○ Common attributes and methods are defined in a parent class and inherited by child classes. ○ Example: Content as the parent class for Movie and TV Show. 2. Association: ○ Represents relationships between two classes, such as User and Order. 3. Composition and Aggregation: ○ Composition: A class cannot exist without its parent (strong dependency). ○ Aggregation: A class can exist independently of its parent (weaker dependency). Syntax: Visibility: ○ + for public, - for private, # for protected. Attributes and Methods: ○ Format: :. ○ Example: -name: string. 3. Tools for UML Diagrams​W8_1_Functional Require…: Tools like LucidChart, Draw.io, and Figma simplify creating UML diagrams. Paper-based sketches are encouraged for early-stage designs. Exam Preparation Focus: 1. Understand UML Basics: ○ The purpose and key components of UML diagrams. 2. Practice Class Diagrams: ○ Include attributes, methods, and relationships between classes. 3. Recognize Relationships: ○ Differentiate between inheritance, association, composition, and aggregation.  4. Use Tools: ○ Familiarize yourself with digital tools to create neat, detailed UML diagrams. This summary highlights Week 9's focus on UML and class diagrams, preparing you to apply these concepts effectively in system design and exams. Let me know if you need further elaboration! omprehensive Summary for Week 10 (W10 Files) 1. Testing Types and Goalsce software testing methodologies to evaluate system functionality, performance, and usability. Key Goals: 1. Verification: ○ Ensure the system meets functional and non-functional requirements. ○ Example: Validate that a user can rent a book or that the system performs well under load. 2. Bug Identification: ○ Detect and address defects in the system's design or implementation. 3. Real-World Usability: ○ Assess the system’s performance under actual usage conditions, such as user interactions or high traffic. Important Note: The goal is not to prove the system is bug-free but to identify areas for improvement. 2. Functional Testing Definition: Fooes and whether it meets specified requirements. Types: 1. Unit Testing: ○ Tests individual components, such as methods or classes, before integration.  ○ Can be either: Black Box: Testing without knowledge of internal code. White Box: Testing with full knowledge of the internal workings. 2. Integration Testing: ○ Evaluates the interaction between integrated components or systems. 3. System Testing: ○ Examines the system as a whole to ensure all components work together. 4. Acceptance Testing: ○ Validates the system against user requirements to confirm it is ready for deployment. 3. Non-Functional Testing Definition: Focuses on system attributbility, and security. Types: 1. Performance Testing: ○ Measures how the system behaves under varying loads, including stress tests with thousands or millions of requests. 2. Security Testing: ○ Identifies vulnerabilities to ensure the system is secure against threats. 3. Usability Testing: ○ Evaluates the user experience, focusing on intuitive design and ease of use. 4. Alpha and Beta Testing: ○ Alpha Testing: Conducted internally with basic functionality. ○ Beta Testing: Performed by real users to uncover issues in a near-final product. 4. Black Box vs. White Box Testing Black Box Testing: Tests the system’s outputs based on inputs wdge of the internal structure. Can miss untested paths or edge cases. White Box Testing: Tests all paths within the system, using knowledge of the internal workings. Useful for ensuring full code coverage. 5. Study Focus for Exam: 1. Understand Testing Types: ○ Be able to differentiate between functional and non-functional testing. ○ Recognize key types (e.g., unit, integration, usability). 2. Testing Goals: ○ Focus on validation, defect identification, and performance evaluation. 3. Testing Methodologies: ○ Understand the difference between black box and white box testing. 4. Practical Application: ○ Apply testing principles to real-world scenarios (e.g., performance testing under load). This summary covers the key concepts and methodologies of software testing from Week 10. Let me know if you need additional details or specific examples! Comprehensive Summary for Week 11 (W11 Files) 1. UX Testing Techniques​W11_1_h2024_More on UX …​W11_1_h2024_More on UX … Purpose: Understand and apply different UX testing methodologies to evaluate and refine design effectiveness. Key Techniques: 1. Think-Aloud Testing: ○ Users verbalize their thoughts while interacting with the system. ○ Process: Observe how users complete tasks. Capture frustrations, confusion, or successes. Analyze user behavior for actionable insights. 2. Heuristic Evaluation: ○ Conducted by experts, using predefined heuristics to identify usability issues. ○ Process: Inspect the interface against usability principles.  Document problems and assign severity levels. Create a joint usability problem list for design iteration. ○ Common Heuristics (Jakob Nielsen’s Guidelines): Visibility of system status. Match between system and real-world conventions. User control and freedom. Error prevention. Aesthetic and minimalist design. 3. Formal UX Evaluation (e.g., Vinnustund System): ○ Example case: Users from diverse professional backgrounds tested a task-oriented system. Metrics: Pre- and post-experience measurements using Attrakdiff 2.0. Usability problem identification. 2. Problem Identification and Resolution​W11_1_h2024_More on UX …​W10_1_h2024_Testing Typ… Usability Problem Lists: Tools for structuring and prioritizing usability issues. Categories: ○ Minor: Low impact, quick fixes. ○ Moderate: Affects functionality but not critical. ○ Severe: Prevents users from completing key tasks. Resolutions: Address severe problems with high urgency. Incorporate user feedback to refine design iteratively. 3. Key Design Principles for Usability​W11_1_h2024_More on UX …​W11_1_h2024_More on UX … Core Principles: 1. Visibility: ○ Ensure controls are visible and actions are clear. 2. Feedback: ○ Provide users with timely and informative responses to their actions. 3. Constraints:  ○ Restrict user actions to avoid errors. 4. Consistency: ○ Maintain uniform design and functionality across the system. 5. Affordance: ○ Design elements should intuitively convey their purpose (e.g., a button looks clickable). 4. Exam Preparation Focus 1. UX Testing: ○ Understand think-aloud testing and heuristic evaluation methodologies. ○ Be able to identify and prioritize usability problems. 2. Design Principles: ○ Memorize and apply visibility, feedback, constraints, consistency, and affordance principles. 3. Problem Lists: ○ Learn how to structure and use problem lists to guide design improvements. 4. Case Studies: ○ Familiarize yourself with real-world examples like the Vinnustund system to understand testing applications. This comprehensive summary captures Week 11's focus on advanced UX testing techniques and usability design principles. Let me know if you need additional details or examples! Comprehensive Summary for Week 12 (L16 and L22) 1. User-Centered Design (L16)​W5_1_h2024_Website desi…​W6_1_Group Assignment 2… Purpose: Highlight the importance of involving users throughout the software design process. Emphasize iterative design and the integration of user feedback. Key Principles: 1. Early Focus on Users: ○ Understand users’ cognitive, behavioral, and attitudinal characteristics. ○ Directly involve users in tasks like interviews, workshops, and prototype evaluations. 2. Empirical Measurement: ○ Observe and analyze user performance and reactions during testing.  ○ Use metrics like effectiveness, efficiency, and satisfaction. 3. Iterative Design: ○ Continuously refine prototypes based on testing feedback. ○ Address usability problems promptly and reevaluate. Core Activities: Understanding Context of Use: ○ Analyze the physical, technical, and social environments in which the system operates. Specifying Requirements: ○ Identify user needs, goals, and tasks using user stories, scenarios, and use cases. Generating and Evaluating Designs: ○ Develop multiple design alternatives and evaluate them using A/B testing or expert reviews. Success Factors: Foster active user participation to build ownership and trust. Clearly define usability and user experience goals. 2. Software Processes and Maintenance (L22)​W8_1_Functional Require…​W7_1_Errormessages Thin… Purpose: Introduce software development processes and their role in maintaining software quality. Key Processes: 1. Waterfall Model: ○ Sequential stages: planning, analysis, design, implementation, testing. ○ Criticized for its rigidity and lack of iterative flexibility. 2. Agile Methods: ○ Iterative and incremental development emphasizing collaboration and adaptability. ○ Popular frameworks: Scrum: Uses sprints (time-boxed iterations) for incremental delivery. Includes roles like Scrum Master and Product Owner. Kanban: Visualizes workflow and limits work in progress to optimize delivery.  3. Rational Unified Process (RUP): ○ Phases: inception, elaboration, construction, and transition. ○ Focuses on iterative development and UML for modeling. Maintenance: Software maintenance includes debugging, updating features, and improving performance. Types: 1. Corrective: Fixing bugs. 2. Adaptive: Adjusting to changes in the environment. 3. Perfective: Enhancing performance and usability. 4. Preventive: Reducing the risk of future issues. Testing in Scrum Projects: Ensure usability and accessibility testing are integrated within sprints. Frequent user involvement reduces misunderstandings about requirements. 3. Exam Preparation Focus for Week 12: 1. User-Centered Design: ○ Understand the principles of early user involvement, empirical measurement, and iterative refinement. ○ Be able to describe techniques for context analysis, requirement specification, and design evaluation. 2. Software Processes: ○ Differentiate between Waterfall, Agile (Scrum, Kanban), and RUP. ○ Understand their strengths, weaknesses, and appropriate applications. 3. Maintenance: ○ Know the different types of software maintenance and their objectives. ○ Emphasize the role of testing in identifying and resolving issues. 4. Practical Knowledge: ○ Relate theoretical concepts to real-world scenarios, such as iterative prototyping or sprint-based development in Agile. This comprehensive summary covers the foundational aspects of Week 12 topics, focusing on user-centered design, software processes, and maintenance. Let me know if you’d like further elaboration or additional examples! Summary of L16_UserCentredDesign_h2019_white Purpose The document provides an overview of user-centered design (UCD), emphasizing the importance of involving users in the design process and integrating their feedback to create usable, effective systems. Key Principles of User-Centered Design (UCD) 1. Early Focus on Users and Tasks: ○ Understand users’ needs, behaviors, and goals. ○ Analyze cognitive, physical, and attitudinal characteristics. ○ Include users in interviews, workshops, and field studies to gather insights. 2. Empirical Measurement: ○ Observe and measure user performance and reactions to prototypes, simulations, or manuals. ○ Metrics: Effectiveness (success rate), efficiency (time/effort), and satisfaction (user perception). 3. Iterative Design: ○ Identify and fix usability issues early. ○ Test and refine prototypes through multiple iterations. 4. Expectation Management: ○ Set realistic goals and expectations for users to avoid disappointment. ○ Maintain open communication about product limitations and benefits. 5. Ownership: ○ Actively involve users as stakeholders in the design process. ○ User participation increases acceptance and success of the final product. Core Activities in UCD 1. Understanding Context of Use: ○ Analyze where and how the product will be used. ○ Consider environmental factors like physical space, cultural norms, and technical setups. 2. Specifying User Requirements: ○ Define who the users are, their needs, and goals. ○ Use user stories, scenarios, and use cases to clarify requirements. 3. Producing Design Solutions:  ○ Generate multiple design alternatives using brainstorming, cross-disciplinary collaboration, and user input. ○ Evaluate designs with prototypes and feedback sessions. 4. Evaluating the Design: ○ Test prototypes through usability evaluations (e.g., think-aloud testing, heuristic analysis). ○ Refine designs based on user feedback and measurable outcomes. Methods for UCD 1. Data Collection Techniques: ○ Interviews, field studies, and workshops to gather contextual user insights. 2. Prototyping: ○ Low-fidelity prototypes for early feedback. ○ High-fidelity prototypes for more refined testing. 3. Evaluation: ○ Informal evaluations, remote testing, and expert reviews. ○ Formal evaluations for structured feedback. Challenges and Considerations 1. Degrees of User Involvement: ○ Face-to-face engagement (e.g., focus groups). ○ Online feedback or crowdsourced design ideas. ○ User involvement post-release for iterative updates. 2. Who are the Users?: ○ Identifying the right stakeholders can be complex. ○ Not all users are aware of their needs; designers must explore problem spaces and suggest solutions. Real-World Applications of UCD Examples include systems designed for elderly users who may have limited computer literacy. Techniques such as simplifying workflows, adding clear feedback, and improving accessibility can enhance user adoption. Study Focus  1. Understand and apply UCD principles: early user involvement, empirical testing, iterative design. 2. Practice data collection methods and prototype evaluation techniques. 3. Develop skills to identify and prioritize user needs, creating effective design solutions. Summary of L22_Processes_Maintainance_h2019 Purpose The document discusses software development processes and their role in designing, building, and maintaining software systems. It highlights key methodologies like Waterfall, Agile, and Rational Unified Process (RUP), as well as the importance of maintenance and testing. Key Topics 1. Software Processes Definition: A structured sequence of stages in software development, including planning, analysis, design, implementation, testing, and maintenance. Key Processes: 1. Waterfall Model: ○ Sequential approach: Each stage (e.g., requirements, design) must be completed before moving to the next. ○ Benefits: Clear structure and deliverables. ○ Drawbacks: Lack of flexibility, difficult to adapt to changing requirements. 2. Agile Methods: ○ Key Principles: Iterative and incremental development. Collaboration with stakeholders. Emphasis on adaptability and user-centered design. ○ Popular Frameworks: Scrum: Time-boxed sprints (short development cycles). Defined roles: Product Owner, Scrum Master, Scrum Team. Uses a Product Backlog to prioritize tasks. Kanban:  Visualizes work in progress using boards. Focuses on flow efficiency and limiting work in progress. 3. Rational Unified Process (RUP): ○ Phases: Inception, Elaboration, Construction, Transition. ○ Combines iterative development with a structured approach. ○ Includes disciplines like business modeling, requirements, design, implementation, and testing. 2. Testing in Scrum Projects Key Insights: Testing is integrated into sprints to ensure functionality and usability. Usability and accessibility testing are critical for user-centered products. Challenges in testing include balancing time constraints and maintaining thoroughness. 3. Software Maintenance Definition: The process of modifying software after delivery to fix issues, adapt to changes, or improve performance. Types: 1. Corrective Maintenance: ○ Fixing bugs or defects discovered after deployment. 2. Adaptive Maintenance: ○ Adjusting the software to work with changes in the environment, such as new operating systems. 3. Perfective Maintenance: ○ Enhancing the software's functionality or performance based on user feedback or evolving requirements. 4. Preventive Maintenance: ○ Proactively addressing potential future issues to improve reliability. 4. Deliverables in Each Phase 1. Planning: ○ Project proposal document.  2. Analysis: ○ Requirements analysis report. 3. Design: ○ System design documents, UI design, and test specifications. 4. Implementation: ○ Source code and related documentation. 5. Testing: ○ Test results and bug reports. 5. Agile vs. Waterfall Aspect Waterfall Agile Process Sequential, rigid. Iterative, adaptable. User Minimal, mainly at the High, continuous feedback. Involvement beginning. Flexibility Low—changes are difficult. High—can accommodate evolving needs. Testing Conducted after Integrated throughout development. implementation. 6. Key Principles for Success 1. Use iterative approaches for flexibility and adaptability. 2. Integrate user feedback and usability testing at every stage. 3. Maintain clear documentation for all deliverables. Study Focus for Exam 1. Processes: ○ Understand the characteristics, benefits, and limitations of Waterfall, Agile, and RUP. 2. Testing: ○ Be able to explain the integration of testing into Agile sprints and its role in software quality. 3. Maintenance: ○ Recognize the four types of software maintenance and their purposes. 4. Practical Knowledge:  ○ Be familiar with deliverables for each phase of software development. This summary encapsulates the key points from the document, providing a clear and focused overview for study purposes. Let me know if you need additional details!