ГОСТ Р 55346—2012
the semantics of the selection_package.</note> <note number=’2*>The seiection_package allows a specification that
provides a constraint that only one of the elements may be selected from the elements in the Package .</note> ’)
ENTITY selection_package
SUBTYPE OF (package):
(* The selection_type specifies the selection constraint. Where applicable one of the following values shall be used:<ul
<li>and: One element of the package may be selected for a particular system;</li> <В>ог: Any number of elements of the
package may be selected for a particular system.</ul> </li> *)
selectionjype: label;
END_ENTITY;
(*A Single_cardinality is a single integer representing a numerical constraint. *)
ENTITY single_cardinality;
(* The defined_value specifies the numerical constraint. *)
defined_value; single_cardinality_select;
END_ENTITY:
(*A Specific_requirement_allocation_relationship is a type of Requirement_allocation_relationship that serves as a
mechanism for the allocation or tracing of a requirementjnstance to an element that cannot be unambiguously identified
in a functional breakdown structure, for example, an Fsm_generic_state or Cb_place. <note number=’ 1’>The method
for identifying elements in the breakdown structure is to identify the Functionality_instance_reference closest in the
breakdown structure to the Fsm_generic_state or Cb_place via the related_to attribute and to specifically identify the
traced object via the specific_element attribute.</note> <notev number="2“>ln cases where the Specific_requirement_al-
location_relationship indicates a requirement allocation to an Fsm_generic_state. the related_to attribute shall identify
the Fsm_model object that defines the context of the finite state machine.</note> <note number=’3’>ln cases where
the Specific_requirement_allocatK>n_relationship indicates a requirement allocation to a Cb_place. then the related_to
attribute shaB identify the Functionality_instance_reference that, in turn, identifies the Composile_function_definition (via
a Functionjnstance) which is constrained by the Functional_behaviour_model of which the Cb_p!ace identified by the
Specific_element attribute is an element.</note> *)
ENTITY specific_requirement_allocation_relationship
SUBTYPE OF (requirement_allocation_relationship);
(* The specific_element specifies the object that the requirement is allocated to via the Specific_requirement_alloca-
tion_relationship. *)
specific_element: specific_element_select:
WHERE
WR1; SYSTEMS_ENGINEERING_DATA_REPRESENTATION.FUNCTIONALITY_INSTANCE_REFERENCE’ IN
TYPEOF(SELF\requirement_allocation_relationship.relation_to);
END_ENTITY:
(‘ A Specification_state_assignment is the mechanism for assigning a Textual_specification to a Fsm_state such that the
specification is implemented by the state. *)
ENTITY specification_state_assignment;
(* The assigned_to specifies the Fsm_state in the assignment. ’)
assignedjo: fsm_state:
(* The specificafion specifies the Textual_specification in the assignment. *)
specification ; textual_specification;
END_ENTITY;
(*A Start_order is a type of Work_order that serves as the authorization for one or more Engineering_process_activity
objects to be performed. <note>A Start_order captures all kinds of work orders except for order for changes - which is
handled by Change_order.</note> ■)
ENTITY start_order
SUBTYPE OF (workorder);
(* The start_order_type specifies the type of activity authorized by the Start_order. Where applicable one of the follow
ing values shall be used:<ul><li>design_activity: authorisation to start design activity for a system:</!i> <li>impact_analy-
sis: authorisation to start analysis activity for identifying the impact of a critical issue.</li> </ul> *)
start_order_type; label:
END_ENTITY;
(*A Start_request is a type of Work_request that solicits the commencement of some work. <note>A Start_request cap
tures all kinds of requests to start activities except for change related information.</note> *)
ENTITY start_request
380