ГОСТ Р 55346—2012
with existing properties. In cases of conflict it shall be assumed thatthe properties of the recursive_data_type_definition
takes precedence over the properties of the redefined data type.</p> *)
ENTITY recursive_data_type_definition
SUBTYPE OF {user_defined_data_type_definition):
(* The redefines specifies the Maths_space or User_defined_data_type_definition that the RecursivejJataJype_defini-
tion is based on. *)
redefines : data_type_definit»on_select;
END_ENTITY;
(*A Requirement_allocation_property_relationship is a mechanism for relating a Requirementjnstance allocated to
an element to a Property_value assigned to that element. <note>This construct allows for tracing the consequences or
implications of allocating a requirement to an element.</note> *)
ENTITY requirement_allocation_property_relationship;
(* The allocated_requirement specifies the requirement in the relationship. *)
allocated_requirement: requirement_allocationjelationship;
(* The define_property_value specifies the Property_value that is influenced or defined by the requirement. *)
define_property_value: property_value;
(* The description specifies additional information about the Requirement_altocation_property_relationship. *)
description : OPTIONAL text_select;
END_ENTITY:
(*A Requirement_allocation relationship is the mechanism for allocating Requirementjnstance to another element
such that the element shall fulfil or has been found compliant with the capabilities stated by the requirement. <note>The
semantics of the Requirement_allocation_relationship are further defined by the role attribute.</note> *)
ENTITY requirement_allocation_relationship
SUPERTYPE OF (specific_requirement_allocation_relatk>nship);
(* The description specifies additional information about the Requirementallocationjelationship. *)
description : OPTIONAL text_select;
(* The relationjo specifies the element that the Requirementjnstance is allocated to. ’)
relationjo: requirement_allocation_select;
(* The requirement specifies the Requirementjnstance in the relationship. *)
requirement: requirementjnstance;
(* The role specifies the semantics of the relation. Where applicable the following values shall be used;<ul> dealloca
tion: The application j)bjed specifies an allocation relationship where the requirement object is allocated to the relation_
to object. The allocation relation means that the relation_to object shall be designed in such a way that the requirement is
fulfilled;</li> </li>fulfils: The application_object specifies a fulfils relationship where the requirement stated in the require
ment object is fulfilled by the relationjo object. The fulfils relation means that the relationjo object has been evaluated
and found to be compliant with the requirement object.</li> </ul> *)
role ; label;
END_ENTITY:
(*A Requirement_dass is a collector for requirements of similar characteristics. <note number=’ r>The standard does
not specify a fixed structure for requirement classification. Instead a dynamical structure is provided by the Requirement
class and the Requirement_classjelationship.</note> ’)
ENTITY requirement_dass;
(* The description specifies additional information about the Requirement_class. <note number="2>The description
may carry information identifying the characteristics of requirements that are m scope of the description.</note> ’)
description : OPTIONAL text_select;
(* The id specifies the identifier of the Requirement_class. *)
id ; element identifier
(* The name specifies the word, or set of words, that is used to refer to the Requirement_dass. *)
name: label;
UNIQUE
UR1: id;
END_ENTITY;
(‘ A Requirement_dass_relationship is a relationship between tw-o Requirement_class objeds. <note>The semantics of
the relationship are specified by the relationshipJype attribute.</note> *)
ENTITY requirement_dass_relationship:
(* The description specifies additional textual information about the spedalisation: The related_class Requirementj:lass
is a specialisation of the relatingj;lass Requirementj:lass. *)
375