V0.1 | 2018-10-18

Using a dashboard to comply with Standards (SPICE, ISO26262)

Squore Software Analytics

2

1. A dashboard for automotive Standard

2. Introduction to Squore

3. Demo and Use Cases

Agenda

3

Dashboard: Evaluating standard compliance

Squore Software Analytics

Reporting is a key step in quality assessment and standard compliance:

It shall assess the maturity of the building process

It shall prove that expectations are met in term of product quality

It shall be automated

What?

(Data, Activities...)

Dashboard

For Who?

(users, accessibility...)

How?

(Data feeding processes)

4

Dashboard Vs SPICE

Squore Software Analytics

A dashboard shall …

Be shared between all stakeholdersincluding end customer (Ex: ACQ4, SPL2)

Be connected to Development Tools (Ex: SUP3, SUP9, SUP10)

Support customized quality objectives (Ex: ACQ11, SUP1, SUP2)

Allow collaboration within the team (Ex: SUP4)

Collect and Store data (Ex: MAN6, SYS, SWE)

Provide High level KPI (Ex: MAN3)

5

Standards Vs Development process... Pragmatic approach

Squore Software Analytics

Build Phase

Code Analysis

Test Activities

Quality Control

Source Code

Repository

Source Code Update

AutomaticTrigger

Real Time access

Continuous Quality– CI/CD

MISRA 26262

25010

Share with customer

CMMI / SPICE

HIS

Tasks to developBug Tracker

6

1. A dashboard for automotive Standard

2. Introduction to Squore

3. Demo and Use Cases

Agenda

7

Web-Based Application ServerIntegrated with development environment

Squore Overview

Squore Software Analytics

Squore Solution embeds:

A Static Code Analyzer for several languages (C/C++, Ada, Python, Java…)

A Data Import API

A KPI Engine

A Business Intelligence Plateform

Static Code Analyzer

KPI Engine Business Intelligence Platform

Data Collection API

8

SQUORE in action

Squore Software Analytics

8

Co

llect

an

d

Org

an

ise

Assess

an

d

An

aly

se

Mon

ito

r

an

d S

hare

Project monitoring

Decision making

Cloning

ISO25010

ISO26262

HIS MISRA

Standard Compliance

Source Tests Tickets Design

DO178

Complexity

Automated Reports

Role-BasedAction Plan

Milestones/Goals

Simulink

Scade

Jira

Mantis

JUnit

CAST/Cover

. . .

CAST/C++

Self descriptiveness

Test Effectiveness

Aggregated IndicatorsStandards

Monitoring Features

Trend Analysis

. . .. . .

Others

Excel

SAP

. . .

SQUAN

Data

Business

BI

GitLabJenkins

Cont. Integration

Traceability

Reqs.

REQIf

Excel

. . .

Real-time

CorporateKPI

Automate

CorporateStandards

. . .

9

Using Squore during the development process

Squore Software Analytics

Build Phase

Code Analysis

Test Activities

Quality Control

Source Code

Repository

Source Code Update

AutomaticTrigger

Real Time access

Continuous Quality– CI/CD

MISRA 26262

25010

Share with customer

CMMI / SPICE

HIS

Tasks to developBug Tracker

10

1. A dashboard for automotive Standard

2. Introduction to Squore

3. Demo and Use Cases

Agenda

11

Use Case 1: Defining the delivery process

Squore Software Analytics

A sample based on HIS Metrics:

HIS metrics thresholds can be tunedaccording to customer expectations

HIS Compliance indicators are aggregatedat project level

HIS Compliance can be shared via a live access or via a generated document (Pdf, PPT, Excel…)

Note:

This will work the same with other indicators: MISRA, Code Coverage , Cloning …

Assess HIS Compliance

Assess Custom HIS Compliance

12

Use Case 2: Driving project to quality objectives

Squore Software Analytics

Sample based on Technical Debt:

Quantify the non-quality in the application according ISO25010 quality breakdown

Apply BI techniques to efficiently focus on relevant Code:

> ASIL Critical

> Recently updated code

Track Technical Debt trend

13

Use Case 3: Minimizing risk with a customized test strategy

Squore Software Analytics

Optimize the test activities:

Import ASIL from requirement analysis

Define code coverage expectations per safety level

Customize list of modules to test based on:> Module Complexity

> Code Stability

> Coverage results

> Criticity

Assess Code Coverage compliance per Safety Level

Coverage Threshold Settings

14 © 2018. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.1 | 2018-10-18

Author:

Vector Germany

For more information about Vectorand our products please visit

www.vector.com