Concept	Documentation
Conceptual Context Element	Represents an abstract element in the given System Context on Conceptual Level, outside the SOI scope, interacting with the SOI.
Conceptual System Context	Specifies the fact that a System Context for a System of Interest is defined on Conceptual Level.
Logical Context SOI_ Deprecated	Represents the Logical SOI in the System Context on Logical Level.
allocatedTo	Specifies the fact that a System Function is assigned to a Conceptual System. Note: This fact may be derived from the Usage of a System Function in a System Process allocated to a System Conceptual SOI Role.
System Function	Specifies the fundamental action or task that have to take place in the System in accepting and processing the inputs and in processing and generating the outputs. A System Function * accepts input from the System boundary * exposes its output at the System boundary * changes the System's State * is dependent on System's State Note: A System Function does not need to expose observable output, when it changes the System's state in a way that is observable by other system functions. Furthermore, a System Function does not need to accept any input from the system boundary, when it is dependent on the System State, which in turn is changeable by other System Functions.
SFNallocatedToAPE	Specifies the fact that a relationship is derived from the assignment of Functions to Logical Elements and the assignment of Logical Elements to Physical Elements.
USAGEallocatedTo	Specifies the fact that a Usage of Function is allocated to a Usage of System Element.
General Functional Usage	Specifies a General Usage of a General Function within one or more other General Functions.
Conceptual System	Describes a conceptual system as specification for an implementation of a system. It is used in both functional and logical architectures on any hierarchy level.
Abstract Physical Element	Abstract element representing physical structure items keeping properties and relations applicable to all physical items.
Conceptual Internal Role	Specifies the fact that a Conceptual System may consist of Conceptual Systems (a white box perspective on a conceptual system).
Conceptual Context Element Role	Specifies the fact that a Conceptual Context Element acts in a given Conceptual System Context.
Conceptual SOI Role	Specifies the fact that a Conceptual System acts as SOI exists in a given Conceptual System Context.
System Partial Function	Specifies the fact that a System Partial Function is a decomposed part of a System Function and defines details of the System Function it belongs to.
Context Function	Specifies the fact that a fundamental action or task is expected to be carried out by an External Entity. Note: The intention is to capture the expectations and to explicitly dissect the functionality. This must not be interpreted as an attempt for a behavior specification of an External Entity. Capturing this valuable information is the basis to reach agreement on the functionality at the System boundary by clarifying the expectations about what is performed by Context Elements.
General Function	Specifies a General Function. It is used as base Class for specific System or Context Functions, or Partial Functions.
CFNallocatedToLCE	Specifies the fact that a Context Function is assigned to a Logical Context Element. Note: This fact may be derived from the Usage of Function of a Context Function allocated to a Logical Context Element.
APEimplementingGFN
SPFNallocatedToLET	Specifies the fact that a System Partial Function is assigned to a Logical SOI Element. Note: This fact may be derived from the Usage of Function of a System Partial Function allocated to a Internal Logical Element Role
SPFNallocatedToAPE	Specifies the fact that a System Partial Function is assigned to an Abstract Physical Element. Note: This fact may be derived from the Usage of Function of a System Partial Function allocated to a Physical SOI Element Role
LETimplementingGFN	Specifies the fact that a Logical Element is responsible to implement a System Function. Note: Logical Elements don't "implement" anything, they pass the function implementation task to Physical Elements.
specifying	Specifies the fact that one or more Logical Element specifies exactly one Physical Element. Rationale: If more than one Physical Element would offer to realize the functionality specified by a Logical Element the responsibility would be ambiguous. It is okay to assign several Logical Elements to one Physical Element. This means all specified functionality assigned to the Logical Elements is to be implemented by the Physical Element. Note, that typically the usage of logical elements in a context is mapped to the usage of physical elements in a context (allocation of usage). Thus this relationship between the definitions is derived.