ГОСТ Р 55346—2012
(* The lssue_sourcejelationship is the mechanism for relating the elements that played a part in raising an issue to a
criticalJssue. *)
ENTITY issue_source_relatk>nship:
(* The description specifies additional information on the lssue_source_relat»onship. *)
description : OPTIONAL text_select;
(* The issue specifies the Criticaljssue that the issue_source is assigned to. ’)
issue: criticaljssue;
(* The issue_source specifies the element that raised the issue. *)
issue_source; issue_source_select;
END_ENTITY:
(*An lssue_system_assignment is the mechanism for relating a Criticaljssue to the System_view or Systemjnstance
that the issue is relevant for. *)
ENTITY issue_system_assignment;
(* The description specifies additional information on the lssue_system_assignment. ’)
description ; OPTIONAL text_select;
(* The identified_system specifies the System_view or Systemjnstance in the relationship. *)
identified_system; system_select;
(* The issue specifies the Criticaljssue in the relationship. *)
issue; criticaljssue;
END_ENTITY;
(*A Justification is a textual description of the reasons for the existence of. or design rationale for. part of a system spec
ification. *)
ENTITYjustification;
(* The assignedjo specifies the object to which the Justification applies.’)
assignedJ o :justification_assignment_select;
(* The justificationJext specifies the textual comment on the object referenced by the assignedjo attribute. *)
justificationJext; text_select;
(* The role is the word, or words, that are used to describe the nature of the Justification. <example num-
ber=»12»>Roles for a Justification might be «comment», «rationale», or «justification».«/example> *)
role ; label;
END_ENTITY;
(*A Justification_re!ationship represents some relationships between two Justification objects. <note>The exact se
mantics of the relationship depend on the value of the relationshipJype attnbute.</note> «example number=»13»>The
relationship between two Justification objects can arise from a situation where the choice of one alternative for a given
part of the design may impact on further choices making potential alternatives invalid.«/example> *)
ENTITY justificationjelationship;
(* The description specifies additional textual information about the Justificationjelationship. *)
description : OPTIONAL text_select;
(* The related specifies the second Justification in the relationship. *)
related;justification;
(* The relating specifies the first Justification in the relationship. •)
relating ;justification;
(* The relationshipJype specifies the semantics of the relationship. *)
relationship Jype: label;
END_ENTITY:
(*A Leaf Junction_definition is a type of Generai_function_definition that is not decomposed any further, «note num
ber»! »>A function hierarchy is always terminated by a LeafJuncfion_definition. In a later release of the system under
design, a Leaf Junction might become a compositeJunction_definition. This case is handled by the use of Configura-
tion_e!ement_version items identifying two different releases of the same object.</note> *)
ENTITY leafJunction_definition
SUBTYPE OF (general_function_definition);
(* The definition specifies the text that describes what (the service, transformation, state change, etc.) is performed by
the function.The definition specifies the Textual_specifieation object that defines the specification and specification lan
guage for the Leaf Junction_definition. «note number=»2»>The standard does not feature any means to ensure
consis tency and correctness of the content of the definition.</note> *)
definition: textual_specification;
347