ГОСТ Р 55346—2012
id :elementjdentifier.
(* The initial_value specifies the actual value of the initial_value.
*)
initial_value : text_select;
(* The name specifies the word, or set of words, by which the name is referred. The name is reffered to as the tag.
*>
name: label;
END_ENTITY;
(*An oo_use_case specifies a sequence of actions that a system or other entity can perform, interacting with Oo_actor
objects of the system.
*)
ENTITY oo_use_case:
(* The description specifies additional information about the Oo_use_case. *)
description : OPTIONAL text_select;
(* The id specifies the identifier of the Oo_use_case. *)
id :elementjdentifier
(* The name specifies the word, or set of words.that are used to refer to the Oo_use_case. *)
name: label;
(* The namespace specifies the element to which the Oo_use_case belongs. The names of elements belonging to the
same namespace element must be unique within this set. *)
namespace; OPTIONAL oo_namespace_select:
END_ENTITY;
(*An Oo_view is a graphical representation of a collection of model_elements. *)
ENTITY oo_view
SUBTYPE OF (oo„package);
(* The viewjype specifies the type of the Oo_view. Where applicable the following values should be used:<ul><li>activ-
ity: The Oo_view represents a state machine where ail or most of the states are Oo_action_state objects and all or most
of the transitions are Oo_ac!ion_stateJransition objects:</li> <li>coltaboration: The Oo_view represents interactions and
links between a collection of objects:</li> <li>component: The Oo_view represents the organizations and dependencies
among Oo_component objects;</li> <li>dep!oyment: The Oo_view represents the run-time configuration of PhysicalJn-
stance objects and the Oo_component objects executing on them;</li> <li>sequence: The Oo_view represents an inter
action of a collection of objects in a time sequence;</li> <li>statechart: The Oo_view represents a state machine;<fli>
<li>static structure: The Oo_view represents a collection of declarative (static) objects:</li> <li>use case; The Oo_view
shows the relationships among Oo_actor objects and Oo_use_case objects within a system.</li></ul> *)
viewjype : label;
END_ENTfTY:
(*An Oo_view_context_element_relationship specifies the allocation of an object to a Oo_view. *)
ENTITY oo_view_context_element_relationship:
(* The represented_model_element specifies the object to be mapped. *)
represented_model_element: oo_extended_model_element_select;
(* The view specifies the Oo_view that the model_element is allocated to.
*)
view: oo_view:
END_ENTITY:
(*An Oo_view_relationship is a relationship between two Oo_view objects. *)
ENTITY oo_view_relationship:
(* The base specifies the relating Oo_view object.’)
base: ooj/iew;
(* The description specifies additional information about the Oo_view_relationship.
*)
description : text_select;
(* The reference_view specifies the related Oo_view object.’)
referenoe_view:oo_view;
(* The relationshipJype specifies the type of the Oo_view_relationship. <example number="15*>An Oo_view of the
view_type sequence can be a specialization of another Oo_view of the viewjype use case. For this example the type
would be given the value specialization.</example> *)
relationship Jype: label:
END_ENT1TY:
362