曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
is called up.
RESUME [(<paramètres>)] The caller regains control (but the operation continues).
SEND <identifiant port> [(<paramètres>)] Message sent on the port indicated.
RECEIVE <identifiant port> [(<paramètres>)] Message received on the port indicated.
4.4.4 Actions
The actions performed when a transition or exception is fired are noted as shown below:
{ <action> ( ; <action>)+ }
ã AIRBUS France / IRIT / LAAS / ONERA/CT-DTIM / GET-Ecole Nationale Supérieure des Télécommunications de Bretagne / TNI-Valiosys - 2004
F241-2 Page 12/45
The possible actions are:
Action Comment
COMPUTATION(<durée max ou intervalle>)
Consumes a CPU time lower than <durée max> or
between the limits of the <intervalle>.
DELAY(<durée max ou intervalle>) Places the object in a pending state for less than the “durée
max” (max. duration) or for a length of time between the
limits of the interval.
PERIODIC_WAIT In the case of a periodic thread, ensures it is blocked until
the start of the following period. Equivalent of SKIP in the
opposite case.
STOP The thread is stopped.
SKIP No action.
<l_exp> := <exp> Modifies the value of a variable.
4.4.5 Definition & initialisation of variables
Internal variables can be of any type supported by the typing extension COTRE (section
4.3.1). The definition takes the form:
ANNEX cotre.behavior IS
VARS
<variable> : <type>;
…
INITS
<variable> := <valeur d’initialisation>;
…
4.4.6 Behavioral automaton
The automaton enables us to describe the different processing stages for objects and
operations. The model used is that of Mealy machines, and the firing conditions and actions
are carried by the transitions only. The states, including the initial state, must be
declared prior to their use.
STATES
<nom état>(, <nom état>)* : STATE;
<nom état> : INITIAL STATE;
TRANSITIONS
<transition 1>;
<transition 2>;
…
<transition n>;
The transitions take the form:
(<label>:)* <état départ> -[ <franchissement> ]-> <état arrivée> { <actions> };
<label> Transition identifier
<franchissement> Condition to be satisfied in order to activate the transition
<état départ> Initial state of the transition
<état d’arrivée> State reached once the transition has been fired.
<actions> Actions to be performed when the transition is fired.
ã AIRBUS France / IRIT / LAAS / ONERA/CT-DTIM / GET-Ecole Nationale Supérieure des Télécommunications de Bretagne / TNI-Valiosys - 2004
F241-2 Page 13/45
4.4.7 Exceptions
Exceptions enable us to describe specific behaviors such as time-outs, error detection
reactions or, more generally, every process involving general monitoring of the behavior
of an executable entity and an interruptive reaction. Exceptions are defined according
to the format below:
EXCEPTIONS
<sensibilisation> -[ <franchissement> BEFORE <désensibilisation> ]->
<état d’arrivée> { <actions> };
…
<sensibilisation> Condition to be satisfied in order for an exception to be
“sensitized”
<franchissement> Condition to be satisfied in order to activate the exception
when it is “sensitized”
<désensibilisation> Condition to be satisfied in order to “desensitize” the exception
<état d’arrivée> State reached once the exception has been fired. The
‘=’ symbol gives the option not to modify the current
state.
<actions> Actions to be performed when the exception is fired.
4.4.8 Examples of behavoral sections
Behavioral description operation by operation:
ANNEX cotre.behavior IS
VARS
tokens : INTEGER 0..+infinity;
INITS
tokens := 1;
SUBPROGRAM wait
STATES
s0, s1 : STATE;
s0 : INITIAL STATE;
TRANSITIONS
s0 -[ WHEN tokens > 0 => CALLED ? ]-> s1 { tokens := tokens - 1 };
s1 -[ RESUME ]-> s0;
EXCEPTIONS
CALLED ? -[ TIMEOUT(300ms) BEFORE WHEN STATE(s1) ]-> s1 { computation(1ms,
2ms) };
SUBPROGRAM release
STATES
s0, s1 : STATE;
s0 : INITIAL STATE;
TRANSITIONS
s0 -[ WHEN tokens < capacity => CALLED ? ]-> s1 { tokens := tokens + 1 };
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料4(118)
