Conferences and supporting programme
How to Efficiently Combine Test Methods for an Automated ISO 26262 Compliant Software Unit/Integration Test
The verification of embedded software in today’s development projects is becoming more and more a challenge. This is in particular true for the automotive industry, where we can observe a rapidly growing software complexity combined with shortened development cycles and an increasing number of safety critical applications. New methodologies like Model-based design or agile processes on one hand clearly help to make the development more efficient, on the other hand they even bring additional challenges related to the test process. One effect is for example, that tests need to be executed earlier and more often and due to the Model-based development approach on more execution levels like MIL/SIL/PIL. One more dimension of complexity comes from the fact, that one test method is not enough to get the necessary confidence regarding the correctness and robustness of the system-under-test. This conclusion is also part of several standards like ISO 26262, which recommend a combination of different test activities on model and code level. This paper presents a concept for an integrated verification platform for models and production code, which addresses the challenges explained above by focusing on three main aspects: integration, separation and automation. The integration aspect can be divided in two different approaches. First of all, the platform should be integrated with other development tools like modelling tool, requirements management tool or code generator. All information needed for the verification of a component should be extracted as automatically as possible, including information about interfaces, data types, data ranges, requirements or code files. As this kind of information is needed in a similar way for different verification methods, the second integration approach consists of integrating different test methodologies on top of a shared database within one environment. The first obvious benefit is, that the information described above needs to be extracted only once for all verification activities which can include guideline checking, static analysis, dynamic analysis and formal methods. We will also describe a second benefit coming from the fact, that these different methods deeply leverage from each other’s results. Separation means that software units shall be thoroughly verified before they are integrated into software components. Integrated components are then being verified according to the software architecture definition. The verification platform should support this divide and conquer approach as recommended and described in ISO 26262 or Automotive SPICE. One final topic to be discussed is automation, which should be made possible by a complete API as well as integration with technologies like Jenkins. The discussed verification platform approach automates many testing activities, from the more mundane activities to develop MBD and code centric test harnesses to the more sophisticating activities of automatic test generation.
--- Date: 01.03.2018 Time: 1:30 PM - 2:00 PM Location: Conference Counter NCC Ost