ГОСТ Р 55346—2012
p!anned_end_date : OPTIONAL penod_or_date_select:
(* The planned_start_date specifies the Date_time when the Engineering_process_activity is or was supposed to start.
*)
planned_start_date : OPTIONAL event_or_date_select;
(* The resolved_request specifies the set of Work_request objects that is resolved by the Engineering_process_activity.
*)
resolved_request: SET [0 : ?] OF work_request;
(* The status specifies the level of completion of the Engineering_process_activity. *)
status : OPTIONAL text_select;
INVERSE
(* The is_controlling specifies the Engineering_process_activity objects that are controlled by this particular Work_order.
*)
authonzation : SET [0 : 1] OF workorder FOR is_controlling:
END_ENTITY:
(*An Engineering_process_activity_element_assignment is the relationship between systems engineering data and the
Engmeering_process_activity in which the data are "created in" or "modified in" or "referenced in". *)
ENTITY engineering_process_activity_element_assignment;
(* The activity specifies the Engineering_process_activity to which the Engineering_process_activity_element_assign-
ment belongs. *)
activity: engineering_process_activity;
(* The description specifies additional information about the Engineering_process_activity_element_assignment. *)
description : OPTIONAL text_select;
(* The element specifies the piece of systems engineering data referenced by the Engineering process activity. ’ )
element: specification_element_select;
(* The role specifies the function that is performed by the Engineering_process_activity_element_ass>gnment in the
context of the concerned Engineering process acbvity. Where applicable the following values shall be used:<ul><li>con-
trol: The referenced element had influence on completing the Engineering_process_actrvity;<1|li><li>created: The refer
enced element was created in the Engineering process activity:<.Ti><li>modified: The referenced element was modified
in the Engineering process activity.<Jli></ul> *)
role : label:
END_ENTITY:
(’ An Engineering_process_activity_relationship is a relationship between two Engineering_process_activity objects. *)
ENTITY engineering_process_activity_relat»onship;
(* The description specifies additional information about the Engineering_process_activity_relationship. *)
description: OPTIONAL text_select:
(* The related_activity specifies the second of the two Engineering_process_activity objects related by an Engineer-
ing_process_adivity_relatranship. *)
related_activity: engineering_process_activity;
(* The relating_activity specifies the first of the Er>gineering_process_activity objects related by an Engineering_pro-
cess_activity_retationship. *)
relating_activity: engineering_process_adivity:
(* The relation_type specifies a textual description of the nature of the relationship between the two Engineer-
ing_process_activity objects involved in the relationship. Where applicable one of the following values shall be
used:<ul><li>alternative: Either the relating_activity or the related_activity shall be performed;</lixli>hierarchy: The
relationship between the relating_activity and the related_activity is such that the relating_activity is divided into the re-
lated_acfivity;<flixli>sequence: The relating_activity and the related_activity shall be performed in sequence where the
relating_activity precedes the related_activity;</li><li>simultaneous: The relatir»g_activity and the related_activity may be
performed simultaneously.
<qiix/ui> •)
relation_type : label;
WHERE
WR1: relating_activity :<>: related_activity;
END_ENTITY:
An Event_data_type_definition is a type of Elementary_maths_space that includes all event values. *)
ENTITY event_data_type_definition
SUBTYPE OF (elementary_maths_space):
END_ENTITY:
333