Squore Reconcilies the Strategic Challenges of Functional Safety and Time to Market

Quality and functional safety represent major stakes for the development in the automotive industry. The emergence of standards such as ISO 26262 and Automotive SPICE clearly reflects the willingness of all players in the sector to take up this challenge.

To control and mitigate risks, development teams need real-time access to the most relevant indicators to optimize their software project management.


  • Software reliability improvement and maintenance costs reduction
  • Demonstration of work products quality and standard compliance HIS and MISRA
  • Integration of standard ISO 26262
  • Optimization of testing strategy
  • Business process performance and support as recommended by Automotive SPICE


Software, the New Engine of Automotive

For 30 years, the share of embedded electronics has been growing in the automotive industry, for the benefit of passenger safety, functionalities reliability, performance and comfort. A trend that will accelerate in the coming years, to see the wide-scale development of ever more electric, automated and interconnected cars.
For each of these development axes, software has become a major and transversal component, and is now indispensable to prevent accidents and malfunction risks. Actually, 40% of the value of a car is made of software components not less than 100 million interconnected vehicles will be on the road by 2025.
Thus, quality and functional safety represent major stakes for the development of the automotive industry, and the emergence of standards such as ISO 26262 and Automotive SPICE clearly reflects the willingness of all players in the sector to take up this challenge.


Reconciling High Quality Level, a Priority for Passenger Safety, and Ever Faster Time to Market Imperatives

Dedicated to all the users who need to address the dual requirement of component quality and costs and deadline optimization, Squore/Software Analytics includes a specific version dedicated to the automotive industry, which allows to ensure and demonstrate code compliance with automotive industry quality requirements (ISO 26262, HIS, MISRA,…), and implements Automotive SPICE base practices.

  • Predefined quality evaluation models: ISO SQuaRE 25010, ISO/IEC 9126
  • Automation of verification methods required by ISO 26262 standard.
  • Out-of-the-box” standardized control points from applicable standards: HIS complexity metrics, MISRA coding rules, code duplication, stability index
  • Risk-based testing strategy
  • Predictive analytics to check your project evolution against your planned objectives
  • Automated and continuous generation of optimized Action Plans to efficiently address the dual requirement of component quality and costs and deadline optimization


Checking MISRA Compliance

There are several MISRA checker tools, each one producing results in a specific format.

To provide a standard MISRA compliance assessment, Squore introduces a generic feature, part of the standard Squore/Software Analytics rating model.

The Squore monitoring solution process is broken down into three steps:

  • Aggregation of MISRA Checking Results from Various Tools

As of today, Squore provides standard plugins for reports generated by tools such as Klocwork, PC-Lint, QA-C, Polyspace, …
This plugin technology is extensible, meaning that results from other tools can be aggregated into Squore when necessary.

  • Rating of Each Project Component with Respect to MISRA Compliance

Squore/Software Analytics is able to check MISRA compliance for the following versions:

  • MISRA 2004: 146 rules in the ruleset
  • MISRA 2008: 228 rules in the ruleset
  • MISRA 2012: 159 rules in the ruleset

The ruleset contents can be adapted to any project rated with Squore. This means that Squore can be tailored to work with a subset of MISRA rules. The compliance (and rating) will be based on this configuration.

  • Dashboard Providing Misra-Related Monitoring Functions
Track MISRA Findings

The traceability feature allows us to attach each finding to the source code element it was found on.
In this example, MISRA findings found by Polyspace are shown, you can see that rule “R 16.7” was found in file “apsm_uds.c” at line 1918.

Track MISRA Metrics

The rating model computes MISRA rule violations counts, broken down by their severity.
The compliance ratio depends on the ruleset definition, and the violated rules.
Note that these metrics are computed.

Achieving Compliance to MISRA C and MISRA C++

Complying with ISO-26262

In the context of ADAS development, the ECUs number, size and complexity has drastically increased. And in the ECU development, safety is a continuous challenge as it impacts process, methods, tools and global strategy.

ISO-26262 Standard intends to address this topic by pointing to the safety and particularly for the ADAS developments.

In order to deal with heterogeneous ECU objectives, ISO-26262 also introduces the safety risk management which is directly derived from the ECU functionality: risk must be minimized for critical ECU requirements.

Squore integrates different features which are helpful for ISO-26262 compliance:

  • Static Code Analyzer Including HIS Metrics
  • External API Connector to Import Hardware and Software Data from Third Party Tools
  • MISRA import
  • CPU Load / Memory consumption
  • Test Results
  • Requirement data
  • Defect and change management tracking
  • Traceability Module Building Links Between Requirements, Test and Source Code
  • ASIL Tracking

  • Dynamic links between artifacts

  • Analytics Platform Aggregating Data and Computing Complex KPIs
Module Test Strategy According to ASIL
Coverage thresholds
HIS Metrics Compliance at Project Level
HIS metrics compliance
How to Comply with the ISO-26262 Standard


Embedded SW Criticality in Today’s Automotive Industry

Squore: Software quality assessment solution at Continental