Definition:
Detailing
There are two main types of Benchmarks: Scalar and Binary.
Illustrations
none
Type
Specification-Type
Examples
Usability:
Headline: Order of magnitude better than future competitors.
Scale: Average time needed to learn to do Typical Tasks for Typical User. Perfect: 0 seconds.
Estimate [This Year, Our Old Product] 10 minutes. <- CTO
Trend [Best Competitors, During New Product Lifetime, Europe Market & USA Market] 5 minutes.
Tolerable [New Product, All Markets] 2 minutes.
Goal [New Product, Initial Release] 1 minute.
Goal [New Product, 1 Year After Initial Release] 30 seconds.
‘Trend’, ‘Perfect’ and ‘Estimate; are Benchmark specifications.
Notes
1. A Scalar Benchmark is a reference Level for a performance or Resource Attribute. It is usually used for comparison purposes in Requirement- Specification, design and
implementation.
2. A Scalar Benchmark is normally defined using the Benchmark Parameters {Past, Record, Trend}.
3. It is arguable that the Concepts Ideal, Perfect and Wish are also reference Benchmarks, rather than actually required states. The Wish is a Stakeholder need, but not a formal System Requirement. Perfect and Ideal are two classes of extreme states, not likely to be seriously affordable, feasible or prioritized into Constraints or targets.
If they are in any Case really ‘required’ we would need to state them as targets or Constraints (added Jan 23 08 tg)
4. Function and design Attributes are specified as Binary Benchmarks: Binary Attributes are either present or absent in a System.
Keyed-Icons
none
Drawn-Icons
none
Related-Concepts
Baseline *351
Past *106
Record *127
Trend *155
Estimate *058
Perfect *648
Ideal *328
Wish *244
Scale
Product-Value
Stakeholder-Value
Target
Status
Meter
Scalar-Benchmark
Binary-Benchmark
Scalar-Baseline
History-of-Concept
none
This Concept entered by Jon Bundy.