Library / Semantic Integration Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 15:41:27 UTC · snapshot created 2026-10-03 15:43:46 UTC · last check 2026-10-03 15:55:10 UTC

SIE.3:5.2 - Extend an Inspection Model

A constructed product-definition and inspection integration asks: “What observation concerns requirement Q for feature F in configuration R?” The source model already describes the feature and its requirement, but represents no actual observation.

Model contentDevelopment and case
Existing feature and requirementReuse their qualified definitions and configuration applicability.
ObservationAdd the actual observation as distinct from its plan and the requirement being checked.
Observation relationState which configured feature and applicable requirement it concerns.
Unit and timeExpress the interpretation required for this observation and question.
CounterexamplesA planned inspection is not an observation; an observation of another configuration does not answer this question.

The domain participants confirm those distinctions and identify any unresolved source-specific interpretation. The module can then supply SIE.4 and SIE.7 with the required meanings. In an AP242/QIF installation, its actual profiles, configuration relations, and inspection meanings must come from the qualified source results; the constructed model above is the working example, not a claim about a particular exchange’s conformance.