Industrial Automation Software Solutions

Parasoft minimizes the cost of the coding standards compliance process by providing dedicated reporting. Compliance reporting gives the user a dynamic view into the compliance process, helping prioritize results of static analysis violations according to groupings and categorizations from the original coding standard.

Compliance documentation is necessary for proving compliance. Generating it automatically saves teams valuable time when the generated reports and documentation comply with the MISRA 2016 standard, which is very popular across automation industries.

Parasoft C/C++test detects complex runtime-like problems early in the development stage by analyzing execution paths through the code and finding potential bugs. In addition to 2200+ rules and checkers, Parasoft makes it easy for teams to verify organization-specific coding guidelines with a special editor for creating custom checkers to extend (or replace) the built-in rules provided with the tool. With Parasoft C/C++test, users don’t have to write any scripts, and organization-specific coding guidelines can be fully automated to replace the manual process of compliance verification.

Parasoft C/C++test’s convenient views and graphical editors reduce the manual effort of unit test case creation and maintenance with a unit testing framework designed with safety-critical software testing in mind. Stubs and test cases with values for tested software’s stimulation can be created as a source code or with graphical editors with source code generation capabilities. Users can store and review created test artifacts together with the project’s files. The initialization of the variables and input parameters for tested software stimulation is done in exactly the same way as during production software operation, making the method reliable and robust.

Unit testing is much easier and productive if used together with a stubbing/mocking framework. Parasoft C/C++test’s powerful module for creating stubs and mocks help in fault injection testing, reduce dependencies of the tested code, and enable users to easily stub out not yet implemented source code.

Parasoft C/C++test supports all the coverage metrics typically required when developing safety-critical software (statement, branch, MC/DC, function, call, path, simple condition, line, and block), displaying code coverage results from all levels of testing, including unit, integration, and system level testing.

C/C++test reduces the time required to analyze coverage results and find the gaps in the testing process. Developers can review code coverage results inside the IDE with dynamic views and filter the results depending on metric, function/method, or specific test case.

Parasoft integrates with requirements management systems to provide traceability reports that display the correlation between requirements and the following:

• Source code created to implement these requirements.
• Test cases created to test the requirements.
• Results of executed tests.
• Code coverage results.

Traceability reports provide clear and complete information about the development progress. Teams can easily determine how many requirements were already implemented and how thoroughly they are tested.

Parasoft C/C++test can be integrated with model-based development tools like Matlab/Simulink or IBM Rational Rhapsody, verifying the source code generated from the models for compliance with the coding standards and performing dynamic validation using data sets from the simulation engines, and then presenting code coverage results.

Parasoft C/C++test is certified by TÜV SÜD as suitable for use when developing safety critical software with the IEC 61508 standard. For projects with a higher level of risk, Parasoft C/C++test’s Qualification Kit automates a significant part of the tool qualification process, reducing the amount of manual work and eliminating this distraction from software teams.

A dedicated Qualification Support Tool guides users through all of the steps required to qualify the tool, automating the majority of the tedious manual work required to qualify the tool, including executing the test cases from the exhaustive test suite provided together with the Qualification Kit, and generation of the final reports required to document the qualification process.