Comments by "Edward Cullen" (@edwardcullen1739) on ""Non-Functional Requirements" Are STUPID" video.

  1. ​ @kbssanik  No clickbait for me. I already came to this conclusion: NFR is an unhelpful term. Cross-functional would be better, but I don't think there's any meaningful distinction. The system must do what it must do, trying to split "requirements" into categories is just a distraction.
    2
  2. Hi, I came to the same conclusion about a year ago, but have real problems expressing myself. NFRs are a hangover from the early days of Software Engineering, which was copied by academics from other fields of engineering. As we're maturing as a discipline, this kind of thing is becoming clearer. Everything that the system must do is a requirement. There are no distinctions beyond this. I split it into standards and requirements. Standards are the things that cut across and inform requirements, but don't necessarily directly translate into 1:1 into requirements. I'd love to talk to you about NATIVE.
    1
  3.  @jimmyhirr5773  Hey, can't expect me to give the game away 😉
    1