- The Constraint column shows whether the component will retrieve data for an "engineering" (AED) or "analytics" domain (AAD), and whether an extension needs to be installed in order to generate results (and if we need a specific version or RestAPI).
- Due to backward compatibility, some components can have two different IDs, but the result will be the same.
- The Mode column shows whether the component is targeted at an Application or a Portfolio or an Application - the relevant option should be chosen in Report Generator (see image below). CAST recommends always selecting an Application when the target domain is "engineering" and when using Application mode, as it will avoid empty results (this is because in an "analytics" domain, violations and components does not exist for an application).
Component Id | Description | Mode | Constraints | Parameters | Configuration sample | Output | Result sample |
---|---|---|---|---|---|---|---|
ACTION_PLANS | Display the action plan summary | Application | Having populated the action plan from the Engineering Dashboard. This component is only relevant on an engineering database. It is empty on an analytics database. | None | TABLE;ACTION_PLANS | Display the number of new and old items in action plans by rules | |
ACTION_PLAN_VIOLATIONS | Display the action plan details | Application | Having populated the action plan from the Engineering Dashboard. This component is only relevant on an engineering database. It is empty on an analytics database. |
| TABLE;ACTION_PLAN_VIOLATIONS; COUNT=10,NAME=SHORT | List the violations in action plan | |
CAST_COMPLEXITY | Cast Complexity | Application | This component is only relevant on an engineering database. It is empty on an analytics database. | None | TABLE;CAST_COMPLEXITY | Evolution of the distribution of objects regarding cast complexity | |
CAST_COMPLEXITY_WITH_VIOL | Complexity with violations: Statistics about Artifacts – CAST Complexity & Violations | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
| TABLE;CAST_COMPLEXITY_WITH_VIOL | Number of artifacts and artifacts with violations by cast complexity distribution | |
CAST_DISTRIBUTION | Evolution of a specific distribution of objects | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
List of distributions :
| TABLE;CAST_DISTRIBUTION;PAR=65501 | Evolution of the distribution of objects regarding specified distribution | |
CAST_HIGH_COMPLEXITY | Evolution of high and very high categories of cast complexity | Application | This component is only relevant on an engineering database. It is empty on an analytics database. | None | TABLE;CAST_HIGH_COMPLEXITY | Evolution of high and very high complex objects regarding cast complexity | |
CAST_HIGH_DISTRIBUTION | Evolution of high and very high categories of a specific distribution | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
cf CAST_DISTRIBUTION for list of distribution | TABLE;CAST_HIGH_DISTRIBUTION | Evolution of high and very high complex objects regarding the specified distribution | |
COMPLIANCE | Compliance grades and evolution | Application | No |
| TABLE;COMPLIANCE;HEADER=SHORT | Score of compliance BC for previous and current snapshot with % variation | |
COMPLIANCE_TO_OBJ_TABLE | Compliance to objectives. This component is based on:
| Application | No |
| TABLE;COMPLIANCE_TO_OBJ_TABLE | Comparison between objectives and achievment | |
CRITERIA_GRADE | For a business criteria, List of technical criteria with grade | Application | No |
| TABLE;CRITERIA_GRADE;PAR=60017,COUNT=10 | Top technical criteria with scores and evolution for the specified BC | |
CRITICAL_VIOL_BY_APPLICATION | Critical violations in the application by health factors for current and previous snapshots | Application | No |
| TABLE;CRITICAL_VIOL_BY_APPLICATION | Health Factors number of total critical violations, added and removed | |
CRITICAL_VIOL_BY_MODULE | Critical violations in the modules by health factors for current snapshot | Application | No |
| TABLE;CRITICAL_VIOL_BY_MODULE | Health Factors number of total critical violations, added and removed for modules | |
FUNCTIONAL_WEIGHT | Functional weight information | Application | No | None | TABLE;FUNCTIONAL_WEIGHT | Values of Automated Function points (10202), Decision Points (10506) and Backfired Function Points (10201) metrics for application | |
FUNCTIONAL_WEIGHT_EVOLUTION | Functional weight evolution information | Application | No | None | TABLE;FUNCTIONAL_WEIGHT_EVOLUTION | Values of previous metrics (Automated Function points (10202), Decision Points (10506) and Backfired Function Points (10201) ) for current and previous snapshots with variation | |
GENERIC_TABLE | A Generic table component is built based on a table structure. The idea is to fill data into the table to populate it automatically | Application | The selection of metrics by standard quality tag name should only be used for an application where the extension “Quality Standards Support” is installed. If not, no metrics will be selected and graph will be empty | COL1=A,COL11=B,ROW1=C,ROW11=D,A=a,B=b,C=c|d,D=e|f|g where A,B,C and D are one of the axis above and a, b, c, d, e, f, g is one or multiple tags of the axis See more information in section about Generic components (CAST Report Generator - Generic components - 1.8.0) | TABLE;GENERIC_TABLE; COL1=METRICS,ROW1=CRITICAL_VIOLATIONS, METRICS=HEALTH_FACTOR, CRITICAL_VIOLATIONS =ALL, SNAPSHOTS=CURRENT | Depends on the selection. See more information in section about Generic Components (CAST Report Generator - Generic components - 1.8.0) | |
HEALTH_FACTOR | Health factors scores and evolution between previous and current snapshots | Application | No |
| TABLE;HEALTH_FACTOR;HEADER=SHORT | Current and previous health factors scores with evolution | |
HF_BY_MODULE | Health factors scores and evolution between previous and current snapshots for modules | Application | No |
| TABLE;HF_BY_MODULE;HEADER=SHORT | Current and previous health factors scores by modules with evolution | |
ID_NAME_INDICATOR_MAPPING | Provides numbers to use for ID values (for BC and distribution) | Application | No | None | TABLE;ID_NAME_INDICATOR_MAPPING | List of BC and distributions ids | |
IFPUG_FUNCTIONS | List of IFPUG functions | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
| TABLE;IFPUG_FUNCTIONS;COUNT=5 | List of IFPUG functions with FP details, module name and technology | |
LIST_OF_ALL_VERSIONS | List all version of application | Application | No |
| TABLE;LIST_OF_ALL_VERSIONS | List all version of application with name and functional date | |
LOC_BY_MODULE | List of modules with number of code lines | Application | No |
| TABLE;LOC_BY_MODULE | List of all modules with their number of code lines | |
METRIC_TOP_ARTEFACT | List of artifacts with violations to business criteria | Application | This component is only relevant on an engineering database. It is empty on an analytics database |
| TABLE;METRIC_TOP_ARTEFACT; COUNT=10,PAR=60016,IDX=0 | List of objets in violation for the idx-ème rule of the specified BC | |
MODULE_LIST | List of modules in application | Application | No |
| TABLE;MODULE_LIST | List of all modules names | |
PF_IGNORED_APPLICATIONS | Provides list of application ignored during computation. | Portfolio | No | None | TABLE;PF_IGNORED_APPLICATIONS | If not empty, investigation should be done to find corruption | |
PF_IGNORED_SNAPSHOTS | Provides list of snapshots ignored during computation. | Portfolio | No | None | TABLE;PF_IGNORED_SNAPSHOTS | If not empty, investigation should be done to find corruption | |
PF_GENERIC_TABLE | A Generic table component is built based on a table structure. The idea is to fill data into the table to populate it automatically | Portfolio | No | COL1=A,COL11=B,ROW1=C,ROW11=D,A=a,B=b,C=c|d,D=e|f|g
See more information in section about Generic components (CAST Report Generator - Generic components - 1.8.0) | TABLE;PF_GENERIC_TABLE; ROW1=APPLICATIONS, COL1=CRITICAL_VIOLATIONS, CRITICAL_VIOLATIONS =ALL,APPLICATIONS=EACH | Depends on the selection. See more information in section about Generic Components (CAST Report Generator - Generic components - 1.8.0) | |
PF_BC_RELEASE_PERFORMANCE | SLA view | Portfolio | No |
SLA Assessment thresholds :
Actual score : average score using latest snapshot data (even if snapshot date is before current quarter Target score: score to reach, to be configured as an option of the component Score from previous quarter: average score using snapshot from previous quarter. If last snapshot date is old and previous current quarter, last snapshot date will be used also for previous quarter calculation | TABLE;PF_BC_RELEASE_PERFORMANCE; BF=2.90 2.90 2.90 2.90 2.90 2.90 2.90 2.90, SLA=2 5 | SLA view for Business Criterion : previous score, target score, current score and SLA | |
PF_TOP_RISKIEST_APPS | Top riskiest applications regarding specific health factor | Portfolio | No |
| TABLE;PF_TOP_RISKIEST_APPS; COUNT=5,ALT=60017 | List of applications with number of critical violations, BC score and last snapshot date | |
QUALITY_RULE_VIOLATIONS | List of violations for a quality rule | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
If there is no previous snapshot, column Status is not displayed | TABLE;QUALITY_RULE_VIOLATIONS; BCID=60013,ID=7788,COUNT=10 | List of objects in violation for the rule with their PRI and status | |
QUALITY_RULE_VIOLATIONS_BOOKMARKS | List of violations for a rule with associated bookmarks | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
If there is no previous snapshot, status is not displayed | TABLE;QUALITY_RULE_VIOLATIONS_BOOKMARKS; ID=7788,COUNT=5 | List of violations with object name, type, status, file path and bookmark | |
QUALITY_STANDARDS_EVOLUTION | Evolution of sub-standards for a quality standard | Application | To use this component, the Quality Standards Mapping extension should be installed on the central where the application resides, with minimum version 20181030 |
| TABLE;QUALITY_STANDARDS_EVOLUTION; STD=CWE-2011-Top25 | List the sub standards with total, added and removed violations (row is highlighted if total or added violations are more than 0) | |
REMOVED_VIOLATIONS_LIST | List of removed violations by Business Criterion | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
| TABLE;REMOVED_VIOLATIONS_LIST; BCID=60017,COUNT=10 | List the violations that have been deleted, either fixed or disappeared (because of exclusion or deletion of object) with rule name, object name, compounded weight of the rule, and action and exclusion status. | |
RULE_IMPROVEMENT_OPPORTUNITY | For a Business Criterion, list of rules sorted by highest improvement opportunity | Application | No |
Formula is: (quality rule weight x technical criterion weight) * (4 – quality rule grade) | TABLE;RULE_IMPROVEMENT_OPPORTUNITY; PAR=60017,COUNT=10 | List of rules wit violations and scores evolutions | |
RULE_NAME_DESCRIPTION | Rule name details and violations count | Application | No |
| TABLE;RULE_NAME_DESCRIPTION;RULID=4670 | Descriptions of the rule with count of violations in current snapshot | |
RULE_NAME_DESCRIPTION_TOPCRITVIOL or METRIC_NAME_DESCRIPTION | Rule Name Details & Violation Count For Top Critical Violations Rules | Application | No |
| TABLE;RULE_NAME_DESCRIPTION_TOPCRITVIOL; COUNT=3,PAR=60016 | Descriptions of the top rules for a BC with count of violations in current snapshot | |
RULES_LIST | List of rules for list of criterion | Application | No |
| TABLE;RULES_LIST; PAR=60014|60013|60012|60011|60016, COUNT=7 | List of rules with their compounded weight, criticity, score, technical criteria, number of violations, and successfull checks | |
RULES_LIST_LARGEST_VARIATION | List of rules with largest variation | Application | No |
The formula are taken from the ones from CED :
| TABLE;RULES_LIST_LARGEST_VARIATION; BCID=60017,VARIATION=decrease, DATA=number,COUNT=50 | List of rules with compounded weight and number of violations variation | |
RULES_LIST_STATISTICS_RATIO | List of violations statistics by BC, TC or Standard Quality Tag | Application | To use the quality standard tags selection, the Quality Standards Mapping extension should be installed on the central where the application resides. When you select the metric id for a BC or TC, all the QRs belonging to this BC or TC is added for displaying violations |
| TABLE;RULES_LIST_STATISTICS_RATIO; METRICS=CISQ-Security, COMPLIANCE=true,LBL=violations | List of selected rules with total, added and removed violations, and optionnally the compliance ratio | |
LIST_RULES_VIOLATIONS_BOOKMARKS | List of violations for a list of rules with bookmarks | Application | This component is only relevant on an engineering database. It is empty on an analytics database. This component exists only for word document. The results would not be readable on powerpoint. To use the quality standard tags selection, the Quality Standards Support extension should be installed on the central where the application resides. When you select the metric id for a BC or TC, all the QRs belonging to this BC or TC is added for displaying violations |
If there is no previous snapshot, status is not displayed | TABLE;LIST_RULES_VIOLATIONS_BOOKMARKS; METRICS=CWE,COUNT=2 | Selected rules with list of detailed violations (object name, type, status, file path, bookmarks,...) | |
TC_IMPROVEMENT_OPPORTUNITY | For a Business Criterion, list of technical criteria sorted by highest improvement opportunity | Application | No |
Formula is : Sum (rule weight x technical criterion weight) * (4 – technical criterion grade) | TABLE;TC_IMPROVEMENT_OPPORTUNITY; PAR=60017 | List of technical criterion with number of violations, total checks and scores | |
TECHNICAL_CRITERIA_RULES | List of rules with new violations by technical criteria | Application | Behavior : if no new violation appeared on rule, rule description is not loaded |
| TABLE;TECHNICAL_CRITERIA_RULES; TCID=61001,BZID=60016,CNT=1 | Rules with name, description and number of violations | |
TECHNICAL_DEBT | Technical debt | Application | If selected « previous snapshot » in Report Generator interface is not the n-1 version, results will sum the Technical Debt Added and removed |
| TABLE;TECHNICAL_DEBT | Technical debt, with added and removed | |
TECHNICAL_SIZING | Technical size information | Application | No | None | TABLE;TECHNICAL_SIZING | Technical information about application : lines of code, by files and classes; number of sql artifacts and tables | |
TECHNICAL_SIZING_EVOLUTION | Technical size evolution information | Application | No | None | TABLE;TECHNICAL_SIZING_EVOLUTION | Technical information about evolution of application : lines of code, by files and classes; number of sql artifacts and tables | |
TECHNO_LOC | Top technologies by size | Application | No |
| TABLE;TECHNO_LOC | Lines of codes by technologies | |
TECHNO_LOC_EVOLUTION | Top technologies evolution by size | Application | No |
| TABLE;TECHNO_LOC_EVOLUTION | Evolution of lines of code by technologies | |
TECHNO_LOC_BY_MODULE | Technologies - Lines of code by modules | Application | No | None | TABLE;TECHNO_LOC_BY_MODULE | Lines of code in modules by technologies | |
TOP_COMPONENTS_BY_PROPERTIES | List of top components by properties Can be used to replace CED reports :
| Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
For PROP1 and PROP2, the available values are :
If PROP1 and/or PROP2 is not correctly set,list of available values is displayed | TABLE;TOP_COMPONENTS_BY_PROPERTIES; PROP1=cyclomaticComplexity, PROP2=ratioCommentLinesCodeLines, ORDER1=desc,ORDER2=asc,COUNT=10 | List of top objects regarding 2 properties | |
TOP_CRITICAL_VIOLATIONS | Top Critical Violations | Application | No |
| TABLE;TOP_CRITICAL_VIOLATIONS; BC-ID=60017,COUNT=5 | List of critical rules with their numbers of violations | |
TOP_CRITICAL_VIOLATIONS_EVOLUTION | Evolution of top critical violations | Application | No |
| TABLE;TOP_CRITICAL_VIOLATIONS_EVOLUTION; BC-ID=60017,COUNT=10 | Evolution of the number of violations by critical rules | |
TOP_NON_CRITICAL_VIOLATIONS | Top Non Critical Violations | Application | No |
| TABLE;TOP_NON_CRITICAL_VIOLATIONS; BC-ID=60017,COUNT=10 | List of non critical rules with their numbers of violations | |
TOP_NON_CRITICAL_VIOLATIONS_EVOLUTION | Evolution of top non critical violations | Application | No |
| TABLE;TOP_NON_CRITICAL_VIOLATIONS_EVOLUTION; BC-ID=60017,COUNT=10 | Evolution of the number of violations by non critical rules | |
TOP_RISKIEST_COMPONENTS | Top riskiest components | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
| TABLE;TOP_RISKIEST_COMPONENTS; SRC=PERF,COUNT=14 | List of objects belonging to a module with their PRI | |
TOP_RISKIEST_TRANSACTIONS | Top riskiest transactions | Application | This component is only relevant on an engineering database. It is empty on an analytics database. |
| TABLE;TOP_RISKIEST_TRANSACTIONS; SRC=PERF,COUNT=14 | List of transactions with their TRI | |
TQI | Technical Quality Index scores | Application | No | None | TABLE;TQI | TQI score for current and previous snapshots | |
TQI_BY_MODULE | Technical Quality Index scores by modules | Application | No |
| TABLE;TQI_BY_MODULE | TQI current and previous scores with variation by modules | |
BC_BY_TECHNO | BC score by technologies | Application | No |
| TABLE;BC_BY_TECHNO;ID=60017 | BC score by technologies | |
VIOLATIONS_LIST | List of violations by health factor | Application | This component is only relevant on an engineering database. It is empty on an analytics database |
| TABLE;VIOLATIONS_LIST; BCID=60016,COUNT=10, NAME=SHORT,FILTER=ALL | Detailed list of violations with status, PRI, exclusion and action status, rule name, BC name, object name, object status | |
VIOLATION_STATISTICS | Statistics on violations | Application | No | None | TABLE;VIOLATION_STATISTICS | Number of critical violations, per file and per kloc, number of complex objects and number of complex objects with violations | |
VIOLATION_STATISTICS_EVOLUTION | Evolution of statistics on violations | Application | No | None | TABLE;VIOLATION_STATISTICS_EVOLUTION | Evolution of the number of critical violations, per file and per kloc, number of complex objects and number of complex objects with violations | |
VIOLATION_SUMMARY | Violation Summary per application or modules, provides violation information (grades, counts, compliance ratios…) for critical and/or non-critical rules, for the whole application or per module | Application | No |
| TABLE;VIOLATION_SUMMARY; MODULES=0,CRITICAL=1,NONCRITICAL=0, GRADE=1,TOTAL=0,FAILED=1, SUCCESSFUL=0,ADDEDREMOVED=1, COMPLIANCE=0,COUNT=5 | List of rules with scores, number of violations, added and removed violations with criticity |