Java Testing and Design - 2.4 The Web Rubric

As with many things, clearly stated objectives and criteria are useful in determining the health of your system.  A rubric has certain advantages:

1. assessment is more objective and consistent
2. helps the testers focus on clarifying criteria into specific terms
3. clearly describes to the developer how her work will be evaluated and what is expected
4. provides benchmarks against which the developers can measure progress

Here is an example ruberic:

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.
Correct operation	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:

1. focus on measuring stated objectives (performance, behavior or quality)
2. use a range to rate performance
3. contain specific performance characteristics arranged in levels indicating the degree to which a standard has been met.

A ruberic's job is to help remove subjectivity when assessing the health and quality of the application.