5.4. Context Categories¶
By default, MQC expects each measure configured in the quality model (see Default Values) to be provided for each artifact defined in the project structure configuration (see Artifact Structures) respectively for each imported artifact if no project structure has been applied so far.
Expected data that is not imported for a certain artifact for a certain revision is stated as “missing” to inform the user about e.g. not yet completed tasks.
However, this may produce lots of missing data, especially for the case that some measures may never be provided for a particular artifact.
By using context categories you can define artifact-relevant data, thus configure, which measures (data sources, measurements, and base measures) are expected for an artifact. In that way, data previously stated as “missing” - and probably resulting in bad quality - is treated as “excluded” data. This means it is ignored in availability and quality calculation.
For details about how to define context categories and how to assign context categories to artifacts see Context Categories.
Context categories will NOT automatically be applied to an MQC project after loading proper project structure and quality model. Per default the usage of context categories is disabled, hence, all data is expected and shown for all artifacts.
Data and quality excluded by context categories are shown as white areas in visualizations.
For details about how to switch on or off context categories see Context Categories.