From: Andrew Gabb (agabb@tpgi.com.au)
Date: Fri Oct 03 2003 - 01:53:27 EST
Geórgia Maria Carvalho de Sousa wrote:
> Some works in RE mentions that there are some non-functional
> requirements (NFRs) that have global scope in the system.
>
> Lately, I have been question myself if this occurs only when the
> NFRs are declared as abstract and subjective requirements (NFR
> softgoals) such as security, performance, response-time,etc.
Not at all. Apart from my normal non-use of 'NFR' (because it's essentially non-meaningful), I seriously warn about any such generalisations with requirements. (Part of my Impurity Principle.)
How about these: 'All documentation shall be in English' or 'All user interfaces shall conform with the CUA standard xxxxx, date yyyy'. Not soft or subjective at all, are they. (Of course I admit that with a slimy lawyer you can create doubt with these, but that also applies to *all* requirements, terms and conditions.)
With regard to NFRs, how about the following: 'The typical users of the system will have the following experience and training: xxx, yyy.' This implicit requirement is not really an NFR, because it specifically identifies the types of users who will use the system, and will affect the design (of functions) in an operational sense. As will requirements talking about users using gloved hands in 4G and arctic conditions.
Andrew
-- Andrew Gabb email: agabb@tpgi.com.au Adelaide, South Australia phone: +61 8 8342-1021, fax: +61 8 8269-3280 ----- ------------------------------------------------------------------------------- To send a message to this mailing list send it to re-online@it.uts.edu.au. To unsubscribe from this mailing list, email majordomo@it.uts.edu.au with the message `unsubscribe re-online' in the BODY of the mail.
This archive was generated by hypermail 2.1.6 : Wed Oct 15 2003 - 14:23:03 EST