how vectorcast supports aspice and iso 26262 · iso/iec/ieee 12207 [1995] iso/iec 15504 [2003-04]...

V1.0 | 2018-11-15

Vector TechDay – Software Testing with VectorCAST

How VectorCAST supports ASPICE and ISO 26262

3

u Software Development Processes

Tools to Support Software Development Processes

Mapping Process to VectorCAST

Mapping VectorCAST Features

Demo Application

Conclusion

Agenda

4

30 Years of Evolution

Software Development Processes

SEI[1988]

BOOTSTRAP[1994]

Trillium[1994]

Capability Maturity Model(CMM) [1998]

ISO/IEC/IEEE 12207[1995]

ISO/IEC 15504[2003-04]

Automotive SPICE v2.5

[2010]

Automotive SPICE v3.1

[2017]

Safety

Standards

IEC 61508Functional Safety

[1998]

IEC 61511Industrial[2004]

IEC 61513Nuclear[2011]

IEC 62061Machine[2005]

EN 50126/8/9Railways[2001]

ISO 26262Automotive

[2011]

ISO 26262Automotive

[Pending-2018]

DO178B/CAeronautics

[1992]

ECSSSpace (ESA)

[1993]

IEC 62304Medical[2006]

Note: [xxxx] is the initial release date

https://en.wikipedia.org/wiki/Trillium_Model

https://en.wikipedia.org/wiki/Capability_Maturity_Model

http://www.automotivespice.com/download/

http://www.automotivespice.com/download/

5

ISO 26262Road vehicles - Functional safety -Part 6:Product development at the software level

Automotive SPICE®

Process Reference ModelProcess Assessment Model


6

ISO 26262Automotive SPICE®

Large & Challenging


1 Part, 128 Pages 10 Parts, 486 Pages

Figure 1. Automotive SPICE v3.1 2017; Page 12 Figure 2. ISO 26262-6 2011; Page vii

7


u Tools to Support Software Development Processes



Demo Application

Conclusion

Agenda

8


Introducing PREEvision – E/E Architecture Development


u PREEvision supports the development of E/E architectures, including key process areas according to ASPICE

u Includes the Design of Safety Relevant Systems according to ISO 26262

9


Introducing VectorCAST


VectorCAST Supports

10

Introducing CANoe, vTESTstudio, VT System, & vVIRTUALtarget


System Validation

System Integration

Test

SWIntegration

Test

SW Unit Test

SWImplementation

So

ftw

are

Syste

m

White-Box testing on host / on target

Vecto

rCAST M

anage a

nd

Analy

tics

Benefits

u Full support in the development process, from SW unit test to system validation

u Uniform test management, test automation (CI),result analysis and traceability

Lin

k t

o R

equirem

ents

VectorCAST/C++VectorCAST/RSP

CANoe, vTESTstudio vVIRTUALtarget

VectorCAST/C++/QA

CANoe, vTESTstudioVT System

VectorCAST/QA

SW integration testing + code coverage

on PC

System validation+ code coverage

on ECUChange-Based Testing

11



u Mapping Process to VectorCAST


Demo Application

Conclusion

Agenda

12


Complete Process


1 Part, 128 Pages 10 Parts, 486 Pages

Figure 3. Automotive SPICE v3.1 2017; Page 12 Figure 4. ISO 26262-6 2011; Page vii

13


Software Development


Figure 5. Automotive SPICE v3.1 2017; Figure 6. ISO 26262-6 2011; Page vii

14


Refine Further


System

Software

Figure 7. Automotive SPICE v3.1 2017; Page 123 Figure 8. ISO 26262-6 2011; Page 5

15


Focus on Software


System

Software

Figure 9. Automotive SPICE v3.1 2017; Page 123 Figure 10. ISO 26262-6 2011; Page 5

16

Automotive SPICE® ISO 26262-6

5 Initiation of product development at the software level

SWE.1 Software Requirements Analysis 6 Specification of software safety requirements

SWE.2 Software Architectural Design 7 Software architectural design

SWE.3 Software Detailed Design and Unit Construction

8 Software unit design and implementation

SWE.4 Software Unit Verification 9 Software unit testing

SWE.5 Software Integration and Integration Test

10 Software integration and testing

SWE.6 Software Qualification Test 11 Verification of software safety requirements

Annex C Software configuration

Remarkably Similar


17

ISO 26262-6 VectorCAST Features

5 Initiation of product development at the software level Unit Testing System Testing Data Flow Static Data Flow Dynamic

Static Analysis Requirements Gateway Control Flow Static Control Flow Dynamic

6 Specification of software safety requirements Unit Testing System Testing Data Flow Static Data Flow Dynamic


7 Software architectural design Unit Testing System Testing Data Flow Static Data Flow Dynamic


8 Software unit design and implementation Unit Testing System Testing Data Flow Static Data Flow Dynamic


9 Software unit testing Unit Testing System Testing Data Flow Static Data Flow Dynamic


10 Software integration and testing Unit Testing System Testing Data Flow Static Data Flow Dynamic


11 Verification of software safety requirements Unit Testing System Testing Data Flow Static Data Flow Dynamic


Annex C Software configuration Unit Testing System Testing Data Flow Static Data Flow Dynamic


Harmonizing with ISO 26262-6


18




u Mapping VectorCAST Features

Demo Application

Conclusion

Agenda

19

u What we see at most customers is a software architect or safety manager role. The person(s) in this ‘role’ owns the responsibility to define, specify, develop, monitor, and improve the software development process

u The mapping will show how various features in VectorCAST could support your software development process

u The applicability of these features to your software development process will have to be evaluated independently

Preface


20

a b c d e f g h

T.1 UT, ST, SA

SA SA SA SA SA SA

5 Initiation of product development at the software level


Unit Testing (UT) System Testing (ST) Static Analysis (SA) Requirements Gateway (RGW) Data Flow Static (DFS) Data Flow Dynamic (DFD) Control Flow Static (CFS) Control Flow Dynamic (CFD)

22

7 Software architectural design (SWE.2)



a b c d e f g

T.2 UT, ST UT, ST

T.3 DFS, CFS UT, ST, SA

UT, SA, DFS, CFS

SA, CFS, DFS

CFS, DFS

T.4 UT UT UT, ST UT, ST UT, CFS UT, ST

T.5 UT, ST UT, ST UT, ST UT, ST

T.6 CFS DFS

23

8 Software unit design and implementation (SWE.3)



a b c d e f g h i j

T.7

T.8 UT, ST UT, ST, SA

UT, ST, DFD

SA UT, SA SA SA

T.9 UT, ST UT, ST, CFS, CFD

UT, ST, DFS, DFD

UT, ST, SA

24

9 Software unit testing (SWE.4)



a b c d e

T.10 UT, RGW UT UT UT UT

T.11 UT, RGW UT UT UT

T.12 UT UT UT

25

10 Software integration and testing (SWE.5)



a b c d e

T.13 UT, ST, RGW UT, ST UT, ST UT, ST UT, ST

T.14 UT, ST, RGW UT, ST UT, ST UT, ST

T.15 UT, ST UT, ST, CFD

26

11 Verification of software safety requirements (SWE.6)



a b c

T.16 UT, ST UT, ST UT, ST

27

Annex C Software configuration



a b c

C.1 UT, ST UT, ST UT, ST

28





u Demo Application

Conclusion

Agenda

29

MyECU

Demo Application

30

Configuring MyECU

Demo Application

MICROSAR SIP

Virtual ECU Integration

ECU Integration

Generate Code

.HEX

.DLL

.c/.hApplication source code

.c/.h

.c/.h

.c/.h

.c/.h

Dual-Target Configuration

SWC B

+ SIP Add-On VTT

DaVinci Configurator Pro

MCAL

OS

HW Module

VTT Module

Auto-sync of VTT modules

BSW

RTE

SWC B SWC B

31

Building MyECU

Demo Application

Other AUTOSAR tools2

Software Component Description Files

Contain software component information.

DaVinci Developer

DaVinci Configurator Pro

ECU Configuration Description File

Contains configuration information.

.arxml

.arxml.arxml.arxml

Other AUTOSAR tools3

Vector tool

3rd Party tool

1 ECU Extract, diagnostic data, etc.File formats: .arxml, .dbc, .ldf, .cdd, …

2 e.g. Embedded Coder, TargetLink3 e.g. 3rd Party MCAL configuration tool

Output vVIRTUALtarget Header and code files

u BSW module configuration

u RTE

.h

.c

VTT Project File

Contains project information, needed for MS VS solution generation.

.vttproj

vVIRTUALtarget basicMS VS Solution

u Static BSW code

u Generated BSW code

u SWC application code

u Startup, Hooks

.sln

MS Visual Studio

CANoe

Node layer DLL

Virtual ECU as DLL.dll

.dll.xvp

CANoe configuration

Contains configuration, panels and tests

.cfg

Input files1

Contain system, communication and diagnostic information.

Provided by OEM.

.arxml

SWC Source Code

u Platform independent implementation of SWCs

.h

.c

32

u Comfortable simulation environment with rich test feature set

u Simulation can be run “as fast as possible” to shorten test cycles

u Virtual ECUs can be tested

u with simulated bus

u with real bus and connected (real) ECUs, VT System, etc.

Running MyECU

Demo Application

PCCANoe

BSW

RTE

SWCA

SWCB

SWCC

VTT MCAL

VTTOS

Visual Studio

Test featureset

Bus Interface

debug

33

uLive Demo

Demo Application

34

Conclusion

VectorCAST can generate reports and artifacts to cover most of the software development processes in ASPICE and ISO-26262

u ASPICE SWE.1-6 and ISO-26262 Part 6 are remarkably similar

u Contact us to learn more details about how VectorCAST satisfies your software development process

u Consider using vVIRTUALtarget to start developing your AUTOSAR applications before your micro is selected

35 © 2018. Vector North America Inc. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 | 2018-11-15

Author:Krueger, KurtVector North America

More Information!Visit our Website for:> News> Products> Demo Software> Support> Workshops> Contact Addresses

www.vector.com

http://www.vector.com/

how vectorcast supports aspice and iso 26262 · iso/iec/ieee 12207 [1995] iso/iec 15504 [2003-04]...

Documents