ГОСТ Р 55346—2012
(‘ An Aggregate_data_type_definition is is a type of User_defined_data_type_definitk>n that comprises a list (or lists) of
values.’)
ENTITY aggregate_data_type_definition
SUBTYPE OF (user_defined_data_type_definition):
(* The aggregate_type attribute specifies the values that each element in the list can take.’)
aggregate_type : data_type_definition_select
(* The bound specifies the ordered set of elements of the Aggregate_data_type_definition. it is assumed, for the pur
poses of assigning compound values, that the aggregate is stored in row order. *)
bound : LIST [1 : ?] OF integer_interval;
END_ENTITY;
(’ An Approval is a judgement concerning the quality of those product data that are subject to approval. An Approval
represents a formal statement made by technical personnel or management personnel regarding whether or not certain
requirements are perceived to be met by the reviewing body. <note number=T>This needs to be reviewed for applicabil
ity of text</note> <note number=’2’>This entity is from the PDM schema.</note> *)
ENTITY approval:
(* The level indicates the kind of activity that may be performed and granted by theApproval. Where applicable, the
following values shall be used: <ut><!i>disposition: The approved object is approved for senes production;</li><li>equip-
ment order: The approved object has reached a status inwhich changes are subject to a defined change process and
tools and other equipment required for production may be ordered;</li><li>planning: The approved object is technically
complete and has reached a status sufficiently stable so that other designs may be based on it.</lix/ul> *)
level: OPTIONAL label:
(* The status specifies thejudgement made about the product data that is the subject of this Approval. *)
status: label:
END_ENTITY;
(*An Approval_assignment is the assignment of anApproval to an element of a system specification. *)
ENTITY approval_assignment;
(* The assigned_approvai specifies theApproval that is assigned. *)
assigned_approval: approval;
(* The assigned_to specifies the system engineering specification element for which the Approval_assignment is valid.
*>
assigned_to: approval_assignment_setect:
(* The description specifies additional information about the Approvai_assignment.")
description: OPTIONAL text_select;
(* The status specifies thejudgement made about the system engineering specification element that is the subject of
this Approval_assignment. *)
status: label:
END_ENTITY:
An Approval_person_organization is the relation between an approval and the juridical person involved in the approval.
The semantics of the relation is further defined by the role attribute. *)
ENTITY approval_person_organization:
(* The authorized_approval specifies the approval for the Approvai_person_organization. *)
authorized_approval: approval:
(* The person_organization specifies the juridical authority involved in the Approval_person_organization. *)
person_organization : person_organization_select;
(* The role specifies the semantics of theApproval_person_organization.<p>Where applicable one of the following
values shall be used:</p><ul><li>project responsible: The person approving is doing so in the role of being responsible
for the project to which the system specification element belongs;<j’li>Oi>verification responsible: The person approving is
doing so in the role of being responsible for verification of the specification element.</li></ul> *)
role: label:
END_ENTITY;
(’ An Approval_relationship is a relationship between two Approval objects. <r»ote>Attribute for defining the semantics of
the relation shall be added.</note> *)
ENTITY approval_relationship;
(* The description specifies additional information about the Approval_relationship. *)
description: OPTIONAL text_select;
(* The related_approval specifies the second Approval in the relationship. *)
related_approval: approval;
315