ГОСТ Р 55346—2012
field : another_type;</p><p>end type:</px/note> <r>ote number=»5»>The is_alias_(or identifies the field of a composite
data type that is assigned to the data variable (Data_instance) of the is_alias_for.</note> <note number=»6»>The data
attribute is inherited from the entity lo_port.</note> *)
is_alias_for: data_instance:
(* The port_of specifies the lo_port of which the lo_composition_port is a part. *)
port_of: data_composition_select;
DERIVE
SELF\io_port.role : port_data_relation := port_of.role;
UNIQUE
UR1: port of. SELF\io_port.io_port_number;
END_ENTITY:
(•An lo_port is a part of the interface of a functional object. <note number=»1»>An io_port is an abstract entity and shall
not be instantiated.</note> *)
ENTITY io_port
ABSTRACT SUPERTYPE OF (ONEOF(actual_io_port. control_io_port. formalJo_port. io_composition_port));
(* The data specifies the Datajnstance that defines the format of the element in the interface. *)
data : datajnstance:
(* The io_port_number in combination with the port_type attribute and the port_of attribute shall be unique within the set
of ports attached to an element. The *o_port_number is the identifier of the lo_port. *)
io_port_number: INTEGER:
(* The portjype specifies the nature of the lo_port. The portjype is one of the following: <ulxli>input: The port is
handling information originating from elements outside the context of the functionality the lo_port is an element of the
interface;</1i> <li>output: The port is handling information originating from elements inside the context of the function
ality the lo_port is an element of the interface:<rti> <li>control: The port is a specialisation of an input such that the
information provided by this part of the interface is a prerequisite for the activation of the element the lo_port is part
of the interface of.<ffix/ulxnote number=»2»>The control is provided to allow for representation of IDEFO control
inputs. Semantically there is no difference between a control and an input portJype.</note> <ulxli>mechanism:
The
port is a specialisation of an input such that the resources provided by this part of the interface is a prerequisite for the
activation of the element the lo_port is part of the interface of.</li></ul><note number=»3»>The mechanism is provid
ed to allow for representation of IDEFO control inputs. Semantically there is no difference between a mechanism and
an input port_type.</note> *)
portjype: portjype;
(* The role specifies the interaction of the lo_port. The role may either produce information or consume information. The
role is one of the following: *)
role : port_data_relation;
END_ENTITY:
(‘ An lo_port_binding is the mapping from oneActualJo_port object to a FormalJo_port object. <note number=»1»>ln
programming languages, this corresponds to the mapping between formal and actual parameters in a function cail.</
note> <r>ote number=»2»>An lo_port_binding is valid only if the ActualJo_port is connected to a Functionjnstance as
its definition attribute has the GeneralJunction_definition object that the FormalJo_port is a port_of.</note> *)
ENTITY io_port_binding:
(* The actual_port specifies the Actual Jo_port object in the mapping. *)
actual_port: actualJo_port;
(* The formal_port specifies the FormalJo_port object in the mapping. *)
formal_port: formal_io_port;
WHERE
WR1: (SELF.formal_port.data :<>: SELF.actual_port.data):
WR2: formal_port.role <> actual_port.role:
WR3: correct_binding(SELF);
END_ENTITY:
(*An lo_splitJoin is a type of Generaljunctionalityjnstance and a means for splitting up the components of a Func-
tionaljink object carrying composite data into several FunctionaIJink objects carrying basic data or merging a Function-
aljink carrying basic data to a FunctionaIJink carrying composite data. <note>The future of this entity is not clear. It
may be removed from the mode! and the functionality may be replaced by an ordinaryfunction.</note> *)
ENTITY k>_splitJoin
SUBTYPE OF (generaljunctionalityjnstance):
END_ENTITY:
346