曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
Floating-point ‘-‘?[0-9]+\.[0-9]+(e(‘-‘|’+’)?[0-9]+)?
Character chains \".*\"
4.2 File importation
AADL is not capable of file inclusion. This point is covered in COTRE using the IMPORT
instruction:
IMPORT "<fichier>";
<fichier> being an absolute or relative path (& expressed in this case based on the
location of the file containing the instruction).
4.3 Data typing
Data are typed using the specific appendix cotre.type.
4.3.1 Recognised types
The following types are recognised:
Nom Description
BOOLEAN Boolean type which can take the values TRUE or FALSE
DATA <id> DATA component in the AADL sense.
ARRAY <exp1>..<exp2> OF <type> Table with issues ranging from exp1 to exp2 & with elements
expressed as <type>.
REAL [<exp1>..<exp2>]
[UNITS (<unit1>, <uniti> => <unitj> *
<mult>…)]
Real type. May be limited to the interval [<exp1> ;<exp2>],
and/or may be associated with units (<unit1>)/subunits(<
uniti>)
INTEGER [<exp1>..<exp2>]
[UNITS (<unit1>, <uniti> => <unitj> *
<mult>…)]
Whole type. May be limited to the interval [<exp1> ;<exp2>],
and/or may be associated with units (<unit1>)/sub-units
(<uniti>)
Examples: REAL 0..+INFINITY
INTEGER 10..20
INTEGER UNITS (s, ms => s * 0.001, us => ms * 0.001)
ARRAY 0..10 OF BOOLEAN
ã AIRBUS France / IRIT / LAAS / ONERA/CT-DTIM / GET-Ecole Nationale Supérieure des Télécommunications de Bretagne / TNI-Valiosys - 2004
F241-2 Page 10/45
4.3.2 Simple data
Simple data is typed as follows:
DATA IMPLEMENTATION int.s32
ANNEX cotre.type IS
<type>;
END ANNEX cotre.type;
END int.s32;
4.3.3 Structured data
Structured data are defined as follows:
DATA IMPLEMENTATION int.sub
ANNEX cotre.type IS
<champ 1> : <type 1>;
<champ 2> : <type 2>;
<champ 3> : <type 3>;
END ANNEX cotre.type;
END int.sub;
4.4 Behavior description
The behavior of objects is described in the appendix cotre.behavior, which is broken
down as follows:
ANNEX cotre.behavior IS
<section variables>
<section initialisations>
<comportement global>|<comportement opération>+
END ANNEX cotre.behavior;
4.4.1 Overall behavior description
In this case, the description takes the form:
…
STATES
<déclaration des états>
TRANSITIONS
<définition des transitions>
EXCEPTIONS
<définition des exceptions>
…
All the components that have behavoirs can be described in this way. It is the only possible
description for threads.
ã AIRBUS France / IRIT / LAAS / ONERA/CT-DTIM / GET-Ecole Nationale Supérieure des Télécommunications de Bretagne / TNI-Valiosys - 2004
F241-2 Page 11/45
4.4.2 Behavior description operation by operation
…
SUBPROGRAM <nom opération>
VARS
<déclaration des variables locales>
INITS
<initialisation des variables locales>
STATES
<déclaration des états>
TRANSITIONS
<définition des transitions>
EXCEPTIONS
<définition des exceptions>
…
Local variables cannot of course be listed outside of the operation’s behavior description,
and can only be local variables.
The call constraints between the operations are described at object level using the
boolean property cotre : :protected defined in the standard file std.cotre. When this
property is true, the operations are mutually exclusive; when it is absent or false, the
operations can be performed concurrently.
Operation reentrance is defined at the level of the operation in question by the property
cotre : :reentrant, which may take the values true or false.
4.4.3 Condition & synchronisation
In COTRE, conditions are expressed as follows:
WHEN <condition booléenne> => <événement de synchronisation>
The recognised synchronisation events are:
Event Comments
<nom opération> ! [(<paramètres>)] Call up of the named operation with possible parameters.
The name of the operation is specified using
the objet.opération notion (with point). The
parameters are separated by commas.
CALLED ? The operation corresponding to the behavior description
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
航空资料4(117)
