CPUX-F Practice Questions

The dialogue principles are a set of seven general ergonomic principles for the design of the user interface's interactive behavior, as defined in the international standard ISO 9241-110. The three principles listed among the correct options are:

- Suitability for the task: The dialogue supports users in completing their tasks effectively and efficiently.

- Conformity with user expectations: The dialogue is consistent and corresponds to predictable user conventions and context.

- Suitability for learning: The dialogue supports and guides the user in learning to use the system.

C. "Suitability for usability" is too general; usability is the outcome achieved by applying specific principles, not a principle itself.

E. "Suitability for engagement" relates to user experience goals like enjoyment and emotional connection, but it is not one of the seven formal dialogue principles.

F. Accessibility is a crucial design goal, ensuring use by people with disabilities, but it is not listed as one of the seven dialogue principles in ISO 9241-110.

1. UXQB® Certified Professional for Usability and User Experience – Foundation Level (CPUX-F) Curriculum, Version 3.11, 2023-07-01, Chapter 4.3.1 "Dialogue principles (ISO 9241-110)", pp. 64-65.

2. ISO 9241-110:2020, "Ergonomics of human-system interaction — Part 110: Interaction principles", Section 5 "Interaction principles".

Determining the context of use involves understanding the current users, their goals, tasks, and the physical and social environment in which they operate. Methods like interviews (B, C), observation (D), focus groups (F), and even competitive usability tests (E) are used to gather data about this existing context. Presenting an idea for a new machine (A) is a future-oriented activity focused on concept validation or gathering requirements for a new design, not on analyzing the current, existing context of use.

B. Interviewing bank clerks provides valuable insight into common user problems and the operational environment, which is part of the context of use.

C. Interviewing current users is a direct method for understanding their goals, tasks, and pain points related to the existing system.

D. Observing users is a primary method for understanding their actual behavior and the environment in which they use the cash machine.

E. Usability tests with competitors' machines can reveal user expectations and common interaction patterns, which are part of the broader context.

F. Focus groups can uncover shared needs, attitudes, and frustrations about current cash machines, contributing to understanding the context of use.

1. UXQB®. (2018). CPUX-F Curriculum - Usability, UX and User Centered Design. Version 3.1. pp. 39-42, Section 3.2 "Methods for analysing the context of use". This section lists observation, interviews, and focus groups as key methods. Presenting ideas is not listed as a method for analyzing the context.

Usability, as defined by the ISO 9241-11 standard and adopted by the CPUX-F curriculum, is the "extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use." These three components—effectiveness, efficiency, and satisfaction—are the core measures of usability. They quantify whether users can achieve their goals, the resources they expend in doing so, and their subjective feelings about the interaction.

B. Product, placement and price: These are elements of the marketing mix (4 Ps of marketing), not components of usability.

D. Interaction with social media: This is a potential feature of a system, not a fundamental measure of its usability.

E. Cultural neutrality: This is a desirable quality attribute for international products but is not one of the three core components of the ISO 9241-11 usability definition.

1. International Organization for Standardization. (2018). ISO 9241-11:2018 Ergonomics of human-system interaction — Part 11: Usability: Definitions and concepts. Section 3.1.1.

2. UXQB. (2018). CPUX-F – Curriculum – Foundation Level – Usability and User Experience. Version 3.2.1. Chapter 2.2, "Definition of usability", p. 15.

A usability finding is a factual observation about user interaction with a system, identified during a usability evaluation such as a usability test. Findings can be negative, identifying a usability problem where the user struggles or fails to complete a task efficiently or effectively. They can also be positive, highlighting aspects of the design that users found particularly easy to use, helpful, or satisfying. Both types of findings are crucial for improving the user experience.

B. A usability requirement: This is a goal or constraint for the design, established before evaluation, not a finding from an evaluation.

D. A usability priority: This is a severity rating or classification (e.g., critical, major) assigned to a usability problem after it has been identified.

E. Something that the users would like to add: This is a feature request or suggestion for new functionality, which is distinct from a finding about the usability of the existing system.

F. The evaluation of the liking of color patterns: This is a specific type of subjective feedback, but "usability finding" is a broader, more formal term for observed problems and positive aspects.

1. Dumas, J. S., & Redish, J. C. (1999). A Practical Guide to Usability Testing. Intellect Books. Chapter 13, "Analyzing and Reporting Data". (Seminal academic and professional text on usability testing).

2. UXQB. (2018). CPUX-F – Curriculum – Foundation Level – Usability and User Experience. Version 3.2.1. Chapter 5.3.3, "Consolidate usability findings", p. 53.

Storyboards are a key tool in human-centred design. They visually narrate a use scenario, often in a comic-strip format (C), showing the sequence of interactions between a user (persona) and a system (F). This visualization helps the design team and stakeholders understand the context of use and the user's journey. Because they effectively illustrate use scenarios, they serve as an excellent foundation for creating early, low-fidelity prototypes that test the proposed workflow (A).

B. This is false; a storyboard is a visual representation of a use scenario, so their purposes are very similar and complementary.

D. This is false; storyboards are very effective for illustrating both current ("as-is") and future ("to-be") user experiences.

E. A storyboard depicts the interaction of a persona within a scenario, not just the persona as a static illustration.

1. UXQB. (2023). CPUX-F Curriculum – Usability, UX and User Centered Design. Version 3.1. Section 3.3.3, "Storyboard," p. 50.

2. Truong, K. N., Hayes, G. R., & Abowd, G. D. (2006). Storyboarding: an empirical determination of best practices and effective guidelines. Proceedings of the 6th conference on Designing Interactive systems, 12-21. https://doi.org/10.1145/1142405.1142409 (This paper details the practice and purpose of storyboarding in design).

This list is taken directly from the CPUX-F curriculum and outlines the seven core responsibilities of a user experience professional. These responsibilities encompass the entire human-centred design lifecycle, from initial planning and understanding the context of use, through requirements definition, information architecture, interaction design, visual design, and finally, the iterative evaluation of the user interface.

This is a fill-in-the-blanks question based on a direct quote from the official curriculum. Therefore, there are no alternative options to evaluate; the provided words are the only correct answers.

International Usability and UX Qualification Board (UXQB), “CPUX-F - Curriculum - Foundation Level,” Version 3.10 EN, 2021. Section 1.2 "The user experience professional," p. 11. The text provides this exact list of responsibilities.

The main purpose of personas and as-is scenarios is to create a shared understanding of the users and their current context. Personas represent user archetypes ("who"), detailing their goals, motivations, and characteristics. As-is scenarios describe the current workflows and tasks these personas undertake ("what they do now"), including existing pain points and obstacles. Together, they provide a concrete foundation based on field research for identifying user needs and ensuring the design team remains focused on solving real-world user problems throughout the development process.

This is a fill-in-the-blank question with only one correct answer provided in the prompt's format. No other options were presented for evaluation.

1. International Usability and User Experience Qualification Board (UXQB), “CPUX-F Curriculum – Foundation Level,” Version 3.11, 2023. Section 3.2.3, "Personas and As-is Scenarios," p. 51.

2. International Usability and User Experience Qualification Board (UXQB), “CPUX-F Glossary,” Version 3.11, 2023. Definition of "As-is scenario," p. 7.

3. International Usability and User Experience Qualification Board (UXQB), “CPUX-F Glossary,” Version 3.11, 2023. Definition of "Persona," p. 28.

Prototypes are created to make design ideas tangible so they can be reviewed and tested before committing to expensive development. Therefore, their primary purpose is to serve as the basis for a usability evaluation. This allows designers and stakeholders to gather early feedback. A usability test, where representative users attempt to complete tasks with the prototype, is one of the most common and effective forms of usability evaluation.

This is a fill-in-the-blanks question; therefore, an analysis of incorrect options is not applicable. The provided terms are directly supported by the official curriculum.

1. International Usability and User Experience Qualification Board (UXQB), “CPUX-F Curriculum - Foundation Level,” Version 3.11, 2023. Section 5.2, Prototypes, p. 78. The curriculum explicitly states, "The primary purpose of a prototype is to serve as the basis for a usability evaluation, often a usability test."

In the context of human-centered design and usability, a 'goal' is the intended outcome or the high-level objective a user wants to achieve. A 'task' represents the specific set of activities and interactions a user performs with a system to reach that goal. For example, a user's goal might be to "communicate with a friend," and the task would be "sending an email." This distinction is crucial for task analysis, where understanding user goals is the first step before breaking down the required tasks.

This is a fill-in-the-blank question with one correct answer. Other words like 'objective' or 'purpose' are synonyms but 'goal' is the specific term used in this standard definition.

1. UXQB. (2023). CPUX-F Curriculum – Foundation Level. International Usability and User Experience Qualification Board e.V. Glossary, page 98, defines a goal as an "Intended outcome" and a task as "The activities required to achieve a goal."

2. International Organization for Standardization. (2018). ISO 9241-11:2018 Ergonomics of human-system interaction — Part 11: Usability: Definitions and concepts. Section 3.1.4 defines a goal as an "intended outcome."

An "As-is scenario" is a narrative that describes how a specific user, often represented by a persona, currently performs a task or achieves a goal. It details the existing workflow, tools used, and any challenges or pain points encountered before the introduction of a new or redesigned system. This tool is fundamental in the "Understand and specify the context of use" activity to establish a baseline of the current user experience, which helps in identifying opportunities for improvement and defining user requirements for the new system.

No alternatives were provided in the item.

1. UXQB® Certified Professional for Usability and User Experience – Foundation Level (CPUX-F) Curriculum, Version 3.1 (May 2023), Glossary, p. 100. "As-is scenario: Narrative description of the activities that a persona carries out in order to reach a goal, including the problems that the persona encounters. An as-is scenario describes the current situation before the use of the interactive system to be developed."

2. Interaction Design: Beyond Human-Computer Interaction, 5th Edition, by Rogers, Y., Sharp, H., & Preece, J. (2019), Chapter 10. This university-level textbook describes scenarios as informal narratives about user tasks and activities, distinguishing between current ("as-is") and future states.