ГОСТ Р 55346—2012
cellular telephone system Systemjnstance with SystemJnstance_relatk>nship_port objects capturing the cardinality in
formation for each system in the relationship. <p>For the example the system_instance_relatk>nship_port for the cellular
telephone system systemjnstance the cardinality figure would be the interval 0-5000.</p> </example> *)
ENTITY system_instance_relationship_port;
(* The cardinality specifies the range of Systemjnstance objects that are involved in the relation. Regardless of the car
dinality specified, exactly one Systemjnstance object is always specified by the port_of attribute.<p>Cardinality defines
the number of Systemjnstance objects that are involved in the System_instance_relationship defined by the defined.re-
lationship attribute.</p> *)
cardinality: cardinality_association_select;
(* The defined_relationship specifies the SystemJnstance_relationship referenced. *)
defined_relationship : system.instance.relationship;
(* The port_of specifies the Systemjnstance referenced. *)
port_of: systemjnstance;
END_ENTITY:
(*A SystemJnstance_replication_relationship is the relation between two Systemjnstance objects where a new Sys
temjnstance object replaces the original one in a system. <note>The entity does not adequately capture the require
ment. Additional work is required.</note> *)
ENTITY system.instance.replication.relationship;
(* The rationale specifies the motivation for replacing the Systemjnstance.’)
rationale ; OPTIONAL text_select;
(* The replaced_application specifies the original Systemjnstance. *)
replaced_application ; systemjnstance;
(* The relacing application specifies the replaced Systemjnstance.’)
replacing_application; systemjnstance;
END_ENTITY:
{*A System_physical_configuration is the mechanism for assigning a Physical_reference_configuration to a Context,
physical.relationship. *)
ENTITY system_physical_configuration;
(* The physical.configuration specifies the Physical_reference_configuration that is assigned by the System.physi-
cal.configuration. *)
physical.configuration: physical.reference.configuration;
(* The system specifies the Context jihysical.relationship to which the Physical_reference_configuration is assigned. *)
system ; context_physical_relationship;
END.ENTITY;
(*A System_substitution_relationship is a relationship that indicates that one System_composition_re!ationship may be
substituted for another System.composifion.relationship. The subjects of the substitution are the related component,
system Systemjnstance objects of both System.composition.relationship objects. The decomposed.system System,
definition shall be the same in both System.composition.relationship objects. *)
ENTITY system.substitution.relationship;
(* The base specifies the System.composition.relationship that is replaceable. *}
base ; system.composition.relationship;
(* The description specifies textual additional information on the System.substitution.relationship.’)
description : OPTIONAL text.select;
(* The substitute specifies the system.composition.relationship that may be used instead of the base System.compo-
sition.relationship.’)
substitute; system.composition.relationship;
END.ENTITY;
(*A System.view is a partial or complete view on a system under specification. <note number=’V>A System.view is a
collector for all information that is of interest for a system specification.<>’note> <note number=H2">System_view captures
the concept of a particular perspective to the system model, as if viewed from a specific stakeholder. It also provides all
system related entities with basic capabilities such as version management, persistent Ids, names etc.</note> *)
ENTITY system.view
ABSTRACT SUPERTYPE OF (ONEOF(partial_system_view. system.definition));
(* The associated.version specifies the Configuration.element object for which the Configuration.element.version
object represents a version. •)
associated.version; configuration.element.version;
(* The description specifies additional textual information about the System.view. *)
384