Addressing ISO 26262 Compliance in Testing Automotive Software

Показать описание

The cost of achieving ISO 26262 compliance in software testing can be expensive. In this presentation, learn how to reduce costs through automating the multiple testing methods required by the standard to produce safe, secure, and reliable software.

Key takeaways:
• Apply static analysis for software safety and security.
• Expedite your unit testing with test automation.
• Understand the various structural code coverage options.
• Identify requirement traceability gaps in testing.

----------------------------------------------------------------

Parasoft C/C++test

PRODUCT TOUR | Take a Tour of Parasoft C/C++test

LIVE DEMO + Q&A

-----------------------------------------------------------------

VIDEO CHAPTERS
0:00 - 0:52 Introduction & Agenda
0:53 - 10:30 Introduction to ISO 26262
10:31 - 13:53 Part 6: Product Development: Software Level and Parasoft C/C++test
13:54 - 23:16 Addressing the Standard Through Static Analysis & Coding Standards
23:17 -30:22 SEI/CERT Secure Coding Guidelines
30:23 - 35:05 MISRA & AUTOSAR
35:06 - 38:50 Unit Testing in ISO 26262
38:51 - 39:58 Structural Code Coverage
39:59 - 41:13 Requirements Traceability
41:14 - 41:36 Closing Comments

__________________________________________________________

ADDITIONAL RESOURCES

EBOOK | ISO 26262 Software Compliance in the Automotive Industry

CASESTUDY | Renovo Balances Speed & Agility With Safety & Security in ADAS Development

Whitepaper | Satisfying SIL Requirements with Parasoft

WEBINAR | Better Together: Amplify Your Requirements Management Solution

________________________________________

BACKGROUND
ISO 26262, titled "Road vehicles — Functional safety", standard covers electrical and electronic automotive systems and their development process, including verification and validation. Part 6 of the standard specifically addresses product development at the software level and the multiple testing methods required by the standard.

Testing technologies like static analysis, unit testing, structural code coverage, and requirements traceability identify any gaps in testing to requirements.

Specific testing methods depend on the Automotive Safety Integrity Level (ASIL) classification of the system. To address safety and security from the get-go, MISRA C 2012, AUTOSAR C++14, CERT, or a custom hybrid are known to be used in achieving code quality across suppliers and primes.

__________________________________________________________

DO YOU HAVE MORE QUESTIONS?

Checkout more helpful content:

Want to stay connected? Find us on these platforms!

___________________________________________________________

ABOUT PARASOFT
Parasoft helps organizations continuously deliver quality software with its market-proven, integrated suite of automated software testing tools. Supporting the embedded, enterprise, and IoT markets, Parasoft’s technologies reduce the time, effort, and cost of delivering secure, reliable, and compliant software by integrating everything from deep code analysis and unit testing to web UI and API testing, plus service virtualization and complete code coverage, into the delivery pipeline. Bringing all this together, Parasoft’s award winning reporting and analytics dashboard delivers a centralized view of quality enabling organizations to deliver with confidence and succeed in today’s most strategic ecosystems and development initiatives — security, safety-critical, Agile, DevOps, and continuous testing.