Presenters: Nabile Khoury and Thabo Krick of BTC Embedded Systems AG
Standards like ISO 26262 for the development of safety critical systems in the automotive domain require to manage traceability between different types of artifacts in the development process. This traceability is in particular important when it comes to requirements and test cases, so that the following questions can be answered with confidence and accuracy at any project stage:
a. Did we create test cases for every requirement?
b. Which requirement(s) is/are covered by a particular test case?
c. Are there requirements which are not correctly implemented by the software?
One option to connect the different tools could be the use of exchange formats like Excel or ReqIf. But especially as todays embedded software development projects become more agile, these exchange formats are inefficient and error prone, as they introduce many manual import/export which can’t guarentee the consistency of the data.
To solve this problem, IBM has introduced the OSLC standard as part of the IBM Engineering solutions, which allows different development and verification tools to communicate directly with “IBM Engineering Test Management” and “IBM Engineering Requirements Management DOORS Next”.
We will show you how to efficiently perform an ISO 26262 compliant software test within a Model-based development process ensuring full traceability between requirements, test cases and test results.