This page provides information on Violation's definition -
Release | Yes/No |
---|---|
8.3.x | |
8.2.x | |
8.1.x | |
8.0.x | |
7.3.x | |
7.2.x | |
7.0.x |
RDBMS | Yes/No |
---|---|
Oracle Server | |
Microsoft SQL Server | |
CSS2 | |
CSS1 |
Definition
The violation is couple = (Object,metric)
In this view, one violation = couple (Object 'com.salesmanager.central.cart.SiteMapAction.execute', metric 'Avoid large number of String concatenation') = couple (Object_ID '1145854',Metric_ID '7196')
Violation Status
The Violation status is set to new in a given snapshot (N) when the couple (Object,metric) exists for the snapshot (N) but doesn't for the previous snapshot (N-1).
Here following query shows that couple (Object_ID '1145854',Metric_ID '7196') has been computed for 2 and 3 but not for snapshot 1.
select * from DSS_METRIC_RESULTS where METRIC_ID=7196 and OBJECT_ID=1145854
METRIC_ID | OBJECT_ID | METRIC_VALUE_INDEX | METRIC_NUM_VALUE | METRIC_CHAR_VALUE | METRIC_OBJECT_ID | SNAPSHOT_ID |
7196 | 1145854 | 1 | 1 | NULL | 985023 | 2 |
7196 | 1145854 | 1 | 1 | NULL | 985023 | 3 |
This means,
For snapshot 2, the status of the violation (Object_ID '1145854',Metric_ID '7196') = to new
For snapshot 3, the status of the violation (Object_ID '1145854',Metric_ID '7196') = to Old.
Follow the different possible reasons that make violation status equal to new for a given snapshot:
- Added Object in snapshot (N) violating the metric
- Modifying an existing Object (updated object in snapshot (N)) leads to the metric violation
- The object is not updated but the one or parameter of the diagnostic has been modified leading to the violation
- The analysis context has been modified:
- added/updated/deleted objects in the KB
- added/deleted links in the KB
This point impacts the copy/paste metric, number commented code lines metrics and the diagnostic based on link(s) detection as 'unreferenced artifacts'
Note:
The modified value of the metric violation doesn't impact the Violation Status
The critical diagnostic doesn't impact the Violation Status
The status of violation is reported in following views -
- FRAME_PORTAL_INVESTIGATION_VIEW - Investigation - Quality Model Drilldown
- FRAME_PORTAL_DEVELOPMENT_VIEW - Investigation - Application Drilldown
- FRAME_PORTAL_VIOLATION_VIEW - Risk Indicators - Object Level
- Reports - FlexReport
- Reports - FAQuery
Types of Violation status
- Added : The violation did not exist in the preceding snapshot
- Deleted : The violation did exist in the preceding snapshot, but does not exist anymore
- Unchanged : The violation did exist in the preceding snapshot and still exists; moreover, its associated value have not changed
- Updated : The violation did exist in the preceding snapshot and still exists; however, some of its associated value has changed
The value associated to a violation depend of the type of the quality rule:
1.For Group and Path quality rules, value associated to a violation consists on the number of paths (number of associated rows in the DSS_METRIC_RESULTS table)
2.For other types of quality rules, value associated to a violation consists on its associated number, text and object (columns METRIC_NUM_VALUE, METRIC_CHAR_VALUE & METRIC_OBJECT_ID in the DSS_METRIC_RESULTS table)