ГОСТ Р 55346—2012
<note>
The systemjunctional_configuration defines the non-functional characteristics such as property values and allocation
information that is valid in one particular view on a system.
</note> *)
ENTITY system_functional_configuration:
(* The functional_configuration specifies the functional_reference_configuration that is assigned by the functional_con-
figuration.
’)
functk>nal_configuration: functkjnal_reference_configuration;
(* The system specifies the context_function_relationship to which the functional_reference_configuration is assigned.
*)
system : context_function_relationship:
END_ENTITY:
(*A System_instance is the instantiation of a system specification in a particular context. <note number=T>A System_
instance does not imply a realized system, only that a particular specification is planned to be used for the realization of
a system in a system composition structure.</note> <note number=*2’>Each System_instance gets its definition from
exactly one System_definition object, defined by the attribute definition.</note> *)
ENTITY systemjnstance:
(* The definition specifies the System_definition object that provides the specification for a particular definition. There is
exactly one System_definition object acting as the definition for a particular definition.
*)
definition: system_definition;
(* The description specifies additional information about the Systemjnstance. *)
description: OPTIONAL text_select:
(* The id specifies the elementidentifier of the Systemjnstance. *)
id :eiementjdentifier.
(* The name specifies the word, or set of words, that is used to refer to the Systemjnstance. *)
name: label;
UNIQUE
UR1: definition, id;
END_ENTITY;
(*A systemJnstancejelationship is a representation of an interaction relationship between two or more Systemjn
stance objects.
<note>
systemJnstance_relationship is used to capture the context of a system in an entity-relationship modelling style. The
idea is to model a set of interacting systems and the relationships between them. This means defining the cardinality
constraints between the systems involved in a relation. All objects involved in a systemjnstance_relatk>nship must
be part of the same system breakdown structure.
</note><ol><li>This is a new modelling philosophy from point of view of the model and corresponds to system context
view argued for by David Oliver.An example of a system context diagram is available on page 210 in Engineering Com
plex Systems with Models and Objects, by David Oliver. The actual relationship is formed by Systemjnstance. System_
mstance_relationship_port and systemjnstancejelationship objects.</li> ’)
ENTITY system_instance_relationship;
(* The description specifies additional information about the description.
*)
description : text_select;
(* The name specifies the word, or set of words, by which the name is referred.
*)
name: label;
INVERSE
(* The defined_relationship specifies the SystemJnstance_relationship referenced. *)
connected_port: SET [2 : ?] OF systemJnstance_relationship_port FOR defined_relationship;
END_ENTITY;
{*A System_instance_relationship_port is the mechanism for associating a Systemjnstance object to a Systemjn-
stance_relationship object. <note>The systemJnstance_relationship_port also specifies the cardinality of the Sys
temjnstance object involved in the relation.</note> <example number-’30’>ln a cellular telephone system it may be
appropriate to express that for each cell there may be in the range of 0-5000 terminals concurrently. In PAS 20542 this
is expressed by instantiating a SystemJnstance_relationship relationship between a cell systems Systemjnstance and
383