ГОСТ Р 55346—2012
ENTITY cb_transition_relationship:
(* The related_transition specifies the set of Cbjransition objects that is involved in the Cb_functional_transition. *)
related_transition : SET [1 : ?] OF cb_functional_transition:
(* The relationship_type specifies the nature of the relationship. Where applicable the relationship_type shall be one of
the foBowing:<ul> <li>or. The Cb_transition_relationship represents a set of Cb_functional_transition (see ISO/WD PAS
20542 clause 4.2.25) objects that indicate the start or an end of a selective structure.</li> </ul> <note number=*3’>This
corresponds to an IF .. THEN .. ELSE statement in programming languages</note> <ul> <li>and: The Cb_transition_re-
lationship represents a set of Cb_functional_transition objects that indicate the start or an end of a concurrent structure;-^
li> <li>loop: The Cb_transition_relationship represents a set of Cb_functional_transition objects that indicate the start
or an end of a fixed loop structure.</li> </ul> <note number=’4’>For the loop keyword it is assumed that the number of
iterations in the loop is hardcoded.</note> <ul><li>iteration: The Cb_transition_relationship represents a set of Cb_func-
tional_transition objects that indicate the start or an end of a iterative structure where the exit condition is evaluated
dynamically;</li><li>replicat»on: The Cb_transition_relationship represents a set of Cb_functional_transition objects that
indicate the startor an end of a replicated structure.</li></ul><note number=’5’>Replication is the representation of a
multiple functional execution threads using a single functional structure.</note> *)
relationship_type: label:
INVERSE
(* The terminal_transition specifies final Cb_transition_relationship of the block. *)
end_bound : SET (0 : 1) OF causal_block_bound FOR terminal_transition;
(* The initial_transition specifies the initial Cb_transition_relationship of the block. *)
start_bound : SET [0 :1] OF causal_btock_bound FOR initial_transition;
END_ENTITY:
(*A Cb_transition_unbounded_\veight is the mechanism to indicate that the boundedness of a Cb_input_relationship or
Cb_output_re!ationship is defined at run-time. The boundedness defined by Cb_transition_unbounded_weight is a
natural number larger or equal to the value defined by the minimal_weight attribute. <note>The boundedness defines
the number of tokens generated by a Cb_input_relatk>nshipor the number of tokens consumed by a Cb_output_relation-
ship.</note> *)
ENTITY cb_transition_unbounded_weight:
(* The minimal_\ve>ght specifies the least number of tokens produced or consumed. *)
minimal_weight: natural_number;
END_ENTITY:
(*A Change_order is a type of Work_order that authorizes the implementation of one or more changes. <note>A
Change_order is normally proceeded by a Change_request object.</note> *)
ENTITY change_order
SUBTYPE OF (work_order):
(* The change_element specifies the elements that are subject to change as a result of the Change_order. *)
change_element: element_critical_issue_relationship;
(* The originates_from specifies the change_request that provided the motivation for the Change_order. *)
originates_from : change_request:
END_ENTITY:
(*A Change_order_relationship is a relationship between two Change_order objects. The semantics of the relationship
are defined by the Change_order_relationship_type attribute. *)
ENTITY change_order_relationship:
(* The change_order_relationship_type specifies the semantics of the change_order_relationship_type. Where appli
cable one of the following values shall be used:<ul> <li>tempora!_order: the relating Change_order shall be completed
before the implementation of the related Change_order:</li> <li>alternative: the relating Change_order is an alternative
to related Change_order. Only one of the two identified Change_order objects shall be effectuated.</li> </ul> *)
change_order_relationship_type : label;
(* The related specifies the second change_order in the relationship. *)
related : change_order;
(* The related specifies the first change_order in the relationship. *)
relating :change_order;
END_ENTITY:
(‘ A Change_report is a collection of elements reporting on changes performed as a resultof a change_request.
<note>The report of what has been changed can either described in text in the description attribute or by assigning other
specification elements to the Change_report by the use of Change_report_element_assignment objects.</note> *)
ENTITY change_report:
321