Checking MDA elements

 

Overview

All MDA elements can be checked, in order to verify that they have been modeled correctly. This check is automatically carried out before an MDA component is compiled. Compilation is only run if no errors have been encountered in the MDA component's composition.

 

By clicking on the  icon, you can launch a check on the selected element. This button is accessible in the “MDA” tab of the auxiliary window.

 

 

Checking without errors

If the check run on the element detects no errors, then no warning or information messages are shown, and the following window appears.

 

Figure 79. Information box appearing after checking an MDA element containing no errors

 

 

Checking with errors

 

Figure 80. Report box appearing after checking an MDA element containing errors

 

Key:

1.      List of error messages, warning messages and information messages. By double-clicking on a message, the element concerned is automatically selected in the model explorer.

2.      Complementary information on the message selected in zone 1. This message helps you resolve the problem more easily.

3.      Icon used to access the on-line help related to the message selected in zone 1. By clicking on this icon, you can directly access the on-line help, which will help you quickly resolve the problem. If the icon is grayed out, this means that no on-line help is available for this message.

4.      Button used to save all the messages in a file.

 

 

Saving the contents of the report box

By clicking on the “Save as...” button, you can save all the messages appearing in the report box. In this case, a window opens, allowing you to select the file in which the messages are to be saved.

 

For each message, this file contains:

·         its type: error, warning or information

·         the element concerned

·         the message displayed in zone 1

·         the complementary information displayed in zone 2

·         the HTML file used to access the on-line help corresponding to the error

 

For example:

Error on "Instance::CheckConsistency.Commands.op1"

"op1 " : the signature of the operation invoked by the command is incorrect.

 

To be invoked by a command, an operation has to be:

- public,

- without parameters (either in/out or return parameter).

For further information, please refer to "D:\Softeam\Objecteering6/help/mda_modeler/mda_components/creating_commands.htm".