A Generic term is a Term in a Specification that needs further definition, there or elsewhere.

Alternative Names

Concept Number: *377
English Master: Generic Term
Synonyms, Variations & Acronyms: Scale-Qualifiers Generic-Standard








For example (1), Scale-Qualifiers (*381) are one example of Generic terms: this could be a Generic-Standard (*150) – a template for a “User Reaction” definition.

User Reaction:
Scale: Probability that defined [People] will report defined [Faults]
within defined [Time Limits].

Then somewhere, just here locally, or in a more global Project Glossary, we define the Generic Terms

For example (2): ( and these could also be either Generic-Standards, or specific to the project. “….” Indicates a “list of more detail”, which we choose not to show here.

People: Defined: The Class of customer, {Customers (Default), Trial
Users, …}.
Faults: Defined: The Class of Faults, {Show Stoppers, Help Problems, … }.
Time Limits: Defined: Time from Fault occurred until report received and
logged by us. {n Hours, N Days, Same Day}.

• In the example (1) “defined [People]” and two other similar qualifiers in the Scale Specification, are Generic Terms. That Means, they need further definition.

• They are defined in example (2), and a set of known values for each is listed in the {Set Parenthesis}. Even this definition (2) is a Generic Term, because it needs further definition to pick the exact Class or time.

• One People Class (2), (“Customers (Default)” ) is identified as the “Default Value” (*447).

The use of these terms is illustrated by the example (3): using Scale Variables (*446)

User Reaction:
Scale: Probability that defined [People, Default: Customers] will report
defined [Faults] within defined [Time Limits].

Tolerable [Customers, Show Stoppers, 24-Hours] 90%
Goal [ People = Trial Users, Faults = Help, Time Limits = 1 hour] 99%
Wish [ Faults = Show Stoppers, Same Day] 95%


Note [Illustration 3].

• We have illustrated defining the Specific Terms by simply using Defined-Term Classes (“{Show Stoppers, Help Problems}”), and even doing so (3, Fail) in the same sequence (“People (Faults (Time Limits”)) in which the Generic Terms were specified, in the Scale specification (1 above).

• We also illustrated (3, Wish & Goal) the use of Explicit Parameters (example “Faults =“) for defining Specific Terms (example “Help”).

Type: Product-Value-Requirement.
Scale: Mean Time Between Failure from defined [Event Beginning] to
defined [Event Ending] for defined [System] under defined

Meter: defined [Test Circumstances {Development, Acceptance Test, Operation}] <specify or refer to test Procedure or protocol or

Goal [<when, where, which circumstances>] <a Level such as
30,000 hours> ( <Source.>

Authority: <which Levels of management, or customer contract,
determine the Level?>

This is a simple example of a Generic template for a Product-Value-Requirement. The terms in <fuzzy> are template “hints”. Instructions as to what to fill out. The intent is that they be removed from an electronic template when used. Both the Scale-Qualifiers (like “Event Beginning”) and the hints (like <when>) are Generic Term examples.








This Concept entered by Diane O'Brien.

Created by system. Last Modification: Thursday 11 of July, 2019 18:32:04 CEST by Admin (Kai).

Concept Search