Monitoring embedded software projects
in the automotive industry

Software reliability improvement and maintenance costs reduction

Demonstration of work products quality and standard compliance

Integration of standard
ISO 26262

Optimization of testing strategy

Business process performance and support as recommended by
Automotive SPICE

SQUORE enables us to demonstrate compliance of our software deliverables with customer quality requirements.

Claude Pinaud, Software Manager, Powertrain Division, Continental.

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.

One main challenge: reconciling high delivery quality level, a priority for passenger safety, and ever faster time to market imperatives

Software development in the automotive industry is a singular business, because of the complexity of its constraints.
High volume of distribution: the car is the most widely used mean of transport. Embedded software is logically overexposed to potential exceptions and failures.
Users cannot act on systems: while airline pilots can switch to manual mode and still master the different instruments on board, the driver of a car only has a driver’s license. When it comes to the software, indeed, the developers are the only people in command. Therefore, risks have to be managed upstream.
Reliability is not a luxury: since user safety is involved in the core functions of a vehicle (breaking systems, airbags, etc.), reliability and stability of the software need to be guaranteed by the manufacturer. A defect can seriously damage the brand reputation, and tragically impact the potential costs of a correction, as well as the business performance of a car model.
A highly competitive market: even if the industry tends to be more concentrated, the opening-up of the automotive market strongly fostered competition, with the entering of new players and brands. While the part of the software cost increases in car production, the development processes have to be optimized.
Time-to-Market : manufacturers must be able to quickly integrate the recent technology evolutions in their systems, especially with regard to connectivity.
Inflexibility of the delivery: the pace of software deliveries is more similar with the mobile device industry than the airline or aerospace industries. Conversely, it is still a difficult and expensive decision to modify a software component that has been already delivered, until cars are not fully connected. So far, test-related costs will always be lesser than the costs of a recall of hundreds of thousands of vehicles.

How SQUORE will allow you to reconcily the strategic challenges of functional safety and time to market

Dedicated to all the actors 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 anayltics 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