User Experience Assessment Quiz

True (A)

1. Background information on the user group. 2. Primary goals and motivations for using the system.

<p>closing</p> Signup and view all the answers

<p>Introduction = Goals, ethical considerations, consent Warm-up = Easy questions to build rapport Main Session = Logical and clear questions Closing = Summarize insights, thank participants</p> Signup and view all the answers

<p>Avoid jargon and compound sentences (C)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Nurture, relatedness, and joy</p> Signup and view all the answers

<p>Information (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>To improve system usability by identifying usability issues and collecting user feedback.</p> Signup and view all the answers

<p>clear</p> Signup and view all the answers

<p>To guide future design iterations (D)</p> Signup and view all the answers

<p>Minor = Minimal user disruption Moderate = Delays user tasks and causes frustration Severe = Prevents task completion entirely</p> Signup and view all the answers

<p>Developing realistic tasks (D)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Intermediate prototypes</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>Use clear, polite, and constructive language.</p> Signup and view all the answers

<p>tasks</p> Signup and view all the answers

<p>Clickable Elements = Simulate user interactions Error Messages = Guide users back to the happy path Colors and Fonts = Enhance visual design User Feedback = Refine tasks iteratively</p> Signup and view all the answers

<p>Overly technical (C)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>Simplicity and usability</p> Signup and view all the answers

<p>They define what the system should do. (B)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>To provide constructive feedback and guide users in resolving issues.</p> Signup and view all the answers

<p>borrow</p> Signup and view all the answers

<p>Colorblind city employee = As a colorblind city employee, I want to send application results in a visually clear format. Citizen with impaired intellectual ability = As a citizen with impaired intellectual ability, I want a simple financial assistance application process.</p> Signup and view all the answers

<p>Both severity and frequency of issues. (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Scenarios where users encounter issues or errors during their interaction with the system.</p> Signup and view all the answers

<p>To capture user frustrations and insights (C)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Visibility of system status</p> Signup and view all the answers

<p>severe</p> Signup and view all the answers

<p>Visibility = Ensure controls are obvious and actions clear Feedback = Provide timely responses to user actions Constraints = Limit user actions to minimize errors Consistency = Maintain uniformity across the system</p> Signup and view all the answers

<p>Neglect (A)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>Minor, Moderate, Severe</p> Signup and view all the answers

<p>Scrum Master (C), Product Owner (D)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Inception, Elaboration, Construction, Transition</p> Signup and view all the answers

<p>Perfective</p> Signup and view all the answers

<p>Corrective = Fixing bugs Adaptive = Adjusting to changes in the environment Perfective = Enhancing performance and usability Preventive = Reducing the risk of future issues</p> Signup and view all the answers

<p>Early focus on users and tasks (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>Debugging, updating features, and improving performance</p> Signup and view all the answers

Error messages that provide general updates or status about the system.

Error messages that alert users about potential risks, often with options like 'Yes,' 'No,' and 'Cancel.'

Error messages that notify users about issues requiring immediate attention.

A type of usability testing where participants think aloud their thoughts and actions while interacting with a system or product.

A process of identifying, categorizing, and prioritizing usability issues based on severity and frequency.

Usability problems that minimally disrupt the user's experience and may cause slight confusion.

Usability problems that delay user tasks and cause frustration, but don't completely prevent task completion.

Usability problems that entirely prevent users from completing tasks, leading to significant dissatisfaction.

A user story describes a user's desired outcome or goal, while a task provides a specific, testable scenario that aligns with a user story. Imagine a user story as a general direction and a task as a specific route.

Error messages should be clear, polite, and guide users back to the correct path. They should also provide visual cues to indicate severity.

Low-fidelity prototypes focus on structure and functionality, while intermediate prototypes add details like color, fonts, and interactive elements. Think of a simple sketch evolving into a detailed painting.

Usability testing involves observing how users interact with a prototype and gathering feedback on their experience. Researchers use this feedback to identify areas for improvement.

Principles of website structure, navigation aids, and responsive design guide how users navigate and interact with a website. This includes clear headings, intuitive menus, and adaptable layouts for different screen sizes.

The Five Acts of Prototype Testing are a framework for conducting and analyzing usability tests. Each act focuses on different aspects of the testing process, from planning to reporting results.

Responsive design ensures a website adapts its layout and content to different screen sizes and devices. This provides a consistent and comfortable user experience across desktops, tablets, and smartphones.

Task creation is a crucial aspect of usability testing. Tasks should be specific, realistic, and aligned with user goals to effectively evaluate the user experience. Imagine real-life scenarios users might encounter.

The process of gathering information directly from users through conversations to understand their needs, behaviors, and opinions.

Identifying the people who will use the system or product, and considering their characteristics, needs, and goals.

Questions designed to gather information about how users interact with a product or system. They can help to understand user motivations and problem-solving approaches.

A structured approach to conducting user interviews, ensuring a smooth flow of information and a comfortable experience for the participant. It involves introducing the interview, building rapport, asking key questions, and summarizing findings.

Analyzing user groups based on their demographics, motivations, and technology usage. This involves identifying their characteristics, goals, and how they interact with the system.

Creating detailed narratives about user behaviors and motivations, illustrating their needs and struggles with a system. They are based on user interview insights and help inform design decisions.

A technique for organizing and priorizing user needs based on their importance and impact on the system's design. It's a way to focus on the needs that matter most to users.

Analyzing data gathered from user interviews to identify patterns, common themes, and insights that inform design decisions. It's about finding the 'golden nuggets' of information.

A specific type of requirement that outlines what a system should do, including its features, rules, and user interactions. Examples: "A user should be able to borrow a book." or "A user can't borrow more than three books at once."

A specific type of requirement that focuses on how a system performs rather than what it does. Examples: "User Experience (UX) should be intuitive and enjoyable" or "The system should be able to handle 10,000 users at once."

A structured format describing a user's need through a specific action. It follows this structure: "As a [user role], I want [action], so that [reason]." Example: "As a citizen with impaired intellectual ability, I want a simple financial assistance application process."

Detailed scenarios outlining steps and interactions to achieve specific user goals, complementing user stories with deeper functional insights. Example: "A user can borrow a book by going to the library, picking it up, and scanning it at the checkout counter."

A formal test that involves thinking aloud as you perform a task, allowing researchers to gain insights into user behavior and identify potential issues.

A type of error message designed to help users understand and resolve problems easily. It is clear, concise, and offers helpful instructions.

Any potential scenario where a user might encounter negative or unexpected outcomes, requiring careful consideration and design to ensure a smooth and supportive experience. Examples: "No internet connection" or "Error while processing request."

A usability evaluation method where experts assess an interface against established usability principles, identifying potential problems and assigning severity levels.

A design principle that ensures controls are visible and actions are clear to users.

A design principle that provides timely and informative responses to user actions, giving them feedback on their progress.

A design principle that restricts user actions to avoid errors and guide them towards correct usage.

A design principle that ensures consistency in design and functionality across a system to enhance user familiarity and predictability.

A design principle where elements suggest their purpose and how they can be interacted with. For example, a button should look clickable.

A software development methodology that prioritizes user involvement throughout the design and development lifecycle.

Involves understanding users' needs, behaviors, and goals to create products that meet their requirements.

A flexible, iterative approach to software development that emphasizes continuous improvement and user feedback.

A framework for managing Agile projects, focusing on iterative sprints and collaborative development.

A visual system for managing work flow that limits work in progress to optimize delivery.

Emphasizes iterative development and utilizes the Unified Modeling Language (UML) for modeling.

The process of modifying software after its release to fix bugs, improve performance, or adapt to new environments.