Marcus is building a great reference on non-functional requirements at From Start to End. He’s created a series of articles, and keeps adding more. Each post focuses on a single type of non-functional requirement. He just put up an index page for all of his posts, and he’ll be keeping that page updated as he adds more content.
He’s been writing good stuff for quite a while, and you should definitely check it out. The index page is on my del.icio.us – because I’ll use it repeatedly. It should be on yours too.
As of May 5, 2006, he has posts for the following non-functional requirements:
- Availabilty (and a followup on Extreme Availability and Reliability)
- Data Currency
- Data Retention
- Disaster Recovery
- Error Handling
What is a Non-Functional Requirement?
In our introduction to structured requirements, we present Karl Wiegers’ diagram, and then distill the concept to a simplified view that we used in a lecture at St. Edwards University last year.
Functional requirements define what a system will do. Non-functional requirements describe how the system will do it. Non-functional requirements characterize the behavior that is required in functional requirements.
Bookmark or tag Marcus’ index. You’ll be glad you did.