Mastering Non-Functional Requirements

Checklist

The checklist for the capture of requirements is as follows:

• The overall purpose of the system and the functions is easy to understand for the end users
• Actions are reversible and, where that is not possible, confirmation is clearly sought.
• The system provides an attractive colour scheme and layout. The system is aesthetically pleasing.
• User manuals and guides are complete and up-to-date.
• Context sensitive guidance and help is available for end users.
• The error messages are useful and indicate how to resolve the issue.
• The application provides error messages for validation, verification or runtime problems.
• The system is relatively easy to learn/remember and intuitive for its users.
• The layout, actions, and interface components ...