Page tree
Skip to end of metadata
Go to start of metadata

This documentation is no longer maintained and may contain obsolete information.

Page frame name:


This view is designed to deliver the information about the modules under the responsibility of the entity you are looking at (i.e., a node of the Organization tree - Organization, Team, Developer etc.) necessary to check their overall quality status, the trends of their overall quality, their latest status regarding each one of the Health Factors and the evolution of violations to Quality Rule-based metrics whose "critical contribution" option has been set:

It displays information that is similar to the Assessment - Portfolio Level.

This view requires access to at least one node of the Organization tree (if one was uploaded) - see the Dashboard administration, specifically in Background Facts and Business Value Metric upload for more information.


Left hand panel

Please see the section Left hand panel in Using the CAST Engineering Dashboard for more information about this.

Main window panels

Ensure that you select the entity (organization, team, developer) you require using the drop down selector in the top left hand corner.

Four main panels are available:

Current Overall StatusMapping of applications from the selected entity (organization, team, developer) according to their TQI (Technical Quality Index) on the horizontal axis, their Technical Debt per kLOC (please see the section Left hand panel in Using the CAST Engineering Dashboard for more information about Technical Debt) on the vertical axis, and their functional weight as the bubble size. Hyperlinks within the list of Applications lead to the Assessment - Application Level (for the Application) and to the Investigation - Quality Model Drilldown for the kLOC. This panel is designed to help identify abnormal situations (e.g.: mission-critical applications with poor TQI).
Portfolio HistoryDisplays the evolution (over successive snapshots) of the TQI (Technical Quality Index) of the selected entity (organization, team, developer) as lines, against the volume (counted as kLOCs) of the selected entity (organization, team, developer). It helps detect trends in overall quality and can also help detect the impact of a large addition/deletion of code on quality.
Bottom two panelsSolely relying on high level indicators to control the health of applications is not enough. Software development is also a question of details and a single violation of a critical performance rule can have severe impacts when occurring in production. An aggregated model can only offer what it is meant for: an effective summary of the quality. But due to the very volume of information they summarize, they fail to visualize the elementary evolutions that can jeopardize the application behavior. Therefore, besides the aggregated quality model, there is a need for a solution to monitor a few number of critical rules and be sure that no (or little) violations to these rules occurs. Hence the following two panels:
    • Critical Violations by Module (exception approach) - displays the number of violations (i.e., defects for rules that have been tagged "critical contribution" in the Assessment Model) split per module of the selected entity (organization, team, developer), and per Health Factor. Hyperlinks lead to the Risk Indicators - Object Level listing the defects. Added and removed tables help identify the number of violations that have been added or removed since the previous snapshot.
    • Health Factors by Module (systemic approach) - displays the Health Factor grades for each module of the selected entity (organization, team, developer), including the SEI Maintainability index). The grade evolution table highlights (with a color-coded value) the evolution since the previous snapshot.
  • No labels