ГОСТ Р 55346—2012
(* The name specifies the word, or set of words, that is used to refer to the Verification_specificatk>n. *)
name: label;
(* The verification_method specifies how the test shall be carried out for a particular system.’)
verification_method : label;
END_ENTITY:
(*A Verification_specification_allocation is a mechanism for allocating a Verification_specification to a Systemjnstance,
a PhysicaIJnstance. a Functionjnstance, or a Requirementjnstance such that the Verification_specification shall be
applied to the allocated object. *)
ENTITY verification_specification_allocation;
(* The description specifies additional information about the Verificatkjn_specification_ailocation.’)
descnption : OPTIONAL text_select;
(* The relevant_for specifies the object that the Verification_specification is allocated to. *)
relevant_for: verification_allocation_select;
(* The specification specifies the Verificationspecification. *)
specification ; verification_specification;
END_ENTITY;
(’ A Verification_specification_system_view_relationship is the mechanism for assigning a Verification_specification to a
System_view indicating the test specification shall be applied for verifying and or validating the system. *)
ENTITY verification_specification_system_view_relationshjp;
(* The assigned_verification specifies the assigned Verification_specification. *)
assigned_verification: verification_specification;
(* The description specifies additional information about the Verification_specification_system_view_relationship. *)
description: OPTIONAL text_select;
(* The index specifies an identifier for the Verification_specification identified by the attribute assigned_verification in the
context of the system_view defined by the system_view attribute. *)
index : label;
(* The system_view specifies the System_view to which the Verification_specification is assigned. *)
system_view : system_view;
END_ENTITY;
(*A View_re!ationship is a hierarchical relation between two Visual_element objects such that the child object is a part
of the Graphics_view of the parent object. <note number=T>lf a View_relationship exists between two Graphics_view
objects the same hierarchical relationship shall exist between the General_function_definition, General_physical_defi-
nition or Fsm_generic_state objects involved in the hierarchy.</note> <note number="2">Each Graphics_view object is
potentially part of many Multi_level_view objects. Toallow for overlapping views each View relationship shall, via the
validjn attribute define the Muitijevel_view for which the relationship is valid.</note> *)
ENTITY view_relationship;
(* The child specifies the Graphics_view that is superimposed in the Graphics_view of the parent. *)
child: graphics_view;
(* The parent specifies the Graphics_view that acts as a context of the child Graphics_view. *)
parent: graphics_view:
(* The validjn specifies the Multi_level_view for which the relation is valid. •)
validjn: multijevel_view;
END_ENTITY;
(*A Visual_element is the super-type for aBentities carrying graphical information for an object. A Visual_element is a
Graphics_node. an Actual_port_position, a Formal_port_position. or a GraphicsJink. *)
ENTITY visual_e!ement
ABSTRACT SUPERTYPE OF (ONEOF(actual__port_position. formal_port_position. graphicsjink. graphics_node));
(* The view specifies the Graphics_view for which the Visual_element is defined. ")
view: graphics_view;
END_ENTlTY;
(*A Work_order is the authorization for one or more Engineering_process_activity objects to be performed. *)
ENTITY work_order
ABSTRACT SUPERTYPE OF (ONEOF(change_order. start order));
(* The description specifies additional information about the Work_order.’)
description :OPTIONAL text_select;
(* The id specifies the identifier of the Work_order. *)
389