Established for more than two decades as the standard tool for developing and testing ECUs and systems in the automotive sector, CANoe has had to face up to the rapidly changing requirements of the automotive electronics market. One of the most important new requirements is support for service-oriented communication. CANoe thus also supports applications with service-oriented architectures (SOA).
The advantage: classical and service-oriented modes of operation are possible in parallel. Users who have already been successfully using CANoe for years will continue with their usual work process. In addition, users implementing SOA projects, such as Autosar Adaptive, are equally supported by CANoe 14.
At least for the automotive market, the focus of the systems to be tested is increasingly shifting away from real ECUs to pure software systems. Here, software interfaces are more likely to be used than classic bus accesses. Thus, with the new communication concept, CANoe is also becoming interesting for applications outside the automotive market, such as in medical technology or in areas of Industry 4.0 - in other words, in all applications of the IoT world where software has to be tested.
Continuous Integration (CI) is a widely used method to increase the quality of software. A characteristic of a CI workflow is to test program codes frequently and automatically at an early stage. CANoe 14 supports this workflow by simplifying the integration of the deployment of the rest of the system and the execution of automated tests into a CI tool chain. For users, access to the CI methodology means significantly more flexibility when simulating and testing in purely simulated flow environments, as they can now also work on a server or in a cloud.