ГОСТ Р 55346—2012
(‘ A Realized_system is the reference to a physically realized system. A Realized_system is realized in accordance with
a specification identified by the realisztion_of attribute. <note number=T>The data model has been extended to cover
real systems in order to correctly represent verification plans and verification results.<>’note> *)
ENTITY realized_system;
(* The description specifies additional information on the Rea!ized_system. ’)
description: text_select;
(* The id specifies the identifier of the Realized_system. <note number="2~>The id typically specifies the serial number
of the Realised_system.</note> *)
id: etementjdentifier
(* The name specifies the word, or set of words, that is used to refer to the Realized_system. *)
name : label;
(* The realization_of specifies the systemJnstance that provided the specification for the realization of the Realized_
system. ’)
realization_of; systemjnstance;
UNIQUE
UR1; id. realization_of;
END_ENTITY:
(‘ A Realized_system_composition_relationship is the hierarchy relationship between two Realized_system objects. The
super-system in the composition is identified via the system attribute and the sub-system is identified via the component
attribute. <note>The Realized_system_composition_relationship specifies that a system of system structure has been
formed for some purpose. In the scope of PAS 20542. the most likely reason is for verification that realized systems are
conformant with the specification that the realization was based on.</note> ’)
ENTITY realized_system_composition_relationship;
(* The component specifies the sub-system in the Realized_system_composition_relationship. *)
component; realized_system:
(* The description specifies additional information on the Realized_system_composition_relationship. *)
description: text_select;
(* The mirror_of specifies the System_composition_relationship that is realized in a physical system and indicated by
the Realized_system_composition_retationship. *)
mirror_of; system_composition_relationship;
(* The system specifies the super-system in the Realized_system_composition_relationship. *)
system ; reafized_system;
END_ENTITY:
{’ A Record_data_type_definition is a type of User_defined_data_type_defmition that combines a number of values into a
single item (arecord). There is a dependency between the combined values that limits their use independently. <exam-ple
number="27’>Assume the following dedaration:<ol><li>record EmployeeDetails</li><li>name : String:</p><p>date_
of_birth ; Date;</p><p>age ; Integer Derived =TODAY - date_of_birth;</pxp>end record;</p><p>The date_of_birth is
the date_of_birth of the employee named in the record. If the date of birth is separated from the rest of the details of the
employee then it becomes just a date.</px/exampie> *)
ENTITY record_data_type_definition
SUBTYPE OF (user_defined_data_type_definition):
END_ENTITY:
(‘ A Record_data_type_member is a relationship between a Record_data_type_definition and a Data_field it contains.
There is no order amongst the occurrences. All of the members of a Record_dataJype_definition must be present. ’)
ENTITY record_data_type_member;
(* The child specifies the Data_field object in the relationship. *)
child ; data_field;
(* The parent specifies the Record_data_type_definition in the relationship. *)
parent; record_data_type_definition;
END_ENTITY:
(‘ A Recursive_data_type_definition is a type of User_defined_data_type_definition and a redefinition of another data
type definition. At its simplest a Recursive_data_type_definition renames or re-describes another data type. At its most
complex, a Recursive_data_type_definition attaches new properties, possibly overriding ones of the redefined
User_de-fined_data_type_definition or Maths_space. <p>A recursive data type inherits the properties of the data type it
rede-fines.</p> <p>A recursive data type may have properties that the data type it redefines does not have.</p> <p>A
recur sive data type can have alternate values for properties that the type it redefines has. Redefined properties may
conflict
374