Few GUI standards
- User ID and Password should be captured
- Password field should be masked
- Errors on invalid credentials should be descriptive
- Field Captions should be same across all the modules
- There should be a copyright statement in the GUI
- It shall contain
- Project started year
- Current year
- e.g.
- Old , New and Confirm New should be captured
- All password fields should be masked
- Auto completion feature can be set on for frequently used fields
- It SHOULD NOT be used for fields with sensitive data. e.g Password, PIN , Credit Card Number
- Text appear in GUI pages should be checked for spelling and Grammar
- MS Word can be used for simple checking
- There should be a link to logout from current session
- Session should expire
- Error messages should be descriptive
- Should be consistent
- Should be short
- It would be nice if they are configurable
- User should be acknowledge on events/changing status (e.g. On Update, Deleted , Add etc)
- Message should be consistent
- Message should be shorter
- Look and feel should be same in all supported browsers
- Look and feel should be same across all the modules
- Title should be appropriate to the current screen
- Should be short
- Appropriate controls should be used in the HTML pages
- Length of fields should be sufficient for users to enter longest possible value.
- Radio buttons are used when there is a list of two or more options that are mutually exclusive and the user must select exactly one choice. (e.g. primary notification method SMS, Email, Voice Mail)
- Checkboxes are used when there are lists of options and the user may select any number of choices, including zero, one, or several. (e.g. Assign permissions)
- A stand-alone checkbox is used for a single option that the user can turn on or off. (e.g Enable /Disable a user)
- Paging should be introduced if user has to scroll down to see the list of records.
- The value(s) selected should be a frequently used by user
No comments:
Post a Comment