This section provides a detailed description of the Validation view. The Validation view provides a list of errors that currently exist in any of the components you have defined.
The errors that are flagged in the Validation view are errors that will prevent the CAST Management Studio from carrying out tasks correctly.
Some example validation errors are as follows:
- Missing Application Root Path > This indicates that an analysis option is missing from an Analysis Unit
- Missing Dashboard Services > This indicates that an Application does not have any Dashboard Services associated to it
- Missing Analysis Services > This indicates that an Application does not have any Analysis Services associated to it
- Missing Applications > This indicates that a System does not yet have any Applications
In general, errors flagged in the Validation view indicate fields in an editor that remain empty when they should not.
|Path||Shows the location of the error - i.e. the editor in which the error can be corrected. Take the following example: |
This error is located as follows:
Application (MEUDON) > Source Code Package as defined in the CAST Delivery Manager Tool (VB_CASTPUBS) > Analysis Unit (new J2EE Analysis Unit)
You may find that names are repeated in the path if the source code package or the Analysis Unit are named the same as Technology (for example "J2EE").
|Error||Indicates the error|
Auto error validation
The Validation view is self-updating and will display a new error as soon as you have finished editing a field in an editor. It will also automatically remove errors when they are corrected.
If you see an error displayed in the Validation view, you simply need to double click it to correct it. This will open the editor in which the error is located, allowing you to correct the problem. When the editor is displayed, a the field title will be highlighted in red indicating the field that is creating the error and which you need to correct (as shown below):
The Validation view is displayed by default. If you close it, you can re-display it by:
- Clicking Window > Show View menu and then choosing the Validation view in the displayed dialog box (under MDA).
Similarity to Verification view
The checks carried out automatically for the Validation view are similar to the checks carried out for the Verification view. The following differences exist:
- the checks are generally more rigorous for the Verification view and will detect errors in external configuration settings such as whether the Layers and Rules files required in the Architecture Model editor are actually valid (instead of simply whether they exist).
- in general, the results of checks for the Verification view will be slower to display than those for the Validation view because the checks are more rigorous.