Considerations in automotive embedded development Global Automotive Director Kiyo Uemura

Transcription

1 Considerations in automotive embedded development Global Automotive Director Kiyo Uemura

2 Agenda 1. IAR Systems Introduction 2. Background & ISO Software Development at the software level 4. Supporting Processes & Software tools 5. Summary

3 Future-proof software tools and services for embedded development, enabling companies worldwide to create the products of today and the innovations of tomorrow. Dedicated team of support, sales and service worldwide Large and loyal base of 46,000 customers 32% of revenue invested in R&D 2016 Sales 34M Operating profit 10M Net cash 10M Listed on NASDAQ Stockholm 34 years in the industry Uppsala Munich Paris Tokyo Seoul Shanghai Dallas Boston Los Angeles San Francisco + Distributor representation in 40+ countries

4 Background Complexity of Automotive Application Increasing Software Engineers at Automotive Industry are expected to follow ISO ISO is an automotive-specific international standard for functional safety of designing and testing products.

5 Overview of ISO 26262

6 Overview of ISO Product Development at the software level Supporting processes

7 ISO Part 6 Product Development at the software level

8 ISO Part 6 Product Development at the software level 6.6 Specification of Safety Software Requirement 6.11 Verification of software safety requirements 6.7 Software architectural design 6.10 Software integration and testing 6.8 Software unit design and implementation 6.9 Software Unit Design testing

9 6-7 Software Architectural design 6.6 Specification of Safety Software Requirement 6.11 Verification of software safety requirements 6.7 Software architectural design 6.10 Software integration and testing 6.8 Software unit design and implementation 6.9 Software Unit Design testing

10 6-7 Software Architectural design methods recemmended by ISO , Table 6 (requirment ) Method ASIL A B C D 1a Design walk-through ++ + o o 1b Design inspection c Simulation of Dynamic parts of design d Prototype generation o o e Formal verification o o + + 1f Control flow Analysis g Data flow Analysis ASIL : Automotive Safety Integrity Level = A risk classification scheme ++ The method is highly recommended for this ASIL + The method is recommended for this ASIL o The method has no recommendation for or against usage for this ASIL Without using a tool not easy to ensure the quality of your Software Architectural design method

11 6-7 Software Architectural design methods recemmended by ISO , Table 6 (requirment ) Method ASIL A B C D Visual State 1a Design walk-through ++ + o o Yes 1b Design inspection Yes 1c Simulation of Dynamic parts of design Yes 1d Prototype generation o o e Formal verification o o f Control flow Analysis Yes 1g Data flow Analysis ASIL : Automotive Safety Integrity Level ++ The method is highly recommended for this ASIL + The method is recommended for this ASIL o The method has no recommendation for or against usage for this ASIL Without using a tool not easy to ensure the quality of your Software Architectural design method

12 Solutions from IAR Systems State Machine Development Tool

13 IAR Visual State Set of tools for designing, testing and implementing embedded applications based on state machines. Build your design from a high level, structure complex applications, and step by step add functionality at a detailed level. Based on Unified Modeling Language (UML) state machine subset Generates very compact C/C++ code, 100% consistent with your design Advanced verification and validation tools

14 6-8 Software Unit design and implementation 6.6 Specification of Safety Software Requirement 6.11 Verification of software safety requirements 6.7 Software architectural design 6.10 Software integration and testing 6.8 Software unit design and implementation 6.9 Software Unit Design testing

15 6-8 Software Unit design and implementation : Coding Guide Topics to be covered by modeling and coding guidelines offered by ISO26262 Part6 ASIL A B C D Enforcement of low complexity Use of language subsets Enforcement of strong typing Use of defensive implementation techniques o Use of established design principles Use of unambiguous graphical representation Use of style guides Use of naming conventions Manual Review is no longer a perfect solution to ensure the quality of your code ASIL : Automotive Safety Integrity Level ++ The method is highly recommended for this ASIL + The method is recommended for this ASIL o The method has no recommendation for or against usage for this ASIL

16 6-8 Software Unit design and implementation : Coding Guide Topics to be covered by modeling and coding guidelines offered by ISO26262 Part6 ASIL A B C D C-STAT Enforcement of low complexity Use of language subsets Yes Enforcement of strong typing Yes Use of defensive implementation techniques o Yes, partly Use of established design principles Use of unambiguous graphical representation Use of style guides Use of naming conventions Manual Review is no longer a perfect solution to ensure the quality of your code ASIL : Automotive Safety Integrity Level ++ The method is highly recommended for this ASIL + The method is recommended for this ASIL o The method has no recommendation for or against usage for this ASIL

17 Solutions from IAR Systems Static Analysis: C-STAT

18 Static Analysis: C-STAT Checks compliance with MISRA C:2012 MISRA C++:2008 MISRA C:2004 CWE and CERT C/C++ (Includes ~250 checks mapping to 100 of issues) Extensive and detailed documentation Fully integrated with IAR Embedded Workbench

19 6-9 Software Unit testing, 6-10 Software integration and testing 6.6 Specification of Safety Software Requirement 6.11 Verification of software safety requirements 6.7 Software architectual design 6.10 Software integration and testing 6.8 Software unit design and implementation 6.9 Software Unit Design testing

20 6-9 Software Unit testing, 6-10 Software integration and testing Requirement The ISO standard requires software integration testing in a realistic target environment. Verifying embedded software according to ISO requires testing in a target environment while ensuring a high level of controllability and observability in the software. Need to have a tool which does not cause code overhead and speed penalty..

21 6-9 Software Unit testing, 6-10 Software integration and testing Requirement The ISO standard requires software integration testing in a realistic target environment. Verifying embedded software according to ISO requires testing in a target environment while ensuring a high level of controllability and observability in the software. C-RUN Yes Yes Need to have a tool which does not cause code overhead and speed penalty..

22 Solution from IAR Systems Dynamic Analysis: C-RUN

23 Dynamic Analysis: C-RUN C-RUN can perform following errors check; Heap and memory leaks checking Bounds checking Integer conversion failure Shift overflow Division by zero Minimized test code overhead and speed penalty Full Integration with IAR Embedded Workbench

24 8-11 Confidence in the use of software tools Supporting processes

25 8-11 Confidence in the use of software tools Requirement & Consideration ISO standards requires all tools used for the development process to be qualified Good to have a tool to be prequalified The amount of work for qualification of tools can be high, if the tools are not pre-qualified

26 8-11 Confidence in the use of software tools Requirement & Consideration ISO standards requires all tools used for the development process to be qualified IAR Embedded Workbench Functional Safety Version Qualified Good to have a tool to be prequalified The amount of work for qualification of tools can be high, if the tools are not pre-qualified Qualified

27 Solution from IAR Systems Functional Safety version of IAR Embedded Workbench

28 ISO certified tools A special functional safety version of IAR Embedded Workbench for ARM V IAR Embedded Workbench for RL78 V Certified for each ASIL (Automotive Safety Integrity Level) A-D of ISO without further tool qualification Guaranteed support through the product life cycle Prioritized support Validated service packs Regular reports of known problems The certification validates the quality of IAR Systems entire development processes, as well as the delivered software.

29 Summary of solutions from IAR Systems

30 Future proof your applications! Code Quality is the key success factor of your Automotive project. IAR Systems will support you to secure the code quality.

31 Want to learn more? Get scanned and get this presentation as PDF Get a demo of our latest news Thank you for your attention!

32 Thank you for your attention!