A Stone Bell

Deep and Sonorous, or maybe just a Dull Thud?


Quality Requirements

I hate the term “Non-functional requirements” – I still believe that if it’s non-functional it doesn’t work.

I understand that the term is used to gather up the performance, capacity and other aspects of a system, but it’s such a negative phrase.

Also it tends to allow unquantifiable assertions such as “it has to be fast” rather than measurable statements like “the response time must be between 1 and 1.5 seconds”.

Therefore we use “Quality Requirements” instead, which also draws the Quality Assurance plan directly into being an integral part of the project testing rather than being some add-on afterthought.

- No Comments on this Post -

Leave a Reply

Your email address will not be published.

eleven + 16 =