There is no supported upgrade path between successive beta releases, nor between beta and 1.0.0-funcrel, therefore results produced in different releases cannot be compared.
1.0.4-funcrel
Other Updates
| Details |
|---|
| Fixes an issue where rules that have a result type as integer or no value were not considered for Technical Debt computation. Impacts to existing results are to be expected after upgrading to this release. |
Performance Improvements
| Summary |
|---|
| Performance issue introduced by the 1.0.3-funcrel release has been resolved. |
1.0.3-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 32318 | Fixes an issue with the Technical Debt calculation when the object which had a Technical Debt value in the previous snapshot is no longer part of the application. |
1.0.2-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 30001 | Snapshot blocked - Performance issue related to computation of Technical debt (ATDM). |
| 30002 | Snapshot blocked - Performance issue related to computation of Technical debt (ATDM). |
1.0.1-funcrel
Other Updates
| Details |
|---|
| Change the dependency on AIP Core (to >= 8.3.24) and com.castsoftware.cisq-index (to >= 1.0.0-funcrel). |
1.0.0-funcrel
Note
This release contains changes and updates to improve the stability of the aggregation and computation processes actioned by the extension. Changes are listed below.
Other Updates
| Details |
|---|
| Violation exclusions are now also excluded from the OMGTD calculation. |
| Data related to the computation of OMGTD values is now mostly stored separately from other metrics (i.e. not in the "dss_metric_results" table). |
| Aggregation processes have been reviewed in order to maintain consistency. |
| Deactivation of the extension will disable the extension and remove the side processes related to the OMGTD computations. |
| Clean up of OMGTD specific tables is performed when a snapshot is deleted. |
1.0.0-beta7
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 27199 | This correction fixes an error which occurs when upgrading from ≤ 1.0.0-beta5 to 1.0.0-beta6 and which prevents the new release from being installed: "SQL Error: ERROR: relation "omgtd_results" already exists." In addition, this fix also provides the ability to deactivate the extension without any adverse side effects. |
1.0.0-beta6
Note
This release of the extension requires the use of the Engineering Dashboard ≥ 1.22.0-funcrel.
Other Updates
| Details |
|---|
| If a Quality Rule contributes to more than one CISQ Pattern with different Effort values, then the minimum of these values will be considered for the Effort related to this Quality Rule. |
Performance Improvements
| Summary |
|---|
| A change has been implemented for the methods used to store results data. Technical debt results at object level are stored in a dedicated table. By default details are not stored and can be generated for display in the dashboard on demand. However it is possible to decide to store all details always. See https://doc.castsoftware.com/display/TECHNOS/OMG-ATDM+-+1.0#OMGATDM1.0-Resultstorage for more information. |
1.0.0-beta5
Other Updates
| Details |
|---|
| The calculation details for objects and rules are no longer stored in the Dashboard schema (aggregate details are still stored). Instead (in order to reduce the amount of data stored in the schema) these details will be generated on demand when required by future releases of the Dashboard RestAPI. There are no differences in results between this release and beta4 when using currently available RestAPIs, except at object and rule level where details will not be available. |
1.0.0-beta4
Other Updates
| Details |
|---|
| This corrects all aggregations at Application/BC level for Technical Debt and Enhanced Technical Debt. As such, small changes have been made to the formulas used to calculate Adjustment Factor (number of occurrences is no longer used) and Technical Debt (number of occurrences is now used), see https://doc.castsoftware.com/display/TECHNOS/OMG-ATDM+-+1.0. This change in formulas may impact your existing results. |
1.0.0-beta3
Upgrade from previous releases
There is no supported upgrade path from beta1/beta2 to beta3, therefore results produced by different releases of the extension cannot be compared. If you have installed beta1 or beta2, CAST highly recommends deleting any snapshots you may have generated with these releases, before installing beta3.
Updates
New sizing measures added
The extension now calculates the following metrics as a Sizing Measures in addition to those already calculated in beta2:
| Metric ID | Name | Description |
|---|---|---|
| 1062030 | OMG-ATDM: Remediation Effort ADDED | Measures the added remediation effort in number of minutes between two snapshots. Results are available at Application, Module, CISQ Business Criteria, CISQ Technical Criteria, Rule and Object level. |
| 1062032 | OMG-ATDM: Remediation Effort DELETED | Measures the removed remediation effort in number of minutes between two snapshots. Results are available at Application, Module, CISQ Business Criteria, CISQ Technical Criteria, Rule and Object level. |
1.0.0-beta2
Upgrade from beta1
There is no supported upgrade path from beta1 to beta2 therefore results produced by the two releases of the extension cannot be compared. If you have installed beta1, CAST highly recommends deleting any snapshots you may have generated with beta1, before installing beta2.
Updates
Dependency to CISQ-Index extension
In this release, the OMG-ATDM extension will now use the CISQ-Index extension instead of the Quality Standards Mapping extension (which was used in 1.0.0-beta1). The CISQ-Index extension will be automatically downloaded and installed when you download and install the OMG-ATDM extension.
Un-adjusted efforts are defined for each CISQ Pattern materialized as Technical Criteria in the CAST AIP Assessment Model:
Each CISQ Pattern is materialized as a Technical Criteria in the Assessment Model, for example, for ASCMM-MNT-1:
New sizing measures added
The extension now calculates the following metrics as a Sizing Measures - previously only 1062020 was calculated:
| Metric ID | Name | Description |
|---|---|---|
| 1062011 | OMG-ATDM: Complexity | The Complexity - or Effort Complexity - of the code elements implementing an Occurrence is qualification information that is measured according to the Effort Complexity definition from the Automated Enhancement Points (AEP) specification. (AEP). |
| 1062012 | OMG-ATDM: Exposure | The Exposure of an Occurrence is qualification information that measures the level of connectedness of the Occurrence with the rest of the software, both directly and indirectly through call paths. |
| 1062013 | OMG-ATDM: Concentration | Concentration is qualification information that measures the number of Occurrences within any Code Element in the software. |
| 1062014 | OMG-ATDM: Technological Diversity | The Technological Diversity of an Occurrence is qualification information that measures the number of distinct programming languages in which the code elements included in a single occurrence of a source code pattern are written. |
| 1062015 | OMG-ATDM: Gap Size | In the context of patterns which rely on roles that model values and threshold values that are not to be exceeded, the gap between these values must be closed to remediate this weakness; the Occurrence Gap Size is the extent of the gap, measured as the difference between the values and the thresholds. |
| 1062016 | OMG-ATDM: Adjusted Remediation Effort | The number of minutes needed to remediate a specific source code pattern that has been adjusted by qualification. |
| 1062020 | OMG-ATDM: Remediation Effort | Provides remediation effort for a violation, at CISQ Pattern, Application and Module level. |
| 1062021 | OMG-ATDM: Number of occurrences | An occurrence (or Pattern Occurrence) designates a single instance of a Source Code Pattern (or Pattern) representing a weakness that has been implemented in the measured software. (ASCMM, ASCRM, ASCPEM, ASCSM). |
Limitation removed
Technical Debt calculation is no longer limited to violations whose findings are bookmarks and call-paths - now, all violation types are taken into account.
1.0.0-beta1
Initial release of the extension.
