Vector integrates Autosar extensions into PREEvision development platform

February 14, 2013 // By Christoph Hammerschmidt
Besides handling requirements management, hazards and risk analysis (ISO 26262), the new PREEvision 6.0 version from Vector now also includes functions for designing Autosar architectures.

The new release 6.0 of Vector's automotive E/E architecture development tool PREEvision. This release offers significant productivity improvements, from requirements handling and extending to the logical architecture level, the hardware and software levels and finally the physical implemetation. Many new functions have been implemented in Version 6.0 for developing Autosar ECUs.

In the new version, Autosar system descriptions can be created which include the internal behavior of software components. PREEvision supports exporting these system descriptions which are extracted from the ECU. These components and their containers can be individually updated based on a system or software component description. This simplifies data exchange (round-trip) between PREEvision and other Autosar tools from Vector and third party suppliers. PREEvision can be used to define and model time-critical modes of behavior, e.g. behaviors that might slow down the exchange of information.

Another component of the tool is the PREEvision Collaboration Platform, which facilitates teamwork with distributed competences in model-based systems engineering. Its common data storage extends across tool boundaries and offers quick access to all engineering data related to the architecture and production development. A new function is automatic procurement of access rights to avoid conflict situations. This enables simultaneous access the same artifact for multiple users, and it increases the speed and efficiency of E/E development processes.


For more information visit