ГОСТ Р 55346—2012
relating_version : configuralion_element_version:
(* The relationshipJype specifies the semantics of the configuration_element_vefsion_relatrariship. Where applicable,
one of the following values shall be used:<il><li>revision;</li> <li>workspace_revision;</li><li>alternative.</li></uf> *)
relationship_type: label;
WHERE
WR1; re!ated_version :<>; relating_version;
END_ENTITY;
(*A Context_funclion_relationship is the relationship between a Functionjnstance object and a System_view object
such that the Functionjnstance object is part of the functional description of the System_view. <note number=’1*>The
Functionjnstance may describe functional aspects of the System_view or functional aspects of the environment to the
System_view. In the first case the role attribute shall be set to "systemJunction’, in the second case the role attribute
shall be set to *external_element’.o’note> *)
ENTITY contextJunction_relationship;
(* The associated_context specifies the System_view that is valid for the relationship. *)
associated_context; system_view:
(* The Contextjunction specifies the Functionjnstance object that is valki for the relationship. *)
contextjunction: functionjnstance:
(* The description specifies additional textual information on the relationship. *)
description ; OPTIONAL text_select;
(* The role specifies what the Functionjnstance describes in the context of a particular System_view. <note num-
ber=‘2">There is a constraint that there shall only be exactly one functionjnstance assigned to a System_view as a
"systemJunction’.</note> *)
role ; function_rote_enumeration:
INVERSE
(* The system specifies the oontextjunction_relationship to which the functional_reference_configuration is assigned.
*)
assignedJunctional_configuration ; SET [0 : 1] OF systemJunctional_configuratk>n FOR system;
UNIQUE
UR1; associated_context. contextjunction:
END_ENTITY:
(*A Context_physical_relationship is the relationship between a PhysicaIJnstance object and a System_view object
such that the PhysicaIJnstance object is part of the top-level physical architecture description of the System_view.
<r»ote>The PhysicaIJnstance may describe physical aspects of the System_view or physical aspects of the environment
to the System_view. In the first case the rote attribute shall be set to "system_e!ementH. in the second case the role attri
bute shall be setto *external_element\<.’note> *)
ENTITY context_physical_relationship;
(* The description specifies additional textual information on the relationship. *)
description : OPTIONAL text_select;
(* The partJn_physical_context specifies the System_view object for which the relationship is relevant. ’ )
part_in_physical_context: system_view;
(* The PhysicaIJnstance specifies the PhysicaIJnstance for which the relationship is valid. *)
PhysicaIJnstance: physicalJnstance:
(* The role specifies the nature of the PhysicaIJnstance in the System_view. *)
role: physical_element_role_enumeration;
INVERSE
(* The system specifies the Context_physical_relationship to which the Physical_reference_configuration is assigned. *)
assigned_physical_configuration : SET [0 : 1] OF system_physical_configuration FOR system;
END_ENTITY:
(*A Contro!Jo_port is a type of lo_port and an element in the behavioural interface to a Functionjnstance object. A Con
trolJo_port is always an input port and consumes data from Functional Jink objects. <r>ote number="1’>The semantics
is such that the ControlJo_port is enabled or disabled by the value of the data associated with the ControlJo_port. If the
Controljo_port is enabled, it may activate the Function instance.</note> <note number=“2">lf the datajnstance defined
by the data attribute is of type event_dataJype_definition then the ControlJo_port is enabled by the arrival of an event
in the dataJnstance.</note> <r>ote number="3*>lf the datajnstance defined by the data attribute is of type logical_data_
type_definitk>n then the Controljo_port is enabled when the value of the datajnstance is TRUE. Otherwise the control_
io_port isdisabled.</note> <note number="4“>lf more than one controlJo_port is attached to a Functionjnstance object,
then all must be enabled to activate the Functionjnstance object. </r>ote> •)
ENTITY controtjo_port
325