ГОСТ Р 55346—2012
associated_version : SET [1 : ?] OF configuration_element_version FOR version_of;
UNIQUE
UR1:kJ;
END_ENTITY;
(’ A Configuration_element_relationship is the mechanism for relating two Configuration_element objects. The nature of
the relationship is defined by the re!ationship_type attribute. *)
ENTITY configuration_element_relationship;
(* The alternate specifies the second configuration_element in the alternate.
*)
alternate: configuration_element;
(* The base specifies the first configuration_element in the base.
*)
base: configuration_element;
(* The description specifies additional information on the description.
*)
description : OPTIONAL text_select;
(* The relationshipjype specifies the semantics of the Configuration_element_relationship. Where applicable one
of the following values shall be used: <ul> <li>alternative: the base and alternate Configuration_element objects are
interchangeable:</li> <li>variant; the alternate is a variant of the base Configuration_element.<li> </ul> <note>A variant
implies that the base and alternative Configurationelement objects share substantial amount of information.</note> *)
relationship_type: label:
END_ENTITY:
(*A Configuration_element_version is a snapshot of any design item for which a change history is maintained. <note
number=T>A change history is kept from an initial item release and is recorded by configuration_eIement_version.
Therefore, the picture is composed of a Configuration_element and a set of Configuration_element_version objects that
record the evolution of the given Configuration element. In this PAS. design elements can come from the requirement
UoF. function UoF, behaviour UoF, documentation and data type.<p>This then leads to a situation where a design is
made up of Configuration_element instances referring to a particular version of the Configuration_element represented.
Therefore, a design can be made up of a set of Configuration_element standing in different version. Then a new version
of the whole design can be made of a single change in the design.</p></note><example number="3">For instance,
design version 1 may comprise version 1of function 1, version 3 of function 2. and versionl of function 3. Then the next
design release (version 2) may comprise version 2 of function 1. version 3 of function 2. and version 1of function 3. This
example illustrates that there may be 2 levels of version management. One party might wish to manage the whole design
version. Another party might wish to manage versions of single items.</example><note number="2*>The standard
assumes that consistency is maintained by either the sending tool, the receiving tool or a third party tool more focussed
on the configuration management items.</note> <note number="3“>The set of configuration_element_version objects of
a Configuration_element represents the history of a Configuration_element within a particular life-cycle stage or possibly
over the whole lrfe-cyde.</note> ’)
ENTITY configuration_element_version;
(* The description specifies additional textual information on the Configuration_element_version. *)
description : OPTIONAL text_select;
(* The id specifies the identifier of the Configuration_element_version. *)
id :elementjdentifier.
(* The version_of specifies the Configuration_element object for which the Configuration_element represents a version.
’)
version_of: configuration_element;
UNIQUE
UR1:id;
END_ENT!TY:
(*A Configuration_element_version_relationship is the relationship between two Configuration_element_version objects
establishing the version graph for the objects. *)
ENTITY configuration_element_version_re!ationship;
(* The description specifies the nature of the change between the related_version and the relating_version. *)
description : OPTIONAL text_select;
(* The related_version specifies the resulting Configuration_element_version object related by the Configuration_ele-
ment_version_relationship. *)
related_version : configurafion_element_version;
(* The related_version specifies the initial Configuration_element_version related by the Configuration_element_ver-
sion_relationship. *)
324