With this setting a dedicated name can be defined for the MQC project. If left
empty, the name “Default Project” is applied.
Project time frame
Define start date and end date of the project.
This setting is used to control the data to be shown for a project respectively
the amount of data to be imported via API connectors.
Data with a report date outside the configured project time frame is ignored.
Configured milestones with a due date after the project end date are not
visible.
If no start and end date is configured, all available data will be imported
from a data location.
This setting defines the degree of compactions of the revisions for which data exists to better visualize your
trend visualizations. The revision granularity can be selected depending on your needs.
Figure 4.31 The default revision granularity is Days, but it might be useful
to change it to CalendarWeeks or Months¶
If an MQC project is shared between areas with different locales,
the calendar locale, which was initially determined during the creation
of the project, is kept. This allows a consistent view on data and quality.
Per default the usage of Context Categories is disabled, hence, all data is
expected and shown for all artifacts. To apply the context category configuration,
enable this setting.
With context categories enabled, for each artifact only expected data is shown
in all visualizations (see Figure 4.33).
All other data is excluded (white areas of the matrix). By this, you can easily
distinguish between not expected data and data that is really missing.
(see context categories in Artifacts)
Figure 4.33 Availability Heatmap showing expected data (Context Categories enabled).¶
Additionally, only expected data is used for calculating quality for an artifact.
The Diff View (see Diff View) shows the differences between revisions.
By default, this view compares each revision to its immediate previous revision. Additionally, users can select broader
comparison ranges, such as Weeks, Months, Quarters, or Years to compare each revision against the last
revision within that selected date range.
Users can select multiple diff bases. For example, enabling Months alongside Revisions.
The active diff base can be switched in the toolbar, allowing users to toggle between selected comparison modes quickly
(see Diff Base).
The Diff View (see Diff View) shows the differences between revisions.
By selecting one or more milestone structures under “Diff for milestones”, an additional comparison is created that
compares each revision to the last revision of the previous milestone of the selected structure.
The diff comparison base can be switched in the toolbar between the selected milestone structures
(see Diff Base).
MQC projects with this setting enabled and saved in the server library are
updated periodically to fetch the latest data changes.
Background server-side updates are only executed if new or changed data was detected.
This ensures that all relevant projects are always kept up to date.
See Update Projects on Server for details on how to add a job to the
“Automation Services” on the MQC Server to periodically check and update
MQC projects.
by a client-side automatic data refresh
MQC projects open in the desktop client and web player use a background monitoring to detect changes in the data
of the projects.
While this setting is disabled, the user is informed of updates by a change in the
Data Import State. The user can then update the project by clicking on the “Refresh Data” button
provided there.
While this setting is enabled, any change detected in the data results in a directly executed update of the
project in the client, while the user is interrupted in his work and has to wait until the project has been updated.
If Data Details are not disabled, they are imported by the DataSource adapters that can read findings.
(at the moment only the MXAMmxmr Adapter supports reading findings)
Disabled
Data Details are disabled.
The DataSource Adapters do not import findings.
The Data Details page and Data Details visualizations are not available.
On Demand
Data Details will not be imported by default, but can be loaded on demand later.
The Data Details visualizations show ‘Not Loaded’ findings, while the List shows
a warning message, if data details have not been imported.
By clicking on the Imported data details button, the data details
to be imported can be configured with the combination of artifacts, datasources
and revisions.
By default, MQC monitors all configured data locations for changes. The interval
for the checks is set to 10 seconds. The next interval only starts after the
current check has been completed.
Figure 4.36 Enable/disable the monitoring of the Data Locations and change the monitoring
interval¶
If a change in a data location is detected, either the user is notified about
the change or an automatic update of the imported data is triggered (see
client-side automatic data refresh in Keep the project up to date).
To disable the monitoring, deselect the option.
Apart from that, the monitoring interval can also be adjusted. This is
particularly useful if several data locations with large amounts of data contained
are configured, where a check for updates would take longer than the configured
interval.
