User Experience (UX) requirement analysis is a critical component of acceptance testing and product development. According to ISTQB Acceptance Testing syllabus and industry-aligned UX design methodologies (e.g., ISO 9241-210 and BABOK guidelines), UX requirement analysis is typically structured around the following pillars:
User Analysis – Understanding who the users are (roles, goals, experience levels)
Task Analysis – Understanding what users do (tasks, workflows, pain points)
Context Analysis – Understanding where and how users interact with the product (environmental and contextual factors)
Competitor Analysis – Understanding how similar problems are solved in the market
Option B best describes Task Analysis, one of the most practical and impactful pillars. In task analysis, business analysts and UX researchers observe how users interact with current or comparable systems to understand workflow patterns, user frustrations, needs, and required system functionality. This method helps uncover implicit needs that users may not articulate in interviews.
This approach is aligned with ISTQB’s emphasis on understanding real-world usage and business processes as a foundation for deriving acceptance criteria and tests. It supports the creation of realistic scenarios that reflect actual user behavior, which is essential for verifying system fitness for use.
The other options are inaccurate:
A refers to psychological disposition, which is more aligned with user profiling or persona development, not a core focus of user analysis in requirement engineering.
C incorrectly ties context analysis with deriving security requirements, which is not its purpose.
D describes an unrealistic or incorrect method for competitor analysis.
Therefore, Option B is the best description of a key pillar of UX requirement analysis per industry and ISTQB standards.
