Definition:
Concept Number: *398
English Master: Specification-Type
Synonyms, Variations & Acronyms: none
Detailing
For example: Type: Product-Value-Requirement.
Illustrations
Illustration: none
Type
none
Examples
Usage 1. It can be declared explicitly (Type: ), After the tag. It can be implicit (Tag: <Type>: <the spec>. ). See the example below for instances.
Usage 2. A spec Type can be declared at a higher Level of specification. For example:
Sub-Component X: Type: Requirements:
Reliability: Product-Value-Requirement: Headline…, Scale…, etc.
Navigation: Function-Requirement: the astronauts must be able to navigate manually.
Eavesdropping: Design-Constraint: eavesdropping must be enabled if local law dictates it.
Budget: Cost Requirement: Scale: Engineering Hours, Goal [To Release 1] 10,000.
Sub-Component Y: Type: Design. “Supra-Level: all below must be some Class of design”
D1: Component: ……..
D2: Process: …….
D3: Architecture: ………
Usage 3. A “Spec Type” can be given with any Planguage glossary-Defined-Term, and in addition with any term defined by you locally.
Notes
none
Keyed-Icons
none
Drawn-Icons
none
Related-Concepts
none
History-of-Concept
none
This Concept entered by Neil White.