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


This page lists the changes made in the configuration folder and details the releases impacted by the changes.

When migrating your configuration, you should be able to review each change since the date of your previous release to adapt your model to the changes where necessary.


11 May 2021 - Update PMD ruleset.xml (21.0.0)

PMD ruleset.xml has been updated, some rules have their severity increased or decreased. Other rules are now disabled. 

We can find a table with all modified rules: [here]

01 February 2021 - Updated Technical Debt computation (20.2.0)

The Technical Debt time cost for each remediation level has been revised, to produce a less costly Technical Debt result.

These new values are (values in minutes) :

<Package>
<Constant id="RCTINY" value="0.5" />
<Constant id="RCLOW" value="1" />
<Constant id="RCMEDIUM" value="20" />
<Constant id="RCHIGH" value="60" />
<Constant id="RCHUGE" value="240" />
</Package>


Note: It is possible to go back to the previous computation (for Squore versions prior to 20.2.0), by overloading the "remediation_costs.xml" file.
To overload this file:

  • Add a new file to the overloading configuration folder
    <Overloading Configuration Folder>\models\software_analytics\Analysis\remediation_costs.xml
  • Refine the following constants to set them to the their previous values (values are in minutes)
    <Package>
    <Constant id="RCTINY" value="1" />
    <Constant id="RCLOW" value="10" />
    <Constant id="RCMEDIUM" value="30" />
    <Constant id="RCHIGH" value="60" />
    <Constant id="RCHUGE" value="480" />
    </Package>

Potential Impact

  • Technical Debt values will produced lower values than in previous Squore versions (prior to 20.2.0)

  • Reapply Model will impact old versions of a project where Technical Debt is computed


03 December 2020 - Constant data counting has been included into the model (20.2.0)

  • Three metrics have been created (VPBL, VPRV, VPRT), to count scoped data (Public, Private, Protected) while ignoring constants
  • Constants are still counted by specific metrics (CPBL, CPRV, CPRT)


Potential Impact

  • The complexity (CPXT_OWN) for CLASS has been updated to use VPBL instead of APBL for types "JAVA_CLASS;CPP_CLASS;CSHARP_CLASS;JAVA_ENUM"
  •  Also, since VPBL is computed for types "ABAP_CLASSDEF;JAVA_INTERFACE", CPXT_OWN is also defined for these types (but the FCCENTROID computation only contains VPBL, all other indicators are CLASS-only)
  • In addition, the grammar for ABAP has been updated so rename the three metrics (DPBL, DPRV, DPRT) into (APBL, APRV, APRT)

06 March 2020 - Updated cloning metrics for backwards compatibility (20.0.0)

Three cloning ratios have been updated: 'CCR', 'ICCR', 'RSR'

Their computations has been updated so that: if CCLC is not available (i.e. <0), LC is used instead

Potential Impact

  • No impacts on projects where CCLC is not available

  • Reapply Model will also have no impact on old versions of a project where CCLC is not available
  • If a project contains old versions where CCLC is not available, and is rebulid with a Squore version where CCLC is available, these three metrics will evidently be computed differently


10 February 2020 - Added VectorCAST/Lint Data Provider (20.0.0)

A new Data Provider has been added: VectorCAST/Lint, used to import PC Lint MISRA 2012 findings


04 February 2020 - Requirements 'Testable state' update in Software Analytics (20.0.0)

The existing 'Testability detection mode' parameter has been extended. It now proposes a third option, which sets the Testable state for a Requirement as soon as it is linked to Tests artefacts.

This option is available in the Squore Form at project building scope.


Potential Impact

  • No impacts on existing projects, as it is a new option on an existing attribute.

Details

  • The associated tag 'REQ_TESTABILITY_MODE" corresponding values are 0, 1, 2 for the three modes.




04 February 2020 - Requirements 'Coverage override' added to Software Analytics (20.0.0)

It is now possible to manually set a requirement's coverage state. Three behaviors are available: 

  • Use the coverage computation based on linked Test Results (default behavior)
  • Force the coverage as 'Not Covered'
  • Force the coverage as 'Covered'

The user has to provide a justification for changing this behavior.

This option is available in the Squore Form at the Requirement artefact scope.


Potential Impact

  • No impacts on existing projects, as the default value for this new tag sets the old behavior (use the coverage computation)



04 February 2020 - Tests 'Status override' added to Software Analytics (20.0.0)

It is now possible to manually set a test status. Four behaviors are available: 

  • Use the status returned by the external tool which provided the test to Squore (default behavior)
  • Force the status to 'Passed'
  • Force the status to 'Inconclusive'
  • Force the status to 'Failed'

The user has to provide a justification for changing this behavior.

This option is available in the Squore Form at the Test artefact scope.


