ГОСТ Р 55346—2012
ENTITY requirementjJefinition
ABSTRACT SUPERTYPE OF (ONEOF(model jJefinedjequirementjfefinition. structuredjequirementjlefinition. textu
al jequirementjlefinition));
(* The associated_version specifies the Configuration_elementj/ersion for the Requirement_definition. *)
associated_version: configuration_element_version;
(* The id specifies the identifier of the Requirement_definition. *)
id : elementjdentifier.
(* The name specifies the word, or set of words, that is used to refer to the Requirement_definition.’)
name : OPTIONAL label;
INVERSE
(* The parent_defmition specifies the decomposed Requirement_definition n the relationship. *)
composed_of; SET [0 : ?] OF requirement composition_relationship FOR parent_definition;
(* The requirement specifies the Requirement_definition in the assignment *)
injequirementjlass : SET [0 : 1] OF requirement_requirement_class_assignment FOR requirement;
UNIQUE
UR1:kJ;
END_ENTITY;
(*A Requirementjnstance is a context dependent representation of a requirement for a particular system. <note>The
Requirement_occurence and Requirement_definition objects provide the definition of what is required.</note> *)
ENTITY requirementjnstance;
(* The definition specifies the Requirement_occurrence that provides additional information on what is required. *)
definition: requirementoccurence;
(* The id specifies the identifier of the Requirementjnstance. *)
id :elementjdentifier.
(* The name specifies the word, or set of words, that is used to refer to the Requirementjnstance. *)
name; label;
INVERSE
(* The associated_requirement specifies the Requirementjnstance in the relationship. *)
implied_extemal; SET [0 : ?] OF implied_extemal Jnteraction FOR associated_requirement:
UNIQUE
UR1: definition, id;
END_ENTITY;
(‘ A Requirement_occurence is the placeholder for a static instance of a requirement in a requirement breakdown hierar
chy. *)
ENTITY requirement_occurence;
(* The definition specifies the Requirementjfefinition object that provides the definition of what is required. ’)
definition ; requirement definition;
(* The id specifies the identifier of the Requirement_occurrence.’)
id ; elementjdentifier.
(* The name specifies the word, or set of words, that is used to refer to the Requirement_occurence. *)
name : label;
INVERSE
(* The chikfjequirement specifies the decomposing Requirement_occurence object in the relationship. *)
child_of; SET [0 ; ?] OF requirementjximpositionjelationship FOR childjequirement;
UNIQUE
UR1: definition, id;
END_ENTITY;
(*A Requirementjelationship is a means of representing relationships among Requirementjnstance objects. <note
number=T>The Requirementjelationship may record the existence of relationships among a set of requirements or
may be used to capture relationships between sets of requirements and individual requirements.</note> <note num
b e r’2">The Requirementjelationship may be used, for example, to identify alternate or derived between requirements
in different System_view objects.</note> <note number="3“>There are two ways of using the Requirementjelationship:
<olxli>To relate a number of requirements. The purpose of the relation is specified by the relationship type attribute.
Any number of Requirement jelationship_input_assignment objects relating Requirement_re!ationship objects and a
number of Requirementjnstance objects maintains such a relation. In this use no new Requirementjelationshipjesult-
ingjelationship are instantiated as a result of the establishment of the Requirement_relationship.</li><li>The creation
or identification of requirements that are dependent on an established requirementjelationship. As in the first case, any
number of Requirement_relationshipJnput_assignment objects relating a requirementjelationship and a number of
377