Roadmap
The roadmap shall give an overview of the modifications and new features
that will be introduced to Artop in the future. The roadmap is divided in
three sections:
For an overview of the components that are available in the current Artop
release (Artop 2.0) please refer to the
Architecture section.
The roadmap is preliminary and is subject to change,
especially release dates may be aligned when AUTOSAR release schedules are
updated.
Model Query & Indexing
Mechanism to enable efficient model querying based on indices. These indices
will also enable editing of partially loaded models to avoid keeping entire
models in-memory.
Additional Editor Types
Support for GMF-based model editors and for spreadsheet and table-like
model editors.
ECU Configuration Validation Constraints
A standard set of predefined ready-to-use validation constraints for the ECU
configuration part of the AUTOSAR meta model.
BSW Module Configuration Initializer
Support for initializing a BSW module configuration out of a vendor specific
module cofiguration description.
Integration with Xpand
Integration of the XPand template engine to simplify code generation out of
Artop.
Here topics are listed were development within Artop is ongoing during the
current Artop release cycle. For these topics first implementations have
been created but these are not yet ready to be part of an actual Artop
release.
Model Database Persistence
Another alternative to XML storage is to use a relational database to store
AUTOSAR models. Such a database can be used to efficiently handle large
models.
Code Generation
An engine which allows to easily generate code based on AUTOSAR models as
the input. The engine also provides APIs to easily access AUTOSAR models out
of source code templates, including the basic software (BSW) configuration.
Model Search & Replace
Provide a mechanism to search through AUTOSAR models on an abstract level,
also with the possibility to replace matched values.
Model Transformation
Adaptation of existing model transformation approaches to the AUTOSAR
domain, e.g. the ATLAS Transformation Language or openArchitectureWare
XTend.
Command Line Interface
Allow batch mode processing of AUTOSAR models via a command line interface
to allow access to Artop features in an automated way. Examples for such
features are code generation and model validation.
Model Refactoring
Provide a mechanism which can be used to refactor AUTOSAR models, for
example that enables to move AUTOSAR elements in an automated way.
Model Release Converters
This components provides converters that allow the conversion of AUTOSAR
models between different AUTOSAR releases, e.g. from 2.1 to 3.0.
Dynamic Scripting
Adds scripting capabilities to Artop that allows the user to automate
repetitive tasks by using a scripting language, that can conveniently access
AUTOSAR models and other Artop functionalities like validation or
transformation.