Potential Impact

  • No impacts on existing projects, as the default value for this new tag sets the old behavior (use the status provided by the external tool)



29 March 2019 - Remove old exports (19.0.0)

A new syntax is available to improve exports, so we remove the call to the old scripts "sqexport.pl" in Software Analytics model and Shared exports.

Potential Impact

  • The list of available exports by default.

Details

  • Remove all lines: <ExportScript name="Files with level G" script="${scriptDir}/sqexport.pl">...



26 March 2019 - Added new MISRA conting metrics(19.0.0)

New MISRA-related counting metrics have been added at APPLICATION level.

These metrics are counting rules from the ruleset, not violations of these rules.
Counting metrics are:

  • Number of MISRA Rules
  • Number of MISRA Directives
  • Number of MISRA Rules or Directives per recommendation level
  • Number of MISRA Rules or Directives  per ISO characteristic

Potential Impact

  • The list of produced metrics contains now these additional "MISRA counting metrics" at APPLICATION level

Details

  • Added a basic Scale 'SCALE_MISRA_TYPE' to differenciate between 'Rule' and 'Directive' MISRA checks

  • Added 'SCALE_MISRA_TYPE' to the list of hidden categories in the Findings tab

  • Updated the misra_c_2004/2008/2012 rulesets to introduce the SCALE_MISRA_TYPE

  • Added APPLICATION-level MISRA counting metrics, to count rules (not violations) from the ruleset, depending on their type (Rule, Directive), ISO characteristic, or Recommendation level

  • Added charts to represent the previous metrics. These charts are not in any dashboard, they are to be used in reports



24 Mars 2019 - Model structure rework (19.0.0)

To prepare for the upcoming Analysis Model Editor, the structure of the Software Analytics model as well as Shared environment have been reworked.

Potential Impact

  • Several objects (Requirements, Tickets, Tests) have been simplified in the Software Analytics model. Modelling objects that were only related to the Data Provider producing them have been removed from the Software Analytics model.
  • Several Data Providers shared configurations (located in Shared\data_provider) have been enhanced with modelling objects previously defined in the Software Analytics model.



10 Mars 2019 - Remove useless descriptions of Software Analytics model (19.0.0)

A list of descriptions were imported but not used. Many mnemonics similar to IDs are removed too.

Potential Impact

  • None

Details

  • Remove useless lines on descriptions bundle: <Properties src="..." />



05 Dec 2018 - Cloning rules Technical Debt and counting adjustments (19.0.0)

'Changeability' Technical Debt was not taking into account all cloning rules.
Also, some counting metrics were counting rules of all natures, including 'Cloning' ones, when they should be restricted to 'Non conformity' and 'Risky practice'

As a result:

  • the Technical Debt 'Changeability' computation has been updated
  • some violation occurrences counting metrics are now restricted to 'Non conformity' and 'Risky practice' natures

Potential Impact

  • The Changeability Technical Debt value is now more accurate, and may increase

  • The 'Coding Rule Violations' chart ('Quality Assurance' dashboard) is more accurate, and may display fewer values

Details

  • Added 'R_NORS_MODULES' rule to the Technical Debt computation in the <SQUORE_HOME>configuration/models/software_analytics/Anaysis/technical_debt.xml file
  • Added additional filtering in some computations of <SQUORE_HOME>configuration/models/software_analytics/Anaysis/issues_counting.xml file



