Apr
13
Non-Functional Requirements or Whatever They’re Called
April 13, 2006 |
Software developers typically break down requirements into two categories that they find useful: Functional Requirements, which describe how a system is supposed to behave, and Non-functional (AKA Supplementary or Quality of Service) Requirements, which describe the conditions and constraints under which a solution must function.
The rest of this post was going to be a digression about what non-functional requirements should be called and why, but never mind. If that definition I just wrote holds up against other ones I think I’ve finally found a formulation that will work, and is even useful for non-IT solutions.
Comments
1 Comment so far
What I'm Reading- Do You really Believe in What you Do?Requirements Defined - Seilevel's Software Requirements Blog
- C.R.A.C.K. Requirements managersBetter Projects
- ‘IT has no inherent value’IT Project Failures
- Business Analysis in an Uncertain EconomyJonathan Babcock
- Why We Lost Focus on Development PracticesAgile Management Blog
- Talking about what we doRequirements Defined - Seilevel's Software Requirements Blog
- BPM is not Software EngineeringGo Flow
- 3 Big CaliberRM Gotchas And How To Fix Them Part 1Requirements Defined - Seilevel's Software Requirements Blog
- Project World and World Congress of Business Analysts (PW&WCBA)Better Projects
- Troubled ProjectsHerding Cats
Would you characterize data retention under quality of service? Suppose you are an ISP and are required to keep track of all activity for years due to security (e.g., anti-terrorist) legislation.
Logging, extensibility and privacy requirements may also be a little harder to argue as falling underneath Quality of Service.