Overview about the relationships between interface related concepts used in the SAF Functional/Logical Domain and the SAF Physical Domain

ConceptDocumentation
Conceptual Context ElementRepresents an abstract element in the given System Context on Conceptual Level, outside the SOI scope, interacting with the SOI.
Conceptual External SystemA Conceptual External System in the Conceptual Domain, outside the SOI scope, interacting with the SOI. E.g., power grid, mobile network, fresh water system (in a house).
Physical EnvironmentThe Physical Environment in the Physical Domain, outside the SOI scope, interacting with the SOI. E.g. air, dirt, sun, road.
Logical Context SOI_ DeprecatedRepresents the Logical SOI in the System Context on Logical Level.
Physical SOIRepresents the Physical SOI on Physical Level.
Physical Context ElementAbstract element of a System Context on Physical Level, outside the SOI scope, interacting with the SOI.
Physical External SystemThe Physical External System in the Physical Domain, outside the SOI scope, interacting with the SOI. E.g. power grid, mobile network, fresh water system (in a house).
Conceptual Exchange TypeSpecification for any type of conceptual item (energy, material, information, etc.) to be exchanged on Conceptual (Functional Architecture and Logical Architecture) Level. The Conceptual Exchange Type is agnostic to any realization on Physical Level.
allowingSpecifies the fact that a Conceptual Item Exchange is allowed on the Conceptual Connection.
typingSpecifies the fact that a Conceptual Exchange Type defines the type of a Logical Item Exchange.
typingSpecifies the fact that a Conceptual Exchange Type defines the type of a Conceptual Interaction Point Property.
realizingSpecifies the fact that a Conceptual Exchange Type is realized by Physical Exchange Types.
Physical Interaction Point PropertySpecifies a detail of an interaction point on Physical Level.
applyingToSpecifies the fact that a Conceptual Interaction Point applies to a Conceptual System.
Software ElementPure Software Elements. Similarity with the V-Model "software unit".
definingSpecifies the fact that a Conceptual Interaction Point Definition defines the exchange capabilities of a Conceptual Interaction Point.
PIPPspecifyingDetailOfPIPDSpecifies the fact that a Physical Interaction Point Property is a detail of a Physical Interaction Point Definition.
PIPDdefiningDetailOfPIPSpecifies the fact that a Physical Interaction Point Definition defines the exchange capabilities of a Physical Interaction Point.
Physical Exchange TypeSpecification for any kind of physical item (energy, material, information, etc.) to be exchanged on Physical Level. This is the realization of the specification made by System Domain Kinds.
typingSpecifies the fact that a Physical Exchange Kind defines the type of a Physical Item Exchange.
Conceptual Interaction PointSpecifies the existence of an interaction point on Conceptual Level.
typingSpecifies the fact that a Physical Exchange Kind defines the type of a Physical Interaction Point Property.
Physical ConnectionSpecifies the connection of two physical interaction points. Note: Connections between physical components indicate that item flows are passed from one output of a source component to one or more inputs of target components.
Conceptual Item ExchangeSpecifies the exchange that is to take place on a connection of two interaction points on Conceptual Level.
PIPapplyingToPCESpecifies the fact that a Physical Interaction Point applies to a Physical Context Element.
PCNallowingPIESpecifies the fact that a Physical Item Exchange is allowed on the Physical Connection.
specifyingDetailOfSpecifies the fact that a Conceptual Interaction Point Property is a detail of a Conceptual Interaction Point Definition.
Physical ElementA composition of Hardware and Software Elements. Similarity with the V-Model segments and system. See [VXT].
PIPapplyingToAPESpecifies the fact that a Physical Interaction Point applies to an Abstract Physical Element.
Physical Interaction PointSpecifies the existence of an interaction point on Physical Level.
Hardware ElementPure Hardware Elements. Similarity with the V-Model "hardware unit".
Conceptual SystemDescribes a conceptual system as specification for an implementation of a system. It is used in both functional and logical architectures on any hierarchy level.
applyingToSpecifies the fact that a Conceptual Interaction Point applies to a Conceptual Context Element.
Conceptual Interaction Point DefinitionSpecifies the exchange capabilities of an interaction point on Conceptual Level.
Physical Item ExchangeSpecifies the exchange that is to take place on a Physical Connection.
Abstract Physical ElementAbstract element representing physical structure items keeping properties and relations applicable to all physical items.
Physical Interaction Point DefinitionSpecifies the exchange capabilities of an interaction point on Physical Level.
Conceptual Interaction Point PropertySpecifies a detail of an interaction point on Logical Level.
Conceptual ConnectionSpecifies the connection of two interaction points on Logical Level. Note: Connections between logical components indicate that item flows are passed from one output of a source component to one or more inputs of target components.
Conceptual EnvironmentA Conceptual Environment in the Conceptual Domain, outside the SOI scope, interacting with the SOI. E.g., air, dirt, sun, road.
Conceptual UserThe Conceptual User is the representation for a human in the Conceptual Domain, outside the SOI scope, interacting with the SOI.
Physical UserThe Physical User is the representation for a human in the physical domain, outside the SOI scope, interacting with the SOI.
Physical Connector CompatibilitySpecifies the fact that two Physical Interaction Point Definitions are compatible and how the Physical Interaction Point Properties are mapped.
PCCapplyingToPCNSpecifies the fact that a Physical Connector Compatibility Assertion shall apply to a Physical Connection.
PCCassertsCompatibiltyForPCPDSpecifies the Physical Interaction Point Definition the Physical Compatibility Assertion is valid for.
Physical LayerSpecifies a Physical Layer, usually used for communication.
Physical Layer StackSpecifies a detail of an interaction point on Physical Level.
Physical Layer OrderingSpecifies an order among two physical layers. This order is valid within a Physical Layer Stack
PLOisValidInPLSSpecifies the fact that a Physical Layer Ordering is valid within a particular Physical Layer Stack.
PEKisAssignedToPLSpecifies the fact that a Physical Exchange Kind is assigned to a particular Physical Layer.
LIEboundedByPLSpecifies the fact that a Logical Item Exchange is constrained to be implemented on a particular Physical Layer.
LIEboundedByPLSSpecifies the fact that a Logical Item Exchange is constrained to be implemented on a particular Physical Layer Stack.
LCPboundedByPLSSpecifies the fact that a Logical Interaction Point is constrained to be implemented on a particular Physical Layer Stack.
PCPOverPCPSpecifies the fact that a physical interaction point communicates / transfers / flows / over an other physical interaction point. Used to define layered physical interfaces, and show layer relationships between interfaces.