What is a key characteristic of a well-written requirement?

A well-written requirement should clearly describe a function that the system must perform. This characteristic ensures that the requirement is actionable and provides a clear expectation of what needs to be delivered within the system. Functional requirements focus on what the system should do, detailing the specific behavior or function of the system, which allows developers and stakeholders to understand the necessary capabilities.

While outlining benefits, defining user roles, and specifying a technology stack are important aspects of system design and implementation, they do not directly relate to the functionality of the system itself. Benefits of implementation focus on outcomes and impacts rather than system requirements. User roles provide context about who interacts with the system but do not define what the system does. The technology stack discusses architecture or tools needed but is not a functional requirement of the system. Thus, the clarity and focus on functionality make the description of a function the most critical aspect of a well-written requirement.