To test is to plan and execute an analytical Process on any System, Product or Process, where we attempt to understand if the System performs as expected, or not.

Alternative Names

Concept Number: *256
English Master: Test
Synonyms, Variations & Acronyms: none


A Test Parameter can be used to reference specific test plans and Processes.


Illustration: none


Process, Parameter


Requirement X:
Scale: ….
Meter [Module Level]: …, [Customer Acceptance]: Contract Section 6.0, [Operation]: …
TP XYZ: Test Plan [System XYZ]: Test Plan Document XYZ [May This Year].
Test [Goal]: TP XYZ [Section 1.2.3, Test Cases = {3.4, 6.7, 9.1.4}].
Test Parameter used to cross-reference test plans and test cases for Requirement X.

Test Tag: Test [Acceptance]: Two independent observers, [Operation]: Built-in software test.
A Test specification, which can be included with any Attribute Requirement, or it can be referred to via its tag (“Test Tag”). Notice that the qualifiers distinguish between two different stages of testing. The two suggested test methods are very roughly specified. This is useful at early stages of specification in order to get some Idea and agreement about test costs and Quality. This does not prevent a later stage of Engineering detailing this to any interesting Level of test plan.

Compare “Test” with the Parameter Meter, which is the specification of how to Measure numerically according to a defined Process in the Meter specification.


1. The overall Aim of testing is to determine if the Requirements are met.

2. Testing is a Means of understanding how something works without necessarily understanding exactly why it works that way. Testing is from outside the “Black-Box”. Only by examining actual construction, or specification can we analyze the inner workings of the System (the design and construction).

3. We typically test by putting planned or random inputs into a System, and comparing the resulting outputs (behavior and data) with our expectations. When the outputs deviate from expected behavior, we must analyze the reason to see if the System is failing to meet Requirements, or if the Requirements are wrongly specified. If it is economic to do so, we will probably correct either the System itself, or the specification, or both.

4. The term testing could be applied in a much wider sense to any form of examination (QC, SQC, QA), but it is specifically limited in Planguage to “input-output” testing of the System prior to operational use. “Test” is not intended to apply to Conceptual models of a System, but only to prototypes and real-world Systems.

5. The Test Parameter can also be used to specify or more likely cross-reference already-developed test cases and test plans for reuse or modification.





Meter *093: Test differs from “Meter” in that Test is very specifically concerned with System testing, while Meter is concerned with any form of Measurement (for example, SQC).



This Concept entered by Lisa.

Created by system. Last Modification: Thursday 11 of July, 2019 21:00:05 CEST by Admin (Kai).

Concept Search