Skip to main content
7 events
when toggle format what by license comment
Oct 15, 2018 at 17:17 history edited Christophe CC BY-SA 4.0
added 269 characters in body
Oct 14, 2018 at 21:23 comment added Arseni Mourzenko 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.
Oct 14, 2018 at 21:08 comment added Christophe @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.
Oct 14, 2018 at 18:43 comment added Arseni Mourzenko 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.
Oct 14, 2018 at 18:12 history edited Christophe CC BY-SA 4.0
added 335 characters in body
Oct 14, 2018 at 10:37 history edited Christophe CC BY-SA 4.0
added 57 characters in body
Oct 14, 2018 at 10:10 history answered Christophe CC BY-SA 4.0