Argosim, the requirements validation company, is announcing a new release of STIMULUS, the first simulation tool to debug and test embedded systems requirements by combining Model-Based System Engineering (MBSE) with a unique Requirements-In-The-Loop (RIL) technology.
STIMULUS 2018 introduces new features that allow test engineers to build and automate requirements-driven test campaigns quickly by reusing previous work by system architects and designers. On one hand, system requirements that have been validated in STIMULUS by system architects can be reused as trusted test objectives by test engineers. On the other hand, co-simulation environments that have been defined in STIMULUS by designers, to check the code versus the requirements, can be reused as test environments. As a result, test engineers start with an operating test environment that they will complete with the necessary use cases required to test all the system requirements.
STIMULUS 2018 therefore removes all the manual and error-prone activities related to the creation and maintenance of test cases. Not only do test engineers stop spending hours interpreting system requirements and use cases to produce test vectors and test objectives but also, they stop rewriting and updating tests all along the development cycle, which is well known to be by far the costliest part of the product lifecycle.
In addition, STIMULUS 2018 brings effective answers to two of the most challenging and practical issues related to tests.
“Is my test campaign complete?”
During a test campaign, test engineers ensure that every requirement has been effectively tested, but the functional coverage of requirements cannot be easily measured, even by traceability tools. As a consequence, test engineers tend to write as many tests as possible, until the project is over.
STIMULUS 2018 provides the mechanism to measure the functional coverage of a test campaign as a simple percentage of covered requirements. You can also identify which requirements are still uncovered, and write specific test cases that will improve the global coverage. Conversely, you can identify which requirements are effectively covered by a given test case.
As a matter of fact, your test campaign is complete when STIMULUS indicates a 100% coverage of the requirements. No more danger of missing test cases.
“Is my system update still correct?”
When maintaining a system over time, many evolutions are likely to occur both in the specification and in the implementation. Most of the time, tests are also likely to become obsolete, and updating them may turn to a nightmare. Moreover, modifications usually cause some test cases to fail, and identifying the violated requirements is never trivial, especially when the test covers many requirements.
With STIMULUS 2018, modifications of the specification have no impact on the test campaign, since test vectors will be regenerated from the test cases and test objectives, or oracles, will be updated from the requirements. When a test fails, the violated requirements will be identified automatically and corresponding test cases will be rerun in the STIMULUS debugger to fix the problem.
Maintaining your tests becomes as easy as maintaining your specifications.
In conclusion, these new test automation features make STIMULUS 2018 the most efficient way of testing your embedded systems.