06 Nov 2018 - Polyspace Data Provider enhancement (19.0.0, #12564)

The Polyspace Data Provider has been enhanced to: 

  • Generate findings of 'Risky Construction' nature based on ORANGE, RED, GRAY type RTE checks
  • Take into account derogations from Polyspace (both on RTE checks and MISRA checks)

Potential Impact

  • The Violation density, which now takes into account Risky Construction findings, might increase

  • The Compliance, since MISRA derogations are now taken into account, might decrease if some MISRA violations are derogated in Polyspace

Details



25 Sept 2018 - Add a technical debt highlight (18.1.0)

New highlight is available: 

Potential Impact

  • None

Details

Technical Debt is the "own" technical debt of every modules. Modules without Technical debt are filtered. 

List is ordered by blocker issues. 



25 Sept 2018 - Update pies chart and test coverage graph (18.1.0)

Graphs have been reworked so they can be lifterable.




Potential Impact

  • Metrics which were used to compute the graphs have been removed from the models.

Details

See <SQUORE_HOME>configuration/models/Shared/Analysis/generic/critical_factor.xml

See <SQUORE_HOME>configuration/models/software_analytics/Analysis/test_coverage.xml




1 Aug 2018 - Additional metrics and ruleset for tickets (18.0.9, 18.1.0)

We have modified the import_ticket data provider. As a result, all data providers that are based on it (JIRA and Mantis in the default configuration) report extra metrics and also findings.

New findings:

  • R_MAPPED_STATUS
  • R_MAPPED_TYPE

New metrics:

  • UNKNOWN_AGREGATED_STATUS
  • UNKNOWN_TYPE

Potential Impact

  • This will mark existing Software Analytics projects as obsolete because of the new 
  • When the violation disappears, your project rating may improve

Details

See <SQUORE_HOME>/configuration/models/Shared/data_provider/shared/ticket



5 Jul 2018 - Disabled Missing Break rule for C# (17.0.14, 17.1.8,18.0.7)

We have modified the default ruleset for Squan Sources to exclude the rule Missing Break (R_BRKFINAL) for C#

The rule provided false positives for C#

Potential Impact

  • Removing the rule will remove the false positives findings for C# projects
  • When the violation disappears, your project rating may improve

Details

<SQUORE_HOME>configuration/models/Shared/data_provider/squan_sources/ruleset.xml now has an excludingTypes attribute that includes CSHARP.

<SQUORE_HOME>configuration/models/Shared/data_provider/squan_sources/ruleset.xml
<Measure measureId="R_BRKFINAL" type="RULE" categories="SCALE_NATURE.NON_CONFORMITY;SCALE_SEVERITY.CRITICAL;SCALE_REMEDIATION.LOW;CHARACTERISTIC.MAINTAINABILITY" families="STABILITY;TESTABILITY" targetArtefactTypes="MODULES" excludingTypes="PYTHON;ADA;SQL;TSQL;FORTRAN;ABAP;COBOL;VBNET;CSHARP" />





20 Mar 2018 - Remove obsolete files (18.0.0)

Potential Impact

Missing xml or properties files on customers configuration.

If it is your case, see the following details to correct it or ask to the support team to retrieve the missing files.

Details

  • The main objective is to remove duplicate or obsolete rules and metrics definitions to avoid confusion.
  • Since the Squore 2015-A, the recommandation is to separate base metrics and rule definitions for data providers from others metrics used to compute the rating in your model.
    For example, if you use the squan sources data provider, you should import the content of the folder "<configuration>/models/Shared/data_provider/squan_sources".
  • Main removed files or folders and recommandation:
    • <configuration>/models/Shared/Analysis/Code/RuleSet/* → <configuration>/models/Shared/data_provider/*
    • <configuration>/models/Shared/Analysis/Code/BaseMeasures/* → <configuration>/models/Shared/data_provider/squan_sources/*
    • <configuration>/models/Shared/Analysis/Code/ObjectOrientation/* → <configuration>/models/Shared/data_provider/squan_sources/*
    • <configuration>/models/Shared/Analysis/Code/iso9126/* → <configuration>/models/Shared/Analysis/product_quality/iso9126
    • <configuration>/models/Shared/Analysis/product_quality/code/call_relation/* → <configuration>/models/Shared/data_provider/squan_sources/*
    • <configuration>/models/Shared/Analysis/product_quality/code/control_flow_analysis/* → <configuration>/models/Shared/data_provider/squan_sources/*
    • <configuration>/models/Shared/Analysis/product_quality/code/vocabulary/* → <configuration>/models/Shared/data_provider/squan_sources/*

15 Mar 2018 - Stability changes (18.0.0)

Changes on Squan Sources Data Provider

  • suspMod - Suspicious findings on code modification
  • suspBefore - Suspicious findings on code modification before finding location

The purpose of these new options is to set a "suspicious" flags on relaxed findings when they are attached on a modified artifact.


6 Mar 2018 - Add a Test Gap Analysis Treemap (18.0.0)

Potential Impact

This works only for project which have Test artifact (from VectorCAST, RTRT, GoogleTest...)

 Only new measure are added to the configuration. 

Details

  • Objective is to highlight the part of the code which has changed and where the test have not been updated.
  • Results Categories:
    1. Code remains unchanged + Test is compliant => GREEN (output = 0)
    2. Code remains unchanged + Test is NOT compliant => Light RED (output = 3)
    3. Code has changed + Test is compliant + Test execution is update => Light GREEN (output = 1)
    4. Code has changed + Test is compliant + Test execution is NOT update => Orange (Dirty results) (output = 2)
    5. Code has changed + Test is NOT compliant => RED (bad results) (output = 4)
  • Note: 
    • Code stability is based on "Monitoring period".
    • Test is Compliant: Coverage is OK and Test status is Passed

6 Mar 2018 - Removing confusing NSI (18.0.0)

Potential Impact

NSI measure and indicator have been removed to avoid confusing statement for end user. 

NSI was not used in the standard model (Software Analytics and Automotive). 

Stability metric SI remains available. SI definition is based on HIS standard. 


28 February 2018 - Added GENERIC_FILE and GENERIC_FILES artefact types (18.0.0)

In order to make it easier to add more languages to Squan Sources (documentation), the GENERIC_FILE and GENERIC_FILES types were added by default in Configuration/models/Shared/data_provider/squan_sources/artefact_types.xml

Potential Impact

You configuration may report errors if you have not added these types as well.

Details

Lines added to artefact_types.xml:

...
<ArtefactType id="GENERIC_FILE" heirs="GROOVY_FILE" /> <!-- Use this type to add your new file types -->
<ArtefactType id="GENERIC_FILES" heirs="FILES;GENERIC_FILE" />
...




13 Feb 2018 - Old models removed (18.0.0)

Potential Impact

If your model is based on the following model list, please, contact us to retrieve a package that contains the old model files.

Details

Removed models:

  • iso9126
  • technical_debt
  • risk_index
  • HIS_Metrics



30 Jan 2018 - Color Update in Technical Debt trend (18.0.0)

Potential Impact

None. This is only a GUI feature. 


29 Jan 2018 - Adding Background color in highlight (18.0.0)

Potential Impact

None. This is only a GUI feature. 


BeforeAfter


18 Jan 2018 - New Technical Debt computation in Software Analytics (18.0.0)

Potential Impact

Functionality and results are completely identical but in order to reduce the number of impacted measures in the formula, some optimisation have been implemented. 

Side effect, the computation of "New", "Modified" and "Unchanged" debt are more accurate. 

CAREFUL: COST_ISSUE_TRA has been renamed to COST_ISSUE_POR

Moreover the Technical Debt is now displayed in Man/days (=8 hours by default).

 


18 Jan 2018 - Cloning Changes (18.0.0)

Removed "backward" option

This mode turned on the old algorithm (< 14-B) to compute cloning metrics on CFT. This option has been removed.

New CCLC metric - Code Cloning Line Counting

This is the effective number of lines used for cloning detection. This might not be LC, as two new options have been added to the Squan Sources data provider: skip blank lines, and skip comment lines. This is not (LC - BLAN - COM) either, as some languages are hashed correctly. Metrics related to cloning ratio shall use this new metric.


18 Jan 2018 - Artefact Status update (18.0.0)

Potential Impact

Formula has been updated due to update of SI into PERCENT format. 

Used in Software Analytics model. 

Bug is fix and not negative impact are expected. 



15 Jan 2018 - Stability Changes (18.0.0)

Duplicated metrics

GCSIZ and CFT are the same metrics, and GCSIZ is not generated anymore.


15 Dec 2017 - Update Automotive Ruleset (18.0.0)

Potential Impact

The MISRA rules from Squore have been set as MISRA rules (and not considered as information anymore). 

This has been done to avoid inconsistency in the results (table which display MISRA violations without being able to point to Squore findings...) 

C MISRA rules from Squore have also been added to the ruleset.  

Rating could be impacted. 

Details

Everything can be assessed in the findings tab.




01 Dec 2017 - Add a new Productivity KPI (18.0.0)

Potential Impact

The KPI is based on the changes (lines added, modified or removed) regarding the number of elapsed days.

Productivity = Impacted lines / days

It should not impact the rating. 

Details

Table is visible on some dahboard at application level.

  - automotive: project manager and quality engineer

  - software analytics: project manager 



28 Nov 2017 - Add a new Report for Automotive Standard Compliance (18.0.0)

Potential Impact

A modification (=fix) has been operated in Shared\Analysis\product_quality\automotive\stats\function_stats.xml

      - Bad computation for MISRA NCC 

      - Bad computation for Coverage compliance

The new report generates a summary of all 3 standards compliance, including export at file level with specific highlights

Details

No specific details. 



11 Dec 2017 - providedBy attribute in Rulesets (17.0.9, 17.1.4)

Potential Impact

We are changing the way the Rule Compliance indicator is computed, and you may need to replicate this change to get this feature if you are overriding:

  • properties.xml
  • any ruleset XML file in shared/data_provider

To learn more about this change, refer to this article.

Details

A providedBy attribute was added at the top of the ruleset in the package element:

<package> ==> <Package providedBy="PC_Lint_MISRA;Polyspace_MISRA;QAC_MISRA">

This element defines how rules are taken into account or ignored when the specified data providers are not part of the analysis.



11 Dec 2017 - General Cleanup (17.0.9, 17.1.4)

Potential Impact

None, we are just tightening the XSD schema and ensuring that all files in the configuration pass validation

Details

Some files contained targetArtefactTypes attributes that ended with a ;. We removed the unnecessary semi-colon. This has no functional impact. You may do the same in your models to avoid a warning in the Model validator.

Here is an example from <configuration>/models/software_analytics/Analysis/test_coverage.xml

Before

<!-- C1 coverage -->
<Measure measureId="OBJECT_C1" ...>
<Computation targetArtefactTypes="PACKAGES;FILES;CLASSES;" result=".." />
</Measure>

After

<!-- C1 coverage -->
<Measure measureId="OBJECT_C1" ...>
<Computation targetArtefactTypes="PACKAGES;FILES;CLASSES" result=".." />
</Measure> 




24 Nov 2017 - Add a Project Status tag at application level (18.0.0)

Potential Impact

A tag "Project Status" has been added into Automotive model so the end user can filter project in the portfolio view. 

The objective is to be able to filter "not active" project in order to focus on current development only.

Details

Build_description.xml has been updated and its associated table in dashboard. 

<line indicatorId="PROJECT_STATUS" displayType="NAME" displayValueType="TEXT" />



24 Nov 2017 - Update of Project Summary Table (18.0.0)

Potential Impact

The project summary table (model level) has been reworked so it displays "?" if the KPI is not activated. 

Some metrics have been updated to have a better definition: 

<Measure measureId="TCOVCR" dataBounds="[0;1]" format="PERCENT" invalidValue="?" defaultValue="0">

Details

There shall no be any side effect of this updates regarding rating of the project. 



24 Nov 2017 - Integration of Test Effectiveness in automotive model (18.0.0)

Potential Impact

The score can be impacted because Test Effectiveness has been introduced in the rating formula.

Test Effectiveness is a new KPI which is automatically build when importing the test results. 

A test artifact hierarchy is created by the data provider. Link to source code are also created by the data provider. 

Details

The root formula has been modified: KPI is TEST_EFFECTIVENESS.

<Measure measureId="QUALITY" defaultValue="0">
		<Computation targetArtefactTypes="MODULES" result="IF(CODING_RULE_WEIGHT=0 AND HIS_WEIGHT=0 AND CLONING_WEIGHT=0 AND TEST_WEIGHT=0,-1, FCENTROID(0,2,I.ROKR|CODING_RULE_WEIGHT,I.HIS_CUSTOM_KOR|HIS_WEIGHT,I.CLO|CLONING_WEIGHT,I.ISO26262_COVOUT|TEST_WEIGHT,I.TEST_EFFECTIVENESS|TEST_EFF_WEIGHT))" />
		<Computation targetArtefactTypes="PACKAGES;FILES;CLASSES" result="IF(CODING_RULE_WEIGHT=0 AND HIS_WEIGHT=0 AND CLONING_WEIGHT=0 AND TEST_WEIGHT=0,-1, FCENTROID(0,2,I.ROKR|CODING_RULE_WEIGHT,I.HIS_CUSTOM_KOR|HIS_WEIGHT,I.CLO|CLONING_WEIGHT,I.ISO26262_COVCR|TEST_WEIGHT,I.TEST_EFFECTIVENESS|TEST_EFF_WEIGHT))" excludingTypes="APPLICATION"/>
		<Computation targetArtefactTypes="APPLICATION" result="IF(CODING_RULE_WEIGHT=0 AND HIS_WEIGHT=0 AND CLONING_WEIGHT=0 AND TEST_WEIGHT=0 AND MEMORY_WEIGHT=0,-1, FCENTROID(0,2,I.ROKR|CODING_RULE_WEIGHT,I.HIS_CUSTOM_KOR|HIS_WEIGHT,I.CLO|CLONING_WEIGHT,I.ISO26262_COVCR|TEST_WEIGHT,I.RESOURCE_USAGE|MEMORY_WEIGHT,I.TEST_EFFECTIVENESS|TEST_EFF_WEIGHT))" />
</Measure>


Dashboard has been updated as well. 




22 Nov 2017 - Remove duplicated FindBugs rules definitions (18.0.0)

Potential Impact

The score can be impacted because the categories are changed and the counting of rules by category changed.

Details

ESYNC_EMPTY_SYNC: "Characteristic" change from "Efficiency" to "Reliability" and the severity from "Major" to "Minor".

RPC_REPEATED_CONDITIONAL_TEST: "Characteristic" change from "Efficiency" to "Reliability".



22 Nov 2017 - Remove duplicated FindBugs rules definitions (18.0.0)

Potential Impact

The score can be impacted because the categories are changed and the counting of rules by category changed.

Details

ESYNC_EMPTY_SYNC: "Characteristic" change from "Efficiency" to "Reliability" and the severity from "Major" to "Minor".

RPC_REPEATED_CONDITIONAL_TEST: "Characteristic" change from "Efficiency" to "Reliability".



21 Nov 2017 - Remove useless level dependent metrics in Software Analytics Model (17.0.8, 17.1.3)

Potential Impact

N/A

Details

Remove A_STAT, B_STAT, C_STAT, ... measures of the Software Analytics Model, these metrics were only used in temporal distribution, advantageously replaced by a TESStackedBar on the "LEVEL" indicator weighted by the STAT measure.

Remove not used measures: CPXT_VOL_A, CPXT_VOL_B... of the Software Analytics Model.



21 Nov 2017 - Remove useless language dependent metrics in Software Analytics Model (17.0.8, 17.1.3)

Potential Impact

N/A

Details

Remove all <language>_LC and <language>_SLOC measures of the Software Analytics Model, these metrics were only used in languages distribution, advantageously replaced by a SimplePie on the "LANGUAGE" information weighted by the SLOC measure.



15 Nov 2017 - New Metrics in Software Analytics Model (17.1.2)

Potential Impact

N/A

Details

The following metrics have been added:

  • IGNORE_CALLING
  • IGNORE_CALLS
  • IGNORE_COMF
  • IGNORE_CYCLE
  • IGNORE_GOTO
  • IGNORE_LEVL
  • IGNORE_PARAM
  • IGNORE_PATH
  • IGNORE_RETURN
  • IGNORE_STMT
  • IGNORE_VG
  • JUSTIFIED_HIS_CALLING
  • JUSTIFIED_HIS_CALLS
  • JUSTIFIED_HIS_COMF
  • JUSTIFIED_HIS_CYCLE
  • JUSTIFIED_HIS_GOTO
  • JUSTIFIED_HIS_LEVL
  • JUSTIFIED_HIS_PARAM
  • JUSTIFIED_HIS_PATH
  • JUSTIFIED_HIS_RETURN
  • JUSTIFIED_HIS_STMT
  • JUSTIFIED_HIS_VG
  • TCOVOUT_REAL

For more details, consult https://support.squoring.com/diffs/overload_1711_1712/report



15 Nov 2017 - New Metrics in Squore Automotive Model (17.1.2)

Potential Impact

N/A

Details

The following metrics have been added:

  • IGNORE_CALLING
  • IGNORE_CALLS
  • IGNORE_COMF
  • IGNORE_CYCLE
  • IGNORE_GOTO
  • IGNORE_LEVL
  • IGNORE_PARAM
  • IGNORE_PATH
  • IGNORE_RETURN
  • IGNORE_STMT
  • IGNORE_VG
  • JUSTIFIED_HIS_CALLING
  • JUSTIFIED_HIS_CALLS
  • JUSTIFIED_HIS_COMF
  • JUSTIFIED_HIS_CYCLE
  • JUSTIFIED_HIS_GOTO
  • JUSTIFIED_HIS_LEVL
  • JUSTIFIED_HIS_PARAM
  • JUSTIFIED_HIS_PATH
  • JUSTIFIED_HIS_RETURN
  • JUSTIFIED_HIS_STMT
  • JUSTIFIED_HIS_VG


For more details, consult https://support.squoring.com/diffs/overload_1711_1712/report




13 Sept 2017 - Add a new "Off" level (17.1.0)

Potential Impact

Default rating shall be identical. The graphical changes remains in the icon of the rating. "?" is replaced by "Off". 

Details

In Software Analytics: A new scales and metrics definition (SDESCR and TEST_COVERAGE) now use the intermediaite level "Off" which mean the KPI are turned off.

 This allows to the end user to activate or de-activate the Code Coverage or the Self-descriptiveness. 

Associated highlights have been updated. 




12 Sept 2017 - Integration of Clone Tracker "Suspicious Detection" Feature  (17.1.0)

Potential Impact

Default rating shall be identical. 

Details

New metrics and highlights are availalble to find suspicious changes in Clone results. 

  - Suspicious clones: Modules which were cloned in V(n-1), which are still cloned in V(n) and for those the code did change between V(n) and V(n-1)
  - Partially Lost Clones: Modules which were cloned (Textual and Algorithmic) in V(n-1) and which has lost one of the 2 type of clones V(n)
  - Lost clones: Modules which are no more cloned.
  - Lost and Suspicious clones: Modules which are no more cloned in V(n), which were cloned in V(n-1) and for those the code didn't change between V(n) and V(n-1) 




6 Sept 2017 - Correct the relaxation mechanism for SDESCR (17.0.6)

Potential Impact

Default rating shall be identical. 

Details

User can use the form to relax all SDESCR rules. Bug was that if all rules were relaxed, the SDESCR KPI was still activated and rated as "G" (=the opposite behavior of what the user would expect) 

Now, if the user relax all rules, the global KPI is de-activated ('?' icon)





31 Aug 2017 - Added support for COBOL paragraphs and sections (16.3.4, 17.0.5)

Potential Impact

The new artefact types (COBOL_SECTION and COBOL_PARAGRAPH) are not used by default, but including them in the model causes previous analyses to be marked as obsolete.

Details

The new artefact types were added to <SQUORE_HOME>/configuration/models/Shared/data_provider/squan_sources/artefact_types.xml

Before: COBOL_MODULES = COBOL_PROGRAM

After: COBOL_MODULES = COBOL_PROGRAM ; COBOL_SECTION ; COBOL_PARAGRAPH

In the rest of the Shared folder, occurrences of COBOL_PROGRAM were updated to COBOL_MODULES so that most metrics are supported for the new artefact types.




31 Aug 2017 - Added rulesets for FxCop and StyleCop (16.3.4, 17.0.5)

Potential Impact

More rules are enabled in Software Analytics, which may result in your projects having a different Rule Compliance than before.

Details

The new rulesets are located in:

<SQUORE_HOME>/configuration/models/Shared/data_provider/fxcop

<SQUORE_HOME>/configuration/models/Shared/data_provider/stylecop

The Analysis and Description Bundles of the Software Analytics model were modified to include them:

<SQUORE_HOME>configuration/models/software_analytics/Analysis/import.xml:

<Bundle>
...
<xi:include href="../../Shared/data_provider/fxcop/ruleset.xml" />
...
<xi:include href="../../Shared/data_provider/stylecop/ruleset.xml" />
...
</Bundle>

<SQUORE_HOME>configuration/models/software_analytics/Description/import.xml:

<Bundle>
...
<Properties src="../../Shared/data_provider/fxcop/descriptions" />
...
<Properties src="../../Shared/data_provider/stylecop/descriptions" />
...
</Bundle>


20 Jan 2017 - New findings for Squan Sources (16.2.4)

Potential Impact

Changed rule count for projects using Squan Sources (all languages)

Details

Squan Sources returns two new findings:

    • R_NOTODO: TODO shall not be commited in sources code as it brings confusion regarding code reliability.
    • R_NOFIXME: FIXME shall not be commited in sources code as it brings confusion regarding code reliability.

You can disable the changes in <SQUORE_HOME>/configuration/models/Shared/data_provider/squan_sources/ruleset.xml if you do not want them:

<Measure measureId="R_NOTODO" type="RULE" categories="SCALE_NATURE.NON_CONFORMITY;SCALE_SEVERITY.MINOR;SCALE_REMEDIATION.LOW;CHARACTERISTIC.RELIABILITY" families="STABILITY;FAULT_TOLERANCE" targetArtefactTypes="MODULES;FILES;CLASSES" />
<Measure measureId="R_NOFIXME" type="RULE" categories="SCALE_NATURE.NON_CONFORMITY;SCALE_SEVERITY.MINOR;SCALE_REMEDIATION.LOW;CHARACTERISTIC.RELIABILITY" families="STABILITY;FAULT_TOLERANCE" targetArtefactTypes="MODULES;FILES;CLASSES" />



19 Dec 2016 - Moved code_review module (16.2.3)

Potential Impact

update your <xi:includes /> in your bundles

Details

Moved code_review module from Shared/Analysis/product_quality/automotive to Shared/Analysis/product_quality/generic


19 Dec 2016 - Updated System Engineering modules (16.2.3)

Potential Impact

Modified metrics if you previously included the modules in your model

Details

N/A


19 Dec 2016 - Removed default value for rules in pylint ruleset (16.2.3)

Potential Impact

N/A

Details

Removed default value for rules in pylint ruleset in Shared/data_provider/pylint/ruleset.xml


19 Dec 2016 - New ScaleLevel in SCALE_NATURE (16.2.3)

Potential Impact

N/A

Details

Added a new ScaleLevel to SCALE_NATURE in Shared/basic_scales.xml

<ScaleLevel levelId="ARCHITECTURE" bounds="]5;6]" rank="7" />

3 Nov 2016 - Removal of non-multi-language models (16.2.0)

Potential Impact

If your model included any of the files in these folders, retrieve them from your current installation before you upgrade so you can move them to your custom configuration.

Details

Models that were not built to handle multi-language analysis have need removed (actually in 16.0):

  • ISO9126_KPI_Code_Cobol
  • ISO9126_Maintainability_C
  • ISO9126_Maintainability_Java
  • ISO9126_Maintainability_OO
  • ISO9126_Maintainability_Xaml
  • risk_index
  • SQuORE_ada
  • SQuORE_C
  • SQuORE_Java
  • SQuORE_OO
  • SQuORE_Plsql
  • Technical_Debt_Java


3 Nov 2016 - New Modules (16.2.0)

Potential Impact

N/A

Details

  • Shared\Analysis\product_quality\generic
  • Shared\Analysis\product_quality\function_point

3 Nov 2016 - Squore Cloning Ruleset and SCALE_NATURE Update (16.2.0)

Potential Impact

N/A

Details

  • The ruleset for cloning has been modified: Shared\data_provider\squan_sources\ruleset.xml

     SCALE_NATURE.NON_CONFORMITY;SCALE_SEVERITY.INFORMATION 
     =>  SCALE_NATURE.CLONING;SCALE_SEVERITY.xxx
    

    The associated scale SCALE_NATURE has been modified, with the addition of a CLONING scale level:

     \Shared\Analysis\basic_scales.xml
    
        <Scale scaleId="SCALE_NATURE">
            <ScaleLevel levelId="NON_CONFORMITY" bounds="];0[" rank="0" />
            <ScaleLevel levelId="RISKY_PRACTICE" bounds="[0;0]" rank="1" />
            <ScaleLevel levelId="RELAXATION" bounds="]0;1]" rank="2" />
            <ScaleLevel levelId="TEST" bounds="]1;2]" rank="3" />
            <ScaleLevel levelId="GUIDELINE" bounds="]2;3]" rank="4" />
            <ScaleLevel levelId="METRIC" bounds="]3;4]" rank="5" />
            <ScaleLevel levelId="CLONING" bounds="]4;5]" rank="6" />
        </Scale>



3 Nov 2016 - Code Status Moved (16.2.0)

Potential Impact

Update your includes

Details

Folder has been moved from Shared\Analysis\product_quality\automotive\code_status to Shared\Analysis\product_quality\generic\code_status

Info: generic should contain generic definition for software KPI such as "criticality" (=ASIL)



3 Nov 2016 - Risk Index deprecation - Software Analytics introduction (16.2.0)

Potential Impact

N/A

Details

With the addition of the Software Analytics model, which will become the standard model in Squore 17), the older Risk Index model is now hidden by default.

If you used it to create some projects, reactivate it by editing your properties.xml (at the root of your top configuration folder by copying the one from the standard configuration and removing the line:

...
<hideModel name="risk_index" />
...


If you do not want to see this wizard when you create a new project, update your properties.xml at the top of your configuration folder and add the line:

...
<hideModel name="software_analytics" />
...

27 Jun 2016 - Supporting Meta Projects (16.1.0)

Potential Impact

A new artefact type is necessary to work with meta projects in your model

Details

If you plan to use meta-projects and are not using the standard artefact types included in Squore, you will need to change your models to add the SUB_APPLICATION type, as described here



6 Apr 2016 - Renamed Analysis Model Editor file (16.0.0)

Potential Impact

A new artefact type is necessary to work with meta projects in your model

Details

If you previously used the Analysis Model Editor to turn off some rules in your model, the Bundle.xml file in the Analysis folder of your model looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<Bundle xmlns:xi="http://www.w3.org/2001/XInclude">
  <xi:include href="AMEBundle.xml" />
  (...)
</Bundle>

AMEBundle.xml is the file where the rules that were turned off were located.

With the changes made to improve the Analysis Model Editor in Squore 16:

  • it is no longer necessary to include the AMEBundle.xml in your Bundle.xml
  • AMEBundle.xml must be renamed to editor.xml

If you do not make these changes, the modifications defined in AMEBundle.xml will be treated as part of the model, not as modifications to the existing model anymore.

7 Oct 2015 - Renamed C alias to CTYPES (15-A-SP2)

Potential Impact

The minimum length for IDs in the configuration is 2 characters from now on. We renamed the C alias in the configuration to CTYPES in the configuration to comply with this new requirement. You may have to do the same if you use IDs under 2 characters.

Details

The main breaking change in since Squore 2015-A-SP2 is that it is now forbidden to use measure names and artefact types that are under 2 characters.

This means that if you had defined an artefact type called "C", this is no longer allowed.

For example, where previous versions defined an artefact type called "C":

<ArtefactType id="C" heirs="C_FILE;C_HEADER;C_FUNCTION" />

and used it in various rulesets as shown below:

<Measure measureId="BUFFERACCESSOUTOFBOUNDS" type="RULE" toolName="CPPCHECK" targetArtefactTypes="C;MINDC;CPP" />

This now needs to be rewritten as:

<ArtefactType id="CTYPES" heirs="C_FILE;C_HEADER;C_FUNCTION" />

and referenced as shown below:

<Measure measureId="BUFFERACCESSOUTOFBOUNDS" type="RULE" toolName="CPPCHECK" targetArtefactTypes="CTYPES;MINDC;CPP" />



  • No labels