15. Validation of Configuration¶
As seen in the previous sections, such as Project Structure Configuration or Quality Model Configuration, MQC requires the user to take a couple of configuration steps to assure an correct functioning adapted to your data, trends, targets and goals. To point the user to possible configuration errors, MQC is providing the user a validation functionality to guide you through the configuration process of your project.
15.1. Validation of Artifacts¶
MQC automatically validates if the imported Artifacts match with your Artifact Structure mentioned in Figure 13.6. In case of lack of congruence, the validation dialogs will inform the user, e.g. about imported but not configured artifacts.
15.2. Validation of Measures¶
MQC will automatically validate if your imported Base Measures coincide with the ones mentioned in your Quality Model (see Base Measures and Default Values) and will give a validation dialog, e.g. about imported but not configured measures.
15.3. Validation of Context Categories¶
If you have defined Context Categories, like in the example mentioned in see Figure 14.10, MQC will notify you of imported Data Sources, Measurements or Measures, that are imported but were excluded by the user.
15.4. Validation of Report Date Times¶
In case you have imported report files with a report date time, which is outside your configured project milestones (see Project Milestone Structure), the corresponding data is not shown in any visualization and is not used for quality calculation. MQC notifies accordingly, e.g. about the file path and name of the corresponding data report.