I've been involved in a couple of projects now where we've held meetings specifically to discuss what the relevant Non-Functional Requirements (NFR) are for the project, and what these should be. 

If you take a minute to look at accuracy and precision you might think they were the same thing - but they aren't.  How do you descibe exactly what robustness and availability are to someone who isn't technical?

These thoughts and the impeding meetings got me thinking; so in the spirit of the Architectural Cheat Sheet comes the "Dictionary of Non-Functional Requirements":

Dictionary of Non-Functional Requirements.pdf 63.12 Kb

Thanks (as usual) to Wikipedia, however, I'm happy to say it's not straight copy and paste, and I'm quietly confident I've added some value.

I suggest you print it out as two sheets per page, double sided - that way you can fit it all neatly on to one single piece of paper.