AUTOSAR Builder Tool Platform
AUTOSAR Builder is an Eclipse based platform which proposes a number of open-interface plug-ins corresponding to the different AUTOSAR design process phases and their required tasks. These plug-ins produce standard descriptions and information based on the AUTOSAR methodology while facilitating the contribution of each actor implementing a specific phase of the process.
They provide the functionalities such as:
To support the AUTOSAR process, Geensys’s AUTOSAR Builder provides an open Eclipse environment into which a suite of open-interface plug-in tools have been integrated. The AUTOSAR Builder plug-in tool suite addresses the successive steps in the different phases of the AUTOSAR design process and enables engineers to easily undertake the various associated design tasks. The AUTOSAR Builder plug-in tool suite includes an AUTOSAR Authoring Tool (AAT), ECU Extract, Software Component Conformance Validation Tool (SCVT), Generic ECU Configuration Editor (GCE) and AUTOSAR RM for AUTOSAR BSW requirement management.
The AUTOSAR Authoring Tool (AAT)
Based on a substantial subset of the AUTOSAR meta-model, the AAT facilitates the creation of AUTOSAR SW-C, ECU and System descriptions at the applications level. It represents the description data organized in templates and ARPackages. For each AUTOSAR element the properties are shown in Forms and the Graphical Editor allows the elements to be displayed as diagrams as well as enabling the creation of new elements. Rule checking of all standard descriptions for AUTOSAR systems with automatic error correction prevents engineers from entering inconsistent or invalid data and notifies them of potential or committed errors. The AAT provides practical assistance to the user to realize the tedious task of creating AUTOSAR standard descriptions.
![]() |
ECU Extract – is a companion feature of the AAT which allows the user to extract a single ECU specific description from the overall vehicle description, in complete compliance with the AUTOSAR methodology and specification.
The Software Component Conformance Validation Tool (SCVT) – Functioning at the applications level, the SCVT verifies the description of SW-Cs. It provides analysis based on description rules for SW-Cs, static analysis of application code and RTE code generated at the Contract Phase, verifying the coherence between SW-C descriptions and the associated code. It also provides reports on the analysis/validation of the code.
The Generic ECU Configuration Editor (GCE) – The GCE facilitates the creation and configuration of Basic Software module parameters based on the AUTOSAR standard and methodology. It ensures strict conformance to the AUTOSAR specification and validation of all AUTOSAR rules and requirements. The GCE is implemented as three separate plug-ins: The ECU Parameter Definition (EPD) plug-in is used to create or modify ECU parameter definitions; it can also be used to create xml format parameter definitions for any other software module other than AUTOSAR BSW; the BSW Module Description (BMD) plug-in is used to create or modify BSW module definitions and configurations, by BSW vendors; and the ECU Parameter Configuration (EPC) plug-in is used to create or modify ECU parameter configurations and to integrate BSW module configurations, by system integrators.
AUTOSAR
RM
The AUTOSAR standard definition contains a powerful and complex set of specification
documents which are divided in many more requirements: each of them can contain
up to 600 requirements. In addition, managing multi-level requirements together
with their generic and specific applicability increases the complexity of aggregating
the right set of requirements for a given software module development.
AUTOSAR-RM is a dedicated plug-in built upon Geensys’s requirement management tool Reqtify; AUTOSAR-RM helps navigate the multi-level, highly populated, AUTOSAR requirements. Furthermore, it extracts and consolidates - for a dedicated AUTOSAR development project - the requirements, and only those, which are mandatorily relevant to the project. Next steps in the requirement management process are fulfilled by Reqtify which ensures traceability automation, coverage assessment and impact analysis of requirement changes along the entire development cycle.