Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel2
stylesquare

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

New highlight is available: 

Image Added

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

...

  • 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

...

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.

...

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/*

...

 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

...

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

...

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). 

...

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.

...

It should not impact the rating. 

Details

Table is visible on some dahboard at application level.

...

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

...

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:

...

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:

...

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.

...

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. 

...

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. 

...

<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.

...

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.

...

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".

...

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".

...

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.

...

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:

...

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

Potential Impact

N/A

Details

The following metrics have been added:

...

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.

...

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. 

...

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) 

...

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

...

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:

...

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:

...

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

...

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):

...

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" />

...