Formal Test Package
BTC EmbeddedPlatform - Formal Test Package, the verification of safety critical requirements is taken to a whole new level. Safety requirements are formalized by an intuitive requirements formalization language called "Simplified Universal Pattern" and transformed to machine readable requirements.
It shows if each requirement is violated by any of the test cases executed on BTC EmbeddedPlatform. Additionally, the formal requirements bring a meaningful and smart definition of requirement coverage based on its internal structure. This allows you to easily assure that all requirements are fully tested.
Automatic Requirements-based Test Generation
Test cases which covers formal requirements coverage can automatically be generated.
Smart and powerful test authoring
Formal Test Package provides a powerful editor for functional test cases. In contrast to generic editors like Excel, the editor knows all details about the test architecture and protects users against invalid data entry. Further features include a signal generator, a graphical viewer, flexible tolerance handling and verdict functions. You can run test cases directly within the editor, allowing you to visualize the results.
Coverage on all levels
For ensuring completeness within a requirements-based testing workflow, different coverage metrics should be measured and documented. While this usually requires a combination of various tools and scripts, Formal Test Package centralizes the analysis for requirement model and code coverage within one user interface. Code coverage is calculated automatically in the background, so that no instrumentation is needed during the simulation of the production code.
Integrated with your development tools
Formal Test Package provides you a tight integration with Simulink and TargetLink, making it the perfect tool for the test of models and production code. For larger models, sub-functions can be tested independently without the need for model modification.
A direct connection to requirements management tools like IBM DOORS, PTC Integrity or dSPACE SYNECT ensures reliable traceability of requirements while avoiding error prone exchange formats like Excel. Test cases can be imported/exported in various formats including Excel, MAT, XML, SignalBuilder or MDF. Additional formats can be easily integrated via a plugin mechanism.
If a test case is failed, Formal Test Package allows exporting a corresponding debug environment. This can be done either as a Simulink/TargetLink model, or as a Microsoft Visual Studio project. In both cases, the debug environment is self-contained making it easy to exchange with colleagues or 3rd parties