ГОСТ Р 55346—2012
textual_paragraph.
textual_section,
textualjable);
END_TYPE;
TYPE timing_type = ENUMERATION OF
(best_case,
nominal_case.
worst_case);
END_TYPE:
TYPE triggerJype_enumeration = ENUMERATION OF
(flank,
level);
END_TYPE;
TYPE verification_aliocation_select = SELECT
(functional! ty_instance_refe rence.
physical_instance_reference.
realized_sysfem.
requirementJnstance,
system_instance);
END_TYPE;
(•An Abstract_data_type_definition is type of User_defmed_data_type_definition that may have the value of any. all or
none of its members. *)
ENTITY abstract_data_type_definition
SUBTYPE OF (user_defined_data_type_definition);
END_ENTITY;
(’ An Abstract_datajype_member is a relationship between an Abstract_data_type_definition and a Data_instance it
contains. The members of anAbstract_data_type_definition are independent of each other. *)
ENTITY abstract_data_type_member;
(* The child specifies the Datajnstance object in the relationship. *)
child ; datajnstance:
(* The parent specifies theAbstract_data_type_definition object in the relationship. *)
parent: abstract_data_type_definition:
END_ENTITY;
(’ An ActualJo_port is a type of lo_port and an element of the interface of a GeneraMunctionalityJnstance object. An
ActualJo_port defines an input or an output parameter to the GeneraMunctionalityJnstance object it is referring to via
the port_of attribute. <note>Flow ports are classified according to three criteria in the data model;<ol><li>Whether the port
is formal (attached to a GeneralJunction_definition type object) or actual (attached to a General[.functionalityJn-stance
type object).</li><li>Whether the port is an input
or
output port.<tfi><li>Whether the port is a flow or control port (a flow port
carries data whereas control port carries triggering information such as start, stop, suspend, resume). This kind of port is
further defined in controlJo_port</lt><p>From this classification, the role a port plays with regard to the Flow objects
connected to the port can be derived. A port can ’consume’ io data (the data on the flow is delivered to the port) or it can
’produce" io data (the data on the flow is delivered from the port).</p><p>For instance, a FormalJo_portwhose direction
attribute is ’input’ produces data, while an ActualJo_port whose direction attnbute is ’input’ consumes data. In the data
model this information is captured in the derived attribute role.</p><p>This attnbute is used to ensure that Io ob jects are
connected correctly (an io object must have one producer and one consumer), and that lo_port_binding objects applied
only to ports where the actual_port in the binding is a producer of information and the formal_port in the binding is a
consumer or vice versa.</p></note> *)
ENTITY actualJo_port
SUBTYPE OF (io_port);
(* The port_of specifies the GeneraMunctionalityJnstance object of which the port_of is part.
*)
port_of: generaMunctionalilyJnstance;
DERIVE
(* Tire role specifies one of producer’, or consumer’. *)
SELF\io_port.role : port_data_relation ;= determineactualportrole(SELF);
313