Skip to main content
Software Engineering

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.

4
  • 4
    I think the distinction between "functional" and "non-functional" is misleading and tends to leave software with poor operability. I've found that thinking about "end-user features" and "operational features" leads to better software: blog.softwareoperability.com/2013/04/08/… (my post) Commented May 3, 2013 at 9:51
  • @MatthewSkelton I could not tell if (2.) is an en-user feature or an operation feature. Seems to be a "testing-feature". Commented Jul 23, 2013 at 6:41
  • @moose - the requirement for the DB to /operate within certain parameters/ given 100 items is more of an operational requirement, although this might impact the end-user experience if performance were degraded. Ultimately, we'd probably need a bit more context on the requirements in the OP to be able to split into F and NF, although - as I hinted - I think this is a bit of a spurious distinction anyhow :) Commented Jul 23, 2013 at 13:35
  • In retrospective: Top 10 answers to top 10 software requirements interview question Commented Sep 26, 2015 at 17:56