 |
|
|
Archive - See List...
Links & More
 |
Print version |
Related Links |
|
 |
Automated Usability Checks (newer version) |
Background Links |
|
 |
SAP R/3 Style Guide |
Automated Checking
By Ulrich Kreichgauer, SAP AG, Usability Engineering Center
This paper is outdated.
Abstract
If you use the SAP Development Workbench, the Usability Monitor enables you to find deviations from the SAP interface standard automatically and correct them.
Checks
In the Screen Painter Tool you will find the following usability checks:
Priority 1
- X field not converted into checkbox or radio button
- Incorrect font for column heading
- Single radio button
- Scrollable field, although there is enough space to display it all
- Rollable numeric or date fields
Priority 2
- The attribute 'bright' is used too often
- Pseudo-frame instead of correct frame
Priority 3
- Screen elements do not begin in column 1
- Label of checkbox/radio button is not to the right of the element
- First info not in line 1 or 3
- Box is empty
- Elements in the frame do not begin at the left edge
- Loop heading does not have the 'bright' attribute
- First information message in a box is too deep
- Field label has a fixed font instead of a proportional font
- Check box or radio button has no label
- Text on a push-button was not replaced by an icon
- Distance between boxes is too great
- Whole screen will be displayed in non-proportional font
Priority 4
- Frames are not aligned
- Frame encloses ALL fields of the template
For GUI definitions you will find the following usability checks:
Priority 1
- Standard function not assigned to a function key
- Function text "Cancel" does not exist
Priority 2
- Edit and/or GoTo menu does not exist or position is incorrect
- Sequence of functions in pull-down menu is wrong
- Last entry in pull-down menu is wrong
- Default text not substituted
- Standard function assigned to the wrong function key
- Function is assigned to a key that is reserved for system functions
- Function is assigned to a key that is not allowed according to F-key type
- Function text does not conform to standard for standard F-key
Priority 3
- Function or pull-down menu appears more than once in menu bar
- Prohibited function appears in pull-down menu
- "Enter" is not the first push-button in dialog box
- Prohibited texts used
- Icon is not permitted or does not exist
- Missing separator in pull-down menu with more than 7 entries
Priority 4
- Push-button now displayed in standard toolbar
Corrections
In most cases the errors can be automatically corrected in the Menu Painter Tool. In Screen Painter the errors have to be corrected manually.
