ГОСТ Р 55346—2012
SUBTYPE OF (workjequest);
(* The requestjype specifies the nature of the Start_request. Where applicable, one of the following values
shall be used:<ul><li>cost_reduction: A request aimed at reducing the engineering and manufacturing costs of an
item;</li> <li>customer_rejection: A request resulting from a rejection by a customer;</li> <li>customer_request:
A request for an activity that is necessary to solve the request of a customer</li> <li>durability_improvement: A
request aimed at extending the life time of an item;</li> <li>government_regulation: A request resulting from legal
requirements;</li> <li>procurement_alignment: A request to adjust the purchasing process of different items;</li>
<li>security_reason: A request for an activity that is necessary from a security point of view:</li> destandardiza
tion: A request to unify variants of an item;</li> <li>supplier_request: A request for an activity necessary to solve
the request of a supplier:</li> <li>technical_improvement: A request aimed at improving the technical aspects of an
item.</li> </ul> ’ )
request_type: label;
END_ENTITY:
(*A State_context_retationship is a mechanism for relating a Fsm_generic_state to a Functional_state_context indicating
that the Fsm_state is a top-level state in the Functional_state_context. <note>This entity provides the link between a
Fsm_state (top-level state if a statechart) and the environment in which a finite state machine exists.</note> *)
ENTITY state_context_re4ationship;
(* The in_context specifies the Fur»ctional_state_context in the relationship. *)
in_context:generic_state_context:
(* The state specifies the Fsm_generic_state in the relationship. *)
state: fsm_generic_state;
END_ENTITY:
(•A State_function_interaction_port is an element of the interface to a Functional_state_context. <note>The Statejunc-
tion_interaction_port is a means for importing knowledge of functions outside a Functional_state_context into a Function-
al_state_context. Explicit import of such knowledge is required as the Functional_state_context maintains it own name
space.</note> *)
ENTITY stateJunctionJnteraction_port;
(* The port_of specifies the Functional_state_context interface of which the State_function_interaction_port is part. *)
port_of: functional_state_context;
END_ENTITY:
(*A State_machine_functional_behaviour_model is a type of Functional_behaviour_model with the discriminator dynamic
behaviour is captured using finite state machine and related formalisms. *)
ENTITY state_machine_functional_behaviour_model
SUBTYPE OF (functional_behaviour_model);
INVERSE
(* The behaviour_model specifies the State_machine_functionai_behaviour_model object for which the Fsm_model
provides the behaviour specification. *)
behaviour_constraint: SET [1 : ?] OF fsm_model FOR behaviour model;
END_ENTITY:
(*A state_transition_specification_assignment is an assignment of a textual specification to a Fsm_state_transition.
<note
number=*T‘>
The state_transition_specification_assignment is the mechanism for assigning a guarding expression to a Fsm_state_
transition in a Moore style finite state machine or the assignment of a guarding expression and a setof action statements
to a Fsm_state_transition in a Mealy style finite state machine.
dnotexnote
number=‘2’>
The language of the assigned specification is not prescribed byAP 233.
</note> *)
ENTITY state_transition_specification_assignment;
(* The assignedjo specifies the Fsm_state_transition to which the textual specification is assigned.
*)
assignedjo: fsm_stateJransition;
(* The specification specifies the textual specification assigned to the Fsm_stateJransition.
*)
specification: textua!_specification;
END_ENTITY:
381