ГОСТ Р 55346—2012
description : OPTIONAL text_select;
(* The id specifies the identifier of the System_view. *)
id :elementjdentifier.
(* The name specifies the word, or set of words, that is used to refer to the System_view. *)
name: label;
INVERSE
(* The associated_context specifies the System_view that is valid for the relationship. *)
system ; SET [0 ; ?] OF context_function_relationship FOR associated_context;
UNIQUE
UR1: id;
WHERE
WR1; at_most_one_system_function_assigned(SELF);
END_ENTITY;
(*A System_view_assignment is the assignment of a ParUal_system_view to a System_definition. <note>The Partial_
system_view assigned to the System_definition represents a part of the complete system specification.</note> *)
ENTITY system_view_assignment;
(* The assigned_view specifies the assigned Partial_system_view. *)
assigned_view; partial_system_view;
(* The assignment_comment specifies additional textual information about the assignment. *)
assignment_comment; OPTIONAL text_select;
(* The system_specification specifies the System_definition to which the Partial_system_view is assigned. ’)
system_specification : system_definition;
END_ENTITY;
(*A System_view_context is a description of the fidelity and system viewpoint for a Partial_system_view. <note>The
System_view_context carries a number of attributes that would be more efficient if they could be assigned individually.</
note> ’)
ENTITY system_view_context;
(* The description specifies additional textual information about the System_view_context. *)
description : OPTIONAL text_select;
(* The fidelity specifies a classification of the level of specification detail the partial_system_view that references the
fidelity, «example number=*31">The value for fidelity may be “user* to indicate that the associated partial_system_view
defines a systems specification at user level of detail.</example> *)
fidelity: label;
(* The system_viewpoint specifies the particular viewpoint that is valid for the System_view_context. «example num-
ber=*32*>The system_viewpoint might be *maintained indicating that a Partial_system_view referencing the sys-
tem_viewpoint provides specifications that are valid from a maintainer’s point of view.«/example> The system_viewpoint
may also be used to indicate that specifications of the referencing Partial_system_view are relevant for a very specific
domain, «example number="33">The system_viewpoint may be *temporal_safety_analysis* indicating that a partial_sys-
tem_view object referencing the systemviewpoint provides a sub-set of system specifications that defines the temporal
requirements of the system under specification </example> *)
system_viewpoint; label:
END_ENT!TY;
(*A Textual_paragraph is a structured representation of text, «note number=*1*>The name shall probably be change to
reflect the fact that the entity does not provide a template only but also textual information.«/note> *)
ENTITY textual_paragraph:
(* The element value specifies the textual component of the Textual_paragraph. *)
element_value : LIST (1 : ?] OF text_elements:
(* The name specifies the word, or set of words, that is used to refer to the Textual_paragraph. «note number=“2“>The
name attribute may be a reference to formatting information for the text.«/note> *)
name: label;
END_ENTITY;
(*ATextual_requirement_defmition is a type of Requirement_definition and a definition of a requirement expressed in
text. <note>This is the most ‘primitive’ representation of requirements in PAS 20542.«/note> *)
ENTITY textual_requirement_definition
SUBTYPE OF {requirement_definition):
(* The description specifies the required capabilities. *)
description: text_select;
END_ENT!TY:
385