ГОСТ Р 55346—2012
Requirement_instance objects build up the input to the relationship. Toindicate the output of the analysis any number of
Requirement_relationship_resulting_relationship objects may be used to indicate requirements created or identified as
results based on the requirement relationship.<i’li><i’note> *)
ENTITY requirement_relationship;
(* The description specifies additional information on the Requirement_relationship. *)
description : OPTIONAL text_select;
(* The relationship_type specifies the type of relationship. Where applicable one of the following values shall be
used:<ul> <li>alternate: The requirements associated via Requirement_relationshipJnput_assignment objects to the
Requirement_relationship are mutually exclusive or equivafent;</li> <li>derived: The requirements associated via Re-
quirement_relationship_input_assignment objects are used to derive additional Requirementjnstance objects. The new
requirements are indicated using Resulting_relationship objects.</li> <ul> •)
relationship_type: label:
END_ENTITY:
(*A Requirement_relationship_context_assignment is the mechanism for associating a Requirement_relationship or Re-
quirement_allocation_relationship to a System_view for which the relationship is valid. <note>The Requirement_relation-
ship_context_assignment allows for specifying that a relationship is valid for more than one System_view. which allows
for reuse of the specification elements over multiple versions of a system specification.</note> *)
ENTITY requirement_relationship_context_assignment:
(* The assigned_requirement_re!ationship specifies the relationship assigned to a system_view by a assigned_require-
ment_relatk>nship.
*)
assigned_requirement_relationship: assigned_requirement_relationship_select;
(* The description specifies additional information about the Requirement_retationship_context_assignment.’)
description: OPTIONAL text_select;
(* The system_context specifies the system_view that the requirement relationship is assigned to. *)
system_context: system_view:
END_ENTITY:
(’ A RequirementrelationshipJnput_assignment is the mechanism for assigning a Requirementjnstance to a Require-
ment_relaticnship. *)
ENTITY requirement_relationship_input_assignment;
(* The assignedjnstance specifies the Requirementjnstance in the relation. *)
assignedJnstanee : requirementjnstance;
(* The input_requirement specifies the Requirement_relationship in the relation. *)
input_requirement: requirement_relationship:
END_ENTITY:
(‘ A Requirementjelationship_resulting_relationship is the mechanism for relating a Requirementjnstance to a Require
mentrelationship indicating that the Requirementjnstance was implied by the Requirement_relationship. *)
ENTITY requirement_relationship_resulting_relationship;
(* The motivation specifies additional information about why the Requirement_relationship_resulting_relationship was
created. *)
motivation : OPTIONAL text_select;
(* The Requirement_relationship specifies the Requirementrelationship. *)
requirement_relationship: requirement relationship;
(* The resulting_requirement specifies the newly created requirement. *)
resutting_requirement; requirementjnstance;
(* The role ought to be deleted! *)
role; label:
END_ENTITY:
(*A Requirement_requirement_dass_assignment is die mechanism for assigning a Requirement_definition to a Require-
ment_class such that the characteristics of the Requirement definition are compliant with those defined for the Require-
ment_class. *)
ENTITY requirement_requirement_class_assignment;
(* The class specifies the Requirement_dass in the assignment. *)
class: requirement_class;
(* The motivation specifies the reason for the assignment. *)
motivation : OPTIONAL text_select;
(* The requirement specifies the Requirement_definition in the assignment. *)
378