- assessment is more objective and consistent
- helps the testers focus on clarifying criteria into specific terms
- clearly describes to the developer how her work will be evaluated and what is expected
- provides benchmarks against which the developers can measure progress
|Criteria assessed through system use
|Level 1 Beginning
|Level 2 Developing
|Level 3 Standard
|Level 4 Above Standard
|Basic features are functioning
|Few features work correctly the first time used
|Many features do not operate. Some missing features required to complete work
|Most features operate. Workarounds available to complete work.
|All features work correctly every time they are used.
|Speed of operations
|Many features never completed.
|Most features completed before user lost interest.
|Most features completed in 3 seconds or less.
|All features completed in 3 seconds or less.
|Few features result successfully without an error condition.
|Some features end with an error condition.
|Most features complete successfully.
|All features complete successfully.
Ruberics can take many forms but typically offer the following:
- focus on measuring stated objectives (performance, behavior or quality)
- use a range to rate performance
- contain specific performance characteristics arranged in levels indicating the degree to which a standard has been met.