A textual representation of an AUTOSAR model brings several benefits with respect to readability, understandability. Due to the textual nature of the format, you will be able to fully take advantage of the well established tools, for instance source, version and change control.

In addition to these support tools, the ARText languages are supported through various features that textual editors bring such as syntax highlighting, syntax proposals, syntax completion, and syntax templates.

In addition, AUTOSAR users, especially developers who are more inclined to textual formats will benefit from a less steep learning curve to developing AUTOSAR models with ARText languages.
The intention of the ARText languages are to only support a frequently used subset of the AUTOSAR standard and not to support all features of all AUTOSAR templates, as this requirement has already been fulfilled through AUTOSAR XML (ARXML). ARText languages instead address a different aspect - the model development process.

It is the goal of ARText to bring maximal benefit to the greatest number of AUTOSAR users by supporting commonly used parts of the AUTOSAR templates. The benefits arise from a succinct textual syntax that will improve development speed, readability, communication and collaboration efforts.

Elements that are not supported by ARText are therefore defined in ARXML. These two formats together produce a merged, comprehensive view of the AUTOSAR system. This is possible due to ARText's ability to fully integrate the languages to interact with ARXML.
The ARText languages are not part of the AUTOSAR Standard, however its goals are to assist with model development and to provide a readable and understandable representation of AUTOSAR models.
The ARText languages and the ARXML format are compatible with the ability to reference each other's AUTOSAR elements. For instance, an element defined in an ARText language will be able to reference elements defined in ARXML and vice versa. This allows developers to mix these two file formats in an AUTOSAR project. However, these ARText languages will not replace the ARXML format as an exchange format. Instead, models specified in ARText languages will be translatable into the ARXML format to support the exchange based on the standard XML format.
A succinct textual language will also bring simplifications in model development and save development time. The grammar elements defined in the ARText languages will provide "short cuts" in defining elements that are more time intensive to create. This results in developers saving time in model development, whilst also having a clear, readable and understandable representation to collaborate with.
The software component language has undergone serveral releases and the is now mature with a stable syntax.
There are no risks involved in defining your AUTOSAR model with ARText languages, as all ARText language files can be transformed into its equivalent AUTOSAR XML format.
Feel free to contact us at with this feature request. ARText languages evolve through their user's needs. We need your input!