...
A rationale has to be given in order to justify the use of the out-of-scope declaration and the declaration that no semantic correspondence has been established. This requirement ensures that the use of these options is verifiable.
Out-of-scope declaration
The specification contains examples of rationales for an out-of-scope declaration. Although these were developed in SESAR they are still widely applicable.
Tip | ||
---|---|---|
| ||
The list of rationales to use for an out-of-scope declaration is:
|
Tip | ||
---|---|---|
| ||
The option to use out-of-scope or change request may not be obvious. In this case, the best practice is to use the change request option. This will allow the AIRM change control board to consider the input and whether the AIRM's scope needs to be changed. |
No semantic correspondence declaration
The use of the declaration that no semantic correspondence has been established must also be justified. The specification gives the example that it allows the mapping exercise to be done in an iterative way. Other obvious examples are when a problem in the information definition means that no mapping is obvious. It is, of course, hoped that the problem can be fixed but in many cases this is not always an easy process.
...