Title

Mapping of data concepts to the matching AIRM concepts

Identifier

SWIM-INFO-017

Requirement

The mapping of a data concept shall contain a trace from the data concept in the information definition to the AIRM concept that has an equivalent or wider meaning and a trace to the data type in the AIRM that has an equivalent or wider meaning.

Rationale

This includes a basic trace to establish the semantic correspondence between concepts. Without such a trace the mapping is pointless.

The requirement adds a second trace for data concepts, as the constraint on value space expressed by the data type is also important to the semantics.

Verification

Correctness

Examples/Notes

Example: An example is an information definition contains a data concept called “Target Startup Approval Time” that is a time.

• one trace to the AIRM concept called “StartUp”; and
• one trace to the AIRM data type called “DateTime”.

Note: In cases where the trace is to an AIRM concept that has a wider meaning, SWIM-INFO-018 also applies. An example of a trace to an AIRM concept with a wider meaning can be found in SWIM-INFO-018.

Note: It may be possible to combine these traces into one single statement depending on the tracing techniques adopted.

Note: This requirement implies that implementations using technology that provides no typing (for example, JSON) will need to specify the applicable value range constraints at design time relative to the AIRM data type to demonstrate semantic correspondence.

Note: SWIM-INFO-019 requires the use of the AIRM’s unique identifiers in traces.

Level of Implementation

Mandatory