Published on December 06, 2019.

Release of BTC EmbeddedPlatform 2.5

The new release BTC EmbeddedPlatform 2.5 (incl. BTC EmbeddedTester 4.5) is now available. Highlights of this release include:

       1. Calibration variants

This brand new feature provides the capability to run one test case multiple times with different sets of calibrations. Calibration variants can be manually created or imported and are centrally managed within the test project.  It is then possible to assign a certain number of calibration sets to a test case and run them all at the same time on MIL, SIL and PIL.

       2. Improved Enumerations handling

For an even more intuitive test authoring, BTC TestComposer (part of BTC EmbeddedTester) now provides drop down menus to assign enumeration values. The list of available enumeration values per signal is automatically extracted from the Simulink model and is also taken into account during automatic test generation and formal verification.

       3. Support for Simulink Embedded Coder®

In addition to Simulink models, dSPACE TargetLink models and handwritten C-Code,  Embedded Coder models are also supported with thsi release. This allows to creation of a test project which can address the Simulink model level (MIL) as well as the production code generated from Embedded Coder (SIL).  A special wizard allows checking and configuration of the mapping between model blocks and code elements. All use cases supported by BTC EmbeddedPlatform are also available for Embedded Coder, incl. code coverage analysis, automatic test generation and formal verification.

       4. New Use Case: Requirements Analysis

The new "Requirements Analysis" Addon provides different methods to verify the consistency, correctness and completeness of your safety requirements.

The consistency checks ensure that a set of requirements doesn't contain any contradictions.

Our definition of correctness implies the requirement represents the intended functionality.  This can be analysed by creating test data and executing it on the requirement, we could also call it "Requirements-in-the-Loop Simulation". 

Our definition of completeness implies a given set of requirements always leads to a defined output bevavior for any kind of input data.

These three methods enable the user to increase the requirements quality in a very early project stage. This addional effort can significantly reduce the misunderstandings and functional issues during development and testing, leading to a more efficient process.

       5. User-Defined Architecture

It is now possible to create a profile independantly from a concrete system-under-test (e.g. Simulink/TargetLink model). With a user-defined architecture, many use cases can be performed during the beginning project phases where no implementation is available.  This includes for example formal specification of safety requirements and requirements analysis (see above).

       6. Interactive Testing

This new feature allows the user to open a test case in BTC TestComposer and the corresponding Simulink model in parallel providing faster iterations and enhanced test driven development. Small changes in either situation can be recognized almost immediatly.

       7. Model Coverage Reporting during MIL Simulation

While in previous releases the Model Coverage measurement triggered an independant execution of the model, it is now also possible to generate a Model Coverage report during the execution of a MIL simulation.  Model Coverage metrics are based on the toolbox "Simulink Check" which requires a dedicated license from TheMathworks.

       8. Merge Multiple reports into combined report

It is now possible to generate one high-level summary report by merging different independant reports (e.g. code coverage, model coverage, test execution, back-to-back report, interface report etc.)