ASPICE compliant software development


Your introduction to explain how Automotive SPICE (Software Process Improvement and Capability dEtermination) influences how automotive software id designed, developed and tested

ASPICE and ISO 26262 in tandem


The overlap between Automotive SPICE (Software Process Improvement and Capability dEtermination) is clear and obvious. So how can they be applied simultaneously?

1

Automating Requirements Traceability


ALM tool provides, facilities for the careful management and monitoring of all aspects of software development, but rely on manual intervention to collate information on code development, verification and validation. 

Learn how that process can be automated using your ALM tool of choice.


2

As recognised by ASPICE, static analysis yields many benefits including checking for adherence to coding standards. Sometimes known as “language subsets”, coding standards aim to improve one or more of the portability, safety, and security aspects of a program by restricting those aspects of the chosen programming language mostly likely to cause problems in those areas

Getting to grips with 
MISRA C:2012


This document reflects LDRA's unique insight into the creation of MISRA C:2012, and into the incremental changes resulting from a policy of continuous improvement.

Leveraging
automated code
review with C++


This video shows the application of C++:2008 standard in the context of a functionally safe application.


Being compliant with
MISRA C/C++


This video gives a practical overview of what is required by the MISRA compliance:2020 document.

Address your
 insecurities with
CERT C


An introduction both to the CERT C standard, and the way in which automated tools can help achieve its objectives.
 


3

Dynamic analysis complements static analysis. It involves the compilation and execution of some or all of the code base to validate or verify its characteristics in practice. ASPICE requires compliant applications to be analysed dynamically.

Testing on target


Accessing the results presents the biggest single challenge in on-target testing. This video demonstrates the three most popular mechanisms; debugger script, file I/O and serial I/O.


Structural Code Coverage with MatLab Simulink


This video demonstrates the automation of code coverage analysis for source code auto generated using MathWorks MATLAB® Simulink®

Achieving functional safety with Eclipse and a Linux target


This video demonstrates how the structural coverage and unit test techniques demanded by ASPICE can be automated for a Linux target
 


4

Test Driven Development is increasingly popular in automotive application development, and the use of manual unit test frameworks is seeing a similar upturn in popularity in parallel. TDD can be achieved using a COTS application like the LDRA tool suite, or a manual unit test framework can be complemented by such a tool to achieve the code coverage required by ASPICE to show that tests are complete and traceable to requirements.

Test Driven Development


Read how Test Driven Development (TDD) can be achieved using a COTS tool such as the LDRA tool suite

Cross Platform Code Coverage with Catch2


This video discusses how code coverage can be achieved on ASPICE compliant projects, where manual unit tests that have been created using Catch2 

Cross Platform Code Coverage with CppUTest


This video discusses how code coverage can be achieved on ASPICE compliant projects, where manual unit tests that have been created using CppUTest

Cross Platform Code Coverage with Google Test


This video discusses how code coverage can be achieved on ASPICE compliant projects, where manual unit tests that have been created using Google Test (Gtest)

5

Improving confidence in
Software Of Unknown Pedigree (SOUP)

Not everyone has the luxury of working with code developed in accordance with clearly defined requirements, coding standards, a well-controlled development process, and a coherent test regime.

Learn how to leverage SOUP and remain in compliance with the principles of ASPICE


Customer Stories

Akihito Iwai 

DENSO

The LDRA tool suite is used as a benchmark for other third party and similar software platform products.

LDRA Is Here To Help


For more than 40 years, LDRA has developed and driven the market for software that automates code analysis and software testing for safety-, mission-, security-, and business-critical markets. Working with clients to achieve early error identification and elimination, and full compliance with industry standards, LDRA traces requirements through static and dynamic analysis to unit testing and verification for a wide variety of hardware and software platforms. Boasting a worldwide presence, LDRA has headquarters in the United Kingdom, United States, Germany, and India coupled with an extensive distributor network. For more information on the LDRA tool suite, please visit www.ldra.com

Our Customers

ISO 9001 | TÜV Certification

The TÜV and ISO certificates each say something a little different about LDRA and its products. ISO 9001 certification demonstrates LDRA’s ability to consistently meet and exceed customer expectations. And TÜV approval of software test tools suggests something more specific about the capabilities of the products, and their capacity to meet the exacting demands of the world’s predominant functional safety standards.