How can I create the needed millions of scenarios?
How can I avoid the test explosion problem?
How can I find out if my tests are passed or failed?
How can I create the needed millions of scenarios?
How can I avoid the test explosion problem?
How can I find out if my tests are passed or failed?
Compliant and certified
The trend of increasing complexity of E/E Systems and shortened development cycles presents a clear challenge in the selection of appropriate development methods and tools. By providing recommendations and processes for the development of safety-related systems, the ISO 26262 standard allows first of all a classification of functions of E/E systems as more or less safety critical (=ASIL levels). It likewise gives recommendations regarding corresponding, state-of-the art methods for development and testing. Over the past years, this has become a de facto standard in the automotive industry for development of safety critical applications.
Relevant methods for developing and testing software are described in part 6 of the standard. Within the different verification methods, Requirement-Based Testing for example, allows demonstration that the software unit fulfils specified requirements and is highly recommended for all ASIL levels. Another important testing goal is to guaranty the robustness of the software unit: the absence of undesired functionally or the sufficient hardware resources to run the software unit can be verified using methods like interface testing, fault-injection testing and resource testing. In regards to model-based development and additionally to other testing methods, the comparison between the model and automatically generated code is necessary to ensure that they behave equivalently to the test objectives.
The completeness of testing activities cannot be evaluated without measuring structural coverage of the software unit. That is why ISO 26262 specifies relevant metrics like statement, decision or MC/DC coverage to be measured in order to establish sufficient confidence in coverage at the software unit level.
To comply with safety-critical functions according to ASIL C or ASIL D, it is also recommended to consider formal methods that help obtain a high degree of confidence regarding a reliable system behavior. While using a formal notation within the software specification process, the computer will be able to understand the meaning of the requirements and will therefore offer advanced verification techniques including proof of complete integrity of the requirements.
With BTC EmbeddedPlatform, BTC Embedded Systems addresses the different verification objectives recommended by ISO 26262 in a complete tool chain within a single and consistent platform that allows alternating from one verification use case to another.
BTC EmbeddedPlatform has been certified by German TÜV Süd as fit for usage in safety critical software development projects.
The certificate addresses different standards including IEC 61508-3:3010, ISO 26262, EN 50128, IEC 62304 as well as ISO 25119. For the automotive standard ISO 26262, the certificate is valid for all ASIL levels including ASIL D. As a verification tool, BTC EmbeddedTester has been classified with the highest tool confidence level of TCL 3.
We provide the certificate and the corresponding report to our customers free of charge upon request, which drmatically reduces or even eliminates any effort for tool qualification measures on the customer side.
Smart test generation for an ISO 26262 certified and fully automated Back-to-Back Test
Wir entwickeln automatisierte und intelligente Test Lösungen, welche unseren Kunden weltweit dabei helfen, eine hohe Software Qualität im Einklang mit dem ISO 26262 Standard zu erreichen
