Non-functional requirements

Non-functional requirements

1. Look and feel

   • spirt of the product apperance
   • overall impression
   • a bank might want a conservative image, a game the opposite
   • "the product should use only two colours"

2. Usability and humanity reguirements

   • ease of use
   • Are users satisfied
   • poor usability = poor productivity, more errors/stress
   • how user feels treated by the sytem
   • "90% of the population should be able to pace an order in under 5 minutes"

3. Performance requirements

   • effectiveness of a system to carry out tasks
   • performance requirements involve speed, capacity, safety, accuracy, reliability and avalability
   • "a product shall calculate a quest bill in less than 2 seconds"

4. Operational and environmental requirements

   • Where the product has to work
   • requirements that relate to the installation of the product
   • "The product need to be installed at 56 locations around the rout by 3 semi-skilled workers"

5. Maintainabilty and support requirments

   • Expected changes and the time allowed to make them
   • is there going to be a help desk
   • "the product can modified to cope with changes in european law"

6. Cultural requirements

   • product sold in a different country
   • cultural differences within an organisation
   • seek the help of someone that is knowledgeable about that culture

7. Legal requiremnts

   • laws and standards

8. Security requirements

   • Access
   • privacy
   • Integaty
   • immunity