ГОСТ Р 55346—2012
(*An oo_view_system_view_relationship is a relationship between an Oo_view and a System_view.
*)
ENTITY oo_view_system_view_retationship;
(* The co_view specifies the Oo view object for that the system_context is being defined.
*)
oo_view : oo_view;
(* The system_context specifies the System_view object that defines a context for the oo_view.
*)
system_context: system_view:
END_ENTITY:
(*An organization is a group of people involved in a particular business process. <note number=T>This is the AP 214
definition.</note> *)
ENTITY organization:
(* The delivery_address specifies the address where goods are delivered. *)
delivery_address: OPTIONAL address;
(* The description specifies additional information about the Organization. *)
description : OPTIONAL text_select;
(* The id specifies the identifier of the Organization. <r>otenumber=’2‘>The assignment of this attribute is usually
controlled by a registration authority. The registration authority may be a public organization that assigns identifiers to
corporations, or it may be the parent corporation that assigns component identifiers to itscomponents.</note><example
number=’16">The id may be the code assigned to the id for a stock market listing, or it may be a department number.</
example>’)
id : basicjdentifier;
(* The name specifies the word, or set of words, that is used to refer to the Organization. *)
name: label;
(* The postal_address specifies the address where letter mail is delivered. *)
postal_address : OPTIONAL address;
(* The visitor_address specifies the address where the Organization receives visitors. *)
visitor address : OPTIONAL address:
END_ENTITY:
(*An Orgamzation_relationship is used to represent an arbitrary relationship between two Organization objects. <note
number=’1*>lt also allows for the description of the respective role of an Organization in a Project (Prime contractor,
partners. sub-contractors).</note> «example number=“17’>The relationship between two Organization objects may be
"system contractor’ or "partner’.</example> *)
ENTITY organization_relationship;
(* The description specifies a textual string that captures additional information on the nature of the relationship between
the hvo Organization objects. *)
description: OPTIONAL text_select;
(* The name specifies a name that is associated with the relationship between the two Organization objects. *)
name: label;
(* The related_organization specifies the second of the two Organization objects involved in the relationship, «note
number="2*>The exact semantics of this attribute depend of the value of the description attribute.«/note> *)
related_organization : organization;
(* The relating_organization specifies the first of the two Organization objects involved in the relationship, «note num-
ber=’3">The exact semantics of this attribute depend of the value of the description attribute.«/note> *)
relating_organization ; organization;
WHERE
WR1: related_organization :<>: relating_organization;
END_ENTITY;
(*A Package is a set of data used to group objects that are related in some way. «note number=*1*>The classification
criteria is user defined.</note> «note number=“2">Package can be used to group information on any level of design
abstraction, from a small set of Requirementjnstance objects that somehow are related to the set of design information
that is the outcome of a design Eng‘meering_process_activity.</note> ’)
ENTITY package
SUPERTYPE OF (selection_package);
(* The description specifies additional information about the Package. *)
description : OPTIONAL text_select;
363