Which is a challenge in determining acceptance criteria for non-functional requirements?

Determining acceptance criteria for non-functional requirements can be particularly challenging due to the fact that these requirements are often not explicitly stated or are assumed to be understood by stakeholders. Non-functional requirements encompass attributes such as performance, reliability, usability, and security, which are more difficult to quantify than functional requirements.

Often, stakeholders may have a general idea of these attributes but may not articulate them clearly, leading to ambiguity. This lack of clear specification means that when it comes time to assess whether the requirements have been met, there may be confusion or misalignment between what was expected and what was delivered. This necessitates a careful approach to drawing out specific, measurable criteria to ensure that everyone involved has a common understanding of success.

Clarity in establishing acceptance criteria is essential for validating whether the system meets the desired qualities and performance thresholds, making this a significant challenge in the realm of software development.