Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Without any doubt, this is not a non-functional requirement, because it is not a requirement in the first place. See softwareengineering.stackexchange.com/a/118446/6605 and softwareengineering.stackexchange.com/a/380009/6605. But don't worry, many persons do the mistake of thinking that non-functional requirement is everything which is not a functional requirement, forgetting the mandatory criteria for a requirement in general. Commented Oct 14, 2018 at 18:43
  • @ArseniMourzenko the fact that a requirement is not well expressed, too subjective, or not sufficiently precise is IMHO not sufficient to deny it the status of requirement. If the same requirement would be refined and expressed as: "the gui shall comply with Apple's human interface guideline and the WCAG 2.0 guidelines for accessibility" it would be less controversial but still a non-functionzl requirement. Commented Oct 14, 2018 at 21:08
  • Not exactly. In my answer below/above, I explain why. The essence, the goal of a requirement is to be objective. A requirement which is subjective loses its purpose. Commented Oct 14, 2018 at 21:23