CTFL-UT Exam Dumps : ISTQB Certified Tester-Foundation Level - Usability Testing

Formative usability evaluation is conducted during the development process to identify usability problems and improve the product iteratively. It is diagnostic and improvement-focused. Summative evaluation, on the other hand, is done after development to assess the final product’s usability, measuring how well it meets defined usability goals. Therefore, the correct distinction is that formative evaluation focuses on improvement, and summative evaluation assesses the outcome. This distinction aligns with widely accepted models such as those defined by ISO 9241-210 and usability.gov.

A pilot usability test session is a critical step prior to conducting the actual usability test. Its purpose is to ensure that the test setup, task design, and moderator instructions are clear and function as expected. According to ISO 9241-210 and the Nielsen Norman Group's best practices, pilot testing helps detect unforeseen issues and fine-tune the process. Options A and B are incorrect because testing conditions must reflect realistic scenarios, and thorough preparation is essential to gather meaningful usability data. Option D is also incorrect; a usability test typically consists of multiple sessions with different users to gather sufficient data for analysis. The pilot session ensures everything works smoothly before involving real participants.

A usability evaluation is specifically designed to assess how real users interact with a software product. It focuses on effectiveness, efficiency, and user satisfaction in completing tasks. This may involve usability testing, expert reviews, or heuristic evaluations. The goal is to identify any usability problems and understand user behavior during real use.

Option A (Accessibility evaluation) targets inclusivity for users with disabilities, not general user interaction. Option B (Usability maturity assessment) evaluates the organization’s usability practices, and Option C (Risk assessment) evaluates potential project or system risks. Only option D directly involves observing and measuring user interaction.