ГОСТ Р 55346—2012
(* The associated_version specifies the Configuration_element_version for the Change_report.’)
associated_version : configuration_element_version;
(* The description specifies additional information on the Change_report. *)
description : OPTIONAL text_select;
(* The name specifies the word, or words, that are used to refer to the Change_report. *)
name: label;
(* The originating_change_request specifies the Change_order that led to the creation of the Change_report.’)
originating_change_request: change_request;
END_ENTITY:
(‘ A Change_report_element_assignment is the mechanism for assigning descriptions of changes implemented toa
Change_report.’)
ENTITY change_report_element_assignment;
(* The change_report specifies the Change_report involved in the Change_report_element_assignment. *)
change_report: change_reporL
(* The change_report_element specifies an element that is part of a Change_report. *)
change_report_element: change_report_element_select:
(* The description specifies additional textual information on the Change_report_element_assignment. *)
description: OPTIONAL text_select;
END_ENTITY;
(’ A Change_request is a type of Work_request that solicits the implementation of a change. <note>The dements affect
ed by the Change_request are identified by the attribute scope inherited from the Work_order.</note> *)
ENTITY change_request
SUBTYPE OF (work_request);
(* The responsejojssue specifies the critical Jssue that led to the creation of the Change_request.’)
response_to_issue : SET [1 : ?1OF criticaljssue;
END_ENTITY;
(*A Clock is a device that emits a control signal at regular intervals. <note number="1">Aclock can define the synchro
nous behaviour of one or more Functionjnstance objects.</note> <note number="2">The subclass of systems engineer
ing toots supporting synchronous behaviour use different methods to represent the clock that provides the synchronous
activations. Some represent the clock explicitly as a kind of function, some represent it as a property of the function that
is controlled by the clock. The approach taken in PAS 20542 supports both variants in the sense that the Clock can be
presented as a function-like block or be a viewed as a property of the function it controls.</note> ’)
ENTITY clock;
(* The control_signal specifies the Datajnstance (whose definition shall be of type Event_data_type_definition) that the
Clock produces at periodic intervals (given by the frequency attribute). *)
control_s»gnal: datajnstance;
(* The description specifies additional information about the Clock. ’)
description: OPTIONAL text_select;
(* The frequency specifies the number of pulses emitted during a given time period. *)
frequency : REAL;
(* The name specifies the word, or words, that are used to refer to the Clock. *)
name : OPTIONAL label;
WHERE
correct_data_definition:
SYSTEMS_ENGINEERING_DATA_REPRESENTATION.EVENT_DATA_TYPE_DEFINITION‘ INTYPEOF(control_sig-
nal.defmition);
END_ENTITY;
(*A Clock_assignment_relationship is a relationship between a Clock and a Controljo_port such that the periodic signal
from the Clock is conveyed to the ControlJo_porL <note>The Clock_assignment_relationship allows the use of a single
Clock to control several function objects (via the corresponding ControlJo_port objects).</note> *)
ENTITY ciockassignmentrelationship;
(* The clock specifies the Clock object in the relationship.
*)
clock: clock;
(* The trigger_for specifies the Control_io_port object in the relationship.
*)
triggerjor: control_io_port;
END_ENTITY;
322