AUTOSAR (AUTomotive Open System Architecture) defines a standard software architecture for motor vehicles. This standard is intended to help manage the growing complexity of embedded electronic systems in motor vehicles.
The definition of the AUTOSAR standard gave birth to a set of complex specifications which are broken down into requirements, each of which may contain over 600 lower-level requirements.
So many demands adds to the complexity of their management at all levels of description of the AUTOSAR standard (SRS – SWS) and the applicability or not, of certain modules of the general and specific requirements.
AAT: AUTOSAR Authoring Tool
AAT is the creation and editing module for AUTOSAR applications.
It allows the development of the three templates for a fundamental standard description: Software Component (SWC), ECU resource, System Topology and messaging.
AAT has a graphics editor for creating the system application for composition, or even for creating new diagrams. An online rules checker gives the user ongoing assistance in the composition stage guaranteeing creations strictly conform to standard applications in the AUTOSAR version selected for the project.
EEX: ECU Extract
ART: AUTOSAR Retargeting Tool Automatic AUTOSAR code generation
Productivity gains made by the plug-in after AUTOSAR Builder are considerable. It allows automatic generation from models, of AUTOSAR-compliant C code, ready to be loaded into the target computer.
ASIM: Validation and Verification of AUTOSAR Systems for PC
The ASIM module of AUTOSAR Builder allows a single PC to validate and control the AUTOSAR systems created earlier in the development cycle, at Virtual Functional Bus (VFB) and ECU levels.
With the function level VFB ASIM, validation and verification of AUTOSAR software components is facilitated, regardless of any physical restraint or allocation on a specific network topology.
The goal is to validate the functional behavior of applications at the earliest, in a context of abstraction into three layers: interface definition, behavior definition and implementation definition. At the level of interface definition layer, validation and verification involve ports and interfaces of a software component communicating with other components of the same type and other basic underlying services.
At the behavioral layer, it is the “executable” in terms of real-time properties and execution semantics (scheduling and activation sources) that are subject to validation and verification. Finally at the implementation layer, validation and verification involve the consumption of resources.
SCVT: Software Component Conformance Validation Tool
The SCVT is for AUTOSAR applications. It allows the user to verify compliance with the AUTOSAR standard of descriptions of SWC-s, in AUTOSAR applications, and their associated code. It is based on the one hand on a rule engine and on the other on a static analysis tool. This last analyses the application code and RTE code generated for the application (Contract Phase). It gives the user analysis and validation reports on the application code.
GCE: Generic ECU Configuration Editor
GCE and its wizards allow the creation of configuration settings and configuration of AUTOSAR Basic Software (BSW), according to the system configuration methodology recommended by AUTOSAR.
AUTOSAR-RM is a separate plug-in built around Reqtify, the traceability management tool for Geensoft requirements. It helps the developer of AUTOSAR BSW modules to navigate the various documents of AUTOSAR specifications to extract requirements specifically and exclusively related to their software project. In fact, AUTOSAR RM will present them with requirements and these only, and allows them through Reqtify, to perform traceability on all stages of the project development cycle.
- Reduces AUTOSAR specifications handling phase
- Automatically extracts requirements for each project
- Manages the impact of future developments of AUTOSAR
- Increases confidence that the project complies with the requirements of the standard
List of modules
AUTOSAR-RM has a wide list of requirements modules in accordance with the contents of the AUTOSAR specifications and documentation. Geensoft offers special packages and modules. All modules can be purchased separately.
The list below is not exhaustive and a complete one may be provided on request. Please contact us for an updated list of modules.
- Basic Software Generic Requirements Package – WP1.1.2
- SPAL EEPROM Module – WP22.214.171.124.12
- Coupling of Graphical Development Tools to AUTOSAR – WP1.2
- SPAL FLASH Module – WP126.96.36.199.12
- Runtime Environment Module – WP188.8.131.52
- SPAL GPT Module – WP184.108.40.206.12
- CAN Module – WP220.127.116.11.1