We offer Qualification Support Kits (QSKs) that let you simplify and automate the qualification process considerably. Notably in the automotive and avionics industries, the QSKs are quite popular with our customers.
Each QSK contains three major parts: a Report Package, a Test Package, and a QSLCD Report.
The Report Package consists of an Operational Requirements Report and a Verification Test Plan. The Requirements Report lists all functional requirements of the tool to be qualified. For each requirement, the Verification Test Plan describes one or several test cases that should give confidence about the correct functional behavior of the tool.
The reports are generated in HTML, enabling easy integration into your certification documents. Both reports are templates, so you need to edit a few things according to your usage of the tool. For example, you have to specify the compiler switches used to generate the executables analyzed by the tool.
The Test Package contains all test cases listed in the Verification Test Plan. This framework provides scripts to execute all test cases and evaluate the results. The evaluation result is printed so that you can attach it to your certification document.
The package can be easily extended with your own test cases to also cover your operational environment.
The QSLCD Report documents AbsInt’s internal development processes, including all verification and quality assurance activities.
QSKs are currently available for
|WCET analysis||Stack usage analysis|
Tasking VX 2.4r1
|✓||Tasking VX 2.4r1
Tasking VX 3.1r2
|M68020||✓||GCC 4.2.1||✓||GCC 4.2.1|
|IBM PPC750||✓||DiabData 4.4||✗||✗|
|TriCore||✓||HighTec GCC 220.127.116.11||✓||✗|
Generic QSKs perform checks on call-graph and control-flow-graph level using ELF executables created with a generic C compiler of our choosing, e.g. a popular version of the GCC. Compiler-specific QSKs are optional add-ons that provide additional test cases compiled with the specific compiler in question.
Generic QSKs are typically sufficient for certification, but compiler-specific QSKs can become mandatory depending on the nature of your application and the certification authority you have to report to.
More QSKs are under development at any given time, and other processors or compilers can always be covered on request. Contact us for further information.