Develop and Test Software of Distributed Systems with CANoe4SW

CANoe4SW is the comprehensive tool for development, test, and analysis of software in cyber physical systems — individual software components as well as subsystems and entire distributed systems. CANoe4SW supports software developers and testers in all markets (medical, railway, automotive, …) throughout the entire development process of distributed systems and IoT devices. Virtual execution environments on the computer, in virtual machines, or in the cloud enable software to be tested for any targeted OS based on Windows or Linux, e.g., Ubuntu, CentOS, SUSE.

The System Under Test is accessed by its functional system interfaces at a pure software level. This enables early “black-box” SIL testing independently of hardware availability. CANoe4SW integrates seamlessly in CI/CT environments.

In addition, the support of connectivity protocols such as MQTT provides access to IoT devices and back end software running in the cloud.

Advantages

Interactively develop and test distributed systems
Easily automate tests to ensure quality at a system-level
Divide and conquer the system
by isolating single components using models for both physical and software environments
Test early in the development process
by utilizing virtual execution environments
Cover dynamic aspects of the software under test
by stimulating and monitoring value curves over time
Simulate failure scenarios
not easy to be covered in real environments, e.g. downtime of cloud services
Utilize CI/CT environments
right from the beginning by being independent of hardware and other software components

Application Areas

Monitoring over Time

Monitoring over time fully integrated software components: Run your software under test asynchronously in virtual execution environments. Observe dynamic aspects while stimulating the application via its functional system interfaces at a software level.

Environment Simulation

Environment simulation by models: Build a “natural ecosystem” for your software under test. Simulate both physical and software environments. Test single software components in isolation before integrating into subsystems.

Interactive Development and Test

Interactive development and test in an exploratory way: Stimulate the software under test using panels, waveform generators, and scripts. Analyze the reaction of your application and value relations via graphical and text-based analysis windows.

Automated Testing

Automated testing with the test design tool vTESTstudio: Leverage the flexibility of various test design methods such as graphical diagrams and tabular sequences. Benefit from flexible parametrization concepts and universal variant support. Ensure traceability from requirements to test cases and results.

Debugging

Debugging on the host: Profit from the power to debug in the development environment rather than on the target. Observe application behavior, view and modify internal variables, watch call stacks, etc. while stimulating the application via interactive or automated tests.

Test of IoT Applications

Connectivity Features Service

The Connectivity Features Service allows you to easily connect your System Under Test (pure software or a real device) to a back end or local broker. MQTT is already supported, further protocols are planned.

For more details, see Connectivity Features Service for IoT

Interfaces to 3rd-Party Tools

Open Environment

CANoe4SW supports the integration of other tools via open interfaces and various well-established standards.

An interface to MATLAB/Simulink enables model in the loop tests as well as the simulation of MATLAB models. FMI (Functional Mock-up Interface) is as a tool-independent standard to exchange models or to establish tool couplings.

Open APIs allow 3^rd-party tools to exchange simulation values with CANoe4SW and to control the overall simulation as well as the automated test execution.

The integration with various test management systems ensures traceability from requirements and test specifications to test cases and test results.

Supported Software

Platforms, Programming Languages, and Protocols

Any Windows or Linux based platform is supported. The software under test can be executed on the same PC as CANoe4SW, a virtual machine or a remote host. The supported programming languages are currently C and C++. Support of further languages e.g. Python is planned.

The MQTT protocol allows access to IoT devices and back end software running in the cloud. Support of further IoT protocols e.g. AMQP is planned.

Server Environments

Continuous Integration and Test

Automated tests with CANoe4SW can easily be integrated into continuous integration and test environments using CANoe4Server. CANoe4Server is the virtual runtime for simulating and testing in a server environment under Windows or Linux.

MIL, SIL, HIL

Seamless Integration Into the Development Process

System setups and tests created with CANoe4SW can seamlessly be re-used in CANoe for hardware/software integration tests and system validation. This allows a consistent development and testing tool chain for MIL, SIL and HIL. The feature set of CANoe4SW is also available to all CANoe users. For further details please refer to CANoe.

Product Descriptions

プレビュー表示

Short overview of facts (PDF)

さらに表示

Here you will find the system requirements for the current version of CANoe4SW and information about which operating systems this version is compatible with.

Component	Recommendation	Minimum
CPU	Intel compatible Core i7 or comparable ≥ 3 GHz ≥ 4 cores	Intel compatible 2 GHz 2 cores
	CANoe4SW benefits from higher clock rates rather than higher number of cores.
Memory (RAM)	≥ 32 GB	8 GB
Hard disk space	≥ 20 GB SSD/NVMe	8 GB HD/SSD
	Depending on the options used and the operating system components.
Screen resolution	Full HD	1280×1024 pixels
Operating system*	Windows 10 64 bit (≥ version 1803)	Windows 10 64 bit (≥ version 1803) Windows 8.1 64 bit Windows 7 64 bit (≥ SP1)

_{* Not virtualized. Running in a virtual machine is possible but not tested. Operation with Vector hardware may be affected by virtualization, e.g., higher latencies may occur.}