-
The artshop model repository includes various tool adapters for tools from the automotive domain to import/export/change created documents within the framework. Custom views let the user navigate their documents like usual.
-
Imported model documents are stored within a database. This database can be queried and updated by artshop. The evolution of models imported to artshop can be traced via a build in model history. Once imported documents can be synchronized to their external sources if they should change.
-
Imported documents can be analysed either by user defined analyses or by pre-defined analyses that ship with the framework itself.
-
Analysis results can be associated with their respective models and also stored within the repository. Reports can also be generated from the result set of certain analyses.
artshop
The artshop model repository is a framework to manage software design artefacts in a central database. The key idea of this framework is the integration of software design artefacts created during standard model-based software development processes and perform a myriad of inter- and intra-artefact analyses. In its current version it supports basic auditing, traceability, variability, conformity and consistency management of a variety of software design artefact from the automotive domain.
The Eclipse Modeling Framework (EMF) is used as the foundation for the datastructures of the framework because of its formal object representation and the amount of technologies that build on top of it, e.g. the Epsilon framework and a multitude of repository techniques. The repository backend is based on the Connected Data Objects (CDO) framework, which supports a variety of database stores for easy exchangeability and basic support for auditing.
Architecture
To illustrate the architecture of the artshop model repository framework take note of the figure below which shows the current components integrated into the framework. The core represents the model repository and the implemented services which handle persisting and updating the loaded design artefacts. The interface to the tool environment is represented by the artconnect component which either establishes a direct connection to the supported integrated development environements (IDE) or plainly imports supplied model files. These components also include abstracted data models for the imported development artefacts which inherit certain properties from a superordinated metamodel. The management and analysis components directly plug into existing data formats and work on the previously mentioned metamodel. More information about the components of artshop can be found here.
Tool support
The artshop model repository framework currently supports the following software design artefacts from the automotive domain:
- Matlab-Simulink/Stateflow
- IBM Rational Doors (Formal modules)
- pure::variants (Feature models, family models, variant configurations)
Currently implemented analyses of the artshop model repository can be found here.
History
In 2012 Dr. rer. nat. Daniel Merschen started developing a database backed model analysis framework which first mainly focused on the analysis of Matlab Simulink models. This framework was later extended with additional software design artefacts like feature models from S2T2 Lero and requirements/test descriptions exported from IBM Rational Doors. In addition, techniques for traceability and variability management were introduced to the framework. In early 2013 a graphical user interface based on the Eclipse Rich Client Platform was created, where all techniques were pooled and accessible in an easy manner. After that techniques for change and dependency analysis were added to the framework, but it soon became apparent that the underlying technologies were not suited for such techniques and therefore a clean cut in the underying api was needed. The artshop team decided to move on to the next major version and rebuild the foundation of the model repository framework with new and emerging technologies.