ГОСТ Р 55346—2012
the relating objects:</li> <!i>precedence: The related Partial_system_vie\v object describe a view of the system which
preceedes the relating view of the system.</li></ul> *)
relationship_type: label;
(* The system_definition_context specifies the System_definition object for which the Partial_system_view is valid. ’ )
system_definition_context: system_definition;
WHERE
correct_relationship; related ;<>: relating;
END_ENTITY;
(*A persistent_storage is a type of General_functionality_instance which allows for persistent storage of discrete Datajn-
stance objects. <note number=’1">Persistent storage should not be confused with continuous storage - such as a water
tank. The latter is a function in itsown right and shall be represented by a General_function_definition object defining the
functional characteristics of the tank.<.’note> <note number=’2">Data_instance objects are used to represent what is stored
no matter what the persistent_storage is designed to store. The interface to persistent_storage isdefined byActual_io_port
objects. What is actually stored inthe persistent_storage is defined by the data associated with the port.</note> ’)
ENTITY persislent_storage
SUBTYPE OF (general_functkjnality_instance);
(* The id specifies the identifier of the Persistent_storage. *)
id; elementjdentifier.
(* The name specifies the word, or set of words, that are used to refer to the Persistent_storage. *)
name; label;
(* The permanent specifies whether the storage is permanent or volatile. <note number=’3*>Volatility in this context is
application dependent. The purpose of this attribute is to define whether the information stored is available after some
kind of “restart" or ’reset" of the system.</note> *)
permanent: LOGICAL;
(* The presentationjd specifies the identity information for a Persistent_storage that shall be presented to the user. *)
presentatk>n_id ; OPTIONAL label;
(* The read_onty specifies whether it is possible to write to the Store or not. <note number="4’>How a read only store
gets values is not specified in the standard but left to the design tools using this feature. It is possible that a store could
have different values for read_onfy in different operating modes (i.e.. operational data may be loaded during ground
warm up but is read only during flight).</note> •)
readonly: LOGICAL;
(* The storage_access specifies how the elements in the Persistent_storage are accessed. Where applicable one of the
following values shall be used:<ul><li>queue: First in - first out semantics app!ies;</li> <li>stack: Last in - first out seman
tics applies;<ili> <li>random_access: The access semantics is not constrained;</li> <li>olher: The access semantics is
not specified.</li> <ful> ’)
storage_access: label:
(* The store_size spedfies the upper bound of elements that can be held in the Persistent_storage.’)
store_size : OPTIONAL INTEGER;
UNIQUE
UR1:kJ;
END_ENTITY:
(*A Persistent_storage_equivalence_relationship is the relationship between two Persistent_storage objects to indicate
that the two objects are representations of the same storage object. <note>The purpose of the persistent_storage_equiv-
alence_relationship is to indicate that two storage objects are referencing the same storage facility. This is because we
can see a hierarchy of functions, but the storage mechanism is generally flat.</note> ’)
ENTITY persistent_storage_equivalence_relationship;
(* The equivalent_storage specifies the setof persistent_storage_reference objectswhich shaB be treated as referenc
es to the same storage in the scope of a functional_reference_configuration. ’)
equivatent_storage : SET [2 : ?] OF persistent_storage_reference;
(* The vafid_context specifies the System_view for which the equivalence relationship is valid. *)
valid_context: functional_reference_configuration:
END_ENTITY;
(*A Persistent_storage_reference is a type of Functionality_instance_reference that provides the mechanism for unam
biguous reference to a persistent_storage object.’)
ENTITY persistent_storage_reference
SUBTYPE OF (functionalityJnstance_reference);
SELF\functionalityJnstance_reference.referenced_functionality_instance: persistent storage;
END_ENTITY;
366