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 are consistent.

The checklist for architecture definition

• Ability for an interface to minimise the need for manual keying. For example, information is already contained in system tables which would result in relevant drop-down lists rather than having to type the information in.
• Ability to enable the use of the computer's operational locale (for example, local, regional and resolution settings) in the browser
• Ability to support the multiple browsers: Internet Explorer, Mozilla Firefox, Netscape, Safari.
• Ability to support the different screen resolutions for PC's: (1024x768, 800x600, 1280x1024, 1280x800, 1152x864)
• Ability to support the different delivery channels: PC, Mobile phones, PDA