ГОСТ Р 55346—2012
(*A Stnng_data_type_definition is a type of Elementary_maths_space containing all of the stnngs up to length n that can
be formed from combinations of the allowable characters. Where n is the length of the string. If n is not given, the string
can have infinite length. *)
ENTITY string_data_type_definition
SUBTYPE OF (elementary _maths_space):
(* The size specifies the space occupied by the String_data_type_definition. <note number=T>The low bound of the
Finite_integer_interval is generally not used but is available when a future use (such as the identification of sub-strings
within strings) becomes apparent. The low bound should be set tozero.</note> <note number=’2‘>The size of the
Finite_mteger_interval is the maximum number of characters and instance of a String_data_type_definition can have. </
note> A size need not be given for a String_data_type_definition in which case it has an unknown length. The size need
not be specified for a particular String_data_type_definition object. *)
size : OPTIONAL finite JntegerJnterval:
END_ENTITY:
(*A Structured_requirement_defmition is a type of Requirement_definition with the discriminator that the required capa
bility is expressed as a value. <note number=’1">This entity provides the capability to represent requirements that are
structured and typed - as opposed to requirements expressed in text.</r»ote> <note number=‘2*>The name of this
entity shall be reconsidered. The current name reflects the fact that the property model is used to store the requirement.
A potentially better name is Structured_requirement_definitk>n.</note> ’)
ENTITY structured_requirement_defmition
SUBTYPE OF (requirement_definition):
(* The required_characteristic specifies the Property_value that provides the structured definition of the requirement. *)
required_characteristic: property_value;
END_ENTITY:
(*A System_composition_relationship is the decomposition relationship between a Systemdefinition object and a Sys
temJnstance object that is a sub-system of the System definition object. ’ )
ENTITY system_composition_relationship;
(* The component_system specifies the sub-system in the relationship. *)
component_system : systemjnstance;
(* The decomposed_system specifies the system in the relationship. *)
decomposed_system : system_definition;
(* The description specifies additional textual information about the relationship.’)
description : OPTIONAL text_select;
(* The relationship describes the type of the System_composition_relationship. Where applicable one of the following
values shall be used:<ul> <li>mandatory: The sub-system must be in the system breakdown structure of a real system
for it to be valid;<fli> <li>optional: The sub-system may. but is not required to. be in the system breakdown structure for
any real system.</li> </ul> *)
relationship_type: label;
END_ENTITY:
(*A System_definition is a type of System view and a representation of a system specification for a life cycle of a
system. <note>The specification may be in any degree of completeness. The system_definitk>n. via relationships to the
collection of detailed entities (function_definition etc), forms the system specification at that point in its evolution. At
com pletion. the System_definition will form the complete system specification for the system life cycle that the
System_defini-tion defines.</note> ")
ENTITY system_definition
SUBTYPE OF (system_view);
(* The life_cycle_stage specifies the phase in the system life-cycle the System_definition is valid for. <example num-
ber=‘29">The value for life_cycle_stage may be ‘operational’ indicating that the System_definition provides the specifi
cation for the operational stage of the system under specification.</examp!e> *)
life_cyde_stage ; label;
INVERSE
(* The system_definition_context specifies the System_definition object for which the Partial_system_view is valid. ’)
assigned_to_system ; SET [0 :
7]
OF partial_system_view_relationship FOR system_definition_context;
(* The system_specification specifies the System definition to which the Partial_system_view is assigned. *)
scenarios_for_system ; SET [0 ; ?] OF system_view_assignment FOR system_specification;
END_ENTITY:
(‘ A system_functional_conriguration is the mechanism for assigning a functional_reference_configuration to a context_
function_relationship.
382