ГОСТ Р 55346—2012
DERIVE
data_on_link : datajnstance := source_port.data;
WHERE
correcl_ports: ((destmationport.role =consumer) AND (source_port.role = producer)):
END_ENTITY:
(*A FunctionalJink_allocation_relationship is the mechanism for indicating that a FunctionalJink_reference shall be rout
ed onto a particular Physical_instance_reference. <note>A prerequisite for the allocation is that the allocated function-
aljink is allocated to a Physical_instance_reference that is part of the same System_view object.</note> ’)
ENTITY functional_link_allocation_relationship:
(* The allocatedjunctionaijink specifies the FunctionalJink_reference in the Functional_link_altocat»on_relationship.’)
allocated_functional_link: functionalJink_reference:
(* The allocated_to specifies the Physical_instance_reference in the relationship.
*)
ailocated_to: physical_instance_reference:
(* The descnption specifies additional textual information about the Functional_link_allocation_relationship. *)
description: OPTIONAL text_select;
END_ENTITY:
(*A Functional_link_group is a container for grouping related Functional Jink objects. <note>A functionatJink_group
allows a designer to refer to a group of FunctionaIJink objects as if they constituted a single flow. One reason for using
a FunctionalJink_group in a model is that it allows for the assignment of the same graphical properties to the group
objects that are members of the FunctionalJink_group.</note> *)
ENTITY functionalJink_group:
(* The elements is the set of FunctionaIJink objects that make up the Functional_link_group. *)
elements : SET [2 : ?] OF functional Jink;
(* The name specifies the word, or words, thatare yused to refer to the Functionaljink_group. *)
name : label;
END_ENTITY;
(*A FunctionalJink_reference is the unambiguous reference to FunctionaIJink objects in the context of a GeneraHunc-
tionalityjnstance that is further decomposed. *)
ENTITY functionalJink_reference;
(* The in_scope__of specifies the Functionality_instance_reference which defines the context of the functionaljink iden
tified by the FunctionalJink_reference. *)
in_scope_of: functionalityJnstance_reference;
(* The referencejunctionaljink specifies the FunctionaIJink for which the FunctionalJink_reference is the unambigu
ous reference. *)
referencejunctionaljink : functionaljink;
END_ENTITY;
(*A Functional_reference_configuration is a collector for all Functionality_reference_composition_relationship objects
that apply for a particular functional view on a system. <note number=’1*>A Functional_reference_configuration may be
assigned to any number of systems through the use of multiple SystemJunctional_configuration objects.</note> <note
number="2*>The Functional_reference_configuratk>n provides the means for defining multiple non-functional views of
single system functional architecture model.</note> *)
ENTITY functional_reference_configuration;
(* The description specifies additional information about the Functional_reference_configuration. *)
description : OPTIONAL text_select;
END_ENTITY:
(*A Functional_representation_relationship is the mechanism for indicating that a datajnstance. used within the
functional view of a specification, is acting as an alias for a PhysicaIJnstance from a physical view of the specification.
<r»ote>The Functional_representation_relationship is motivated by the need to allow for functional models to reference
other elements than data types, while maintaining a rigourous structure in the model. <p>The alternative would be to
allow lo_port objects to directly carry objects of other types than of Datajnstance. While straightforward, this
approach would lead to severe interpretation problems for tools incapable of representing items other than
Datajnstance ob jects.<i’p></note> *)
ENTITY functional_representation_relationship;
(* The description specifies additional information about the Functional_representation_relationship. *)
description; OPTIONAL text_select:
340