Artop - autosar
Artop - autosar
Artop - autosar
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Artop</strong> - recent highlights and exploitation of the<br />
AUTOSAR tool platform in products and projects<br />
Michael Rudorfer (BMW Car IT), Mark Brörkens (OpenSynergy),<br />
Christian Knüchel (BMW Car IT), Stefan Voget (Continental Engineering),<br />
Stephan Eberle (See4Sys), Aldric Loyer (PSA Peugeot Citroen)<br />
AUTOSAR Open Conference<br />
2011-05-11, Frankfurt
2<br />
Overview.<br />
� <strong>Artop</strong> – a short introduction<br />
� Recent Highlights<br />
� Success Story at OpenSynergy
3<br />
<strong>Artop</strong> – the AUTOSAR tool platform.<br />
� The AUTOSAR Tool Platform (<strong>Artop</strong>) is an<br />
implementation of common base functionality<br />
for AUTOSAR development tools.<br />
� <strong>Artop</strong>‘s goal is to cooperatively develop the nondifferentiating<br />
base infrastructure in the community.<br />
This frees resources that each company can use<br />
to focus on its competitive features.<br />
� <strong>Artop</strong>, including its source code, is available free<br />
of charge to all AUTOSAR members and partners.<br />
<strong>Artop</strong><br />
� The <strong>Artop</strong> licenses are designed business-friendly and - in contrast to some open source<br />
licenses - make it easy to use <strong>Artop</strong> and build complete commercial products with it.<br />
� The <strong>Artop</strong> Platform is structured in a core project and several sub-projects. The<br />
subprojects are led by the main-contributors, not necessarily the design members.<br />
� Contributions to existing projects and proposals for new sub-projects are highly<br />
welcome.
4<br />
Recent Highlights (1/5).<br />
Growing community<br />
� In 2008: 4 Design Members (BMW, Continental, See4sys, PSA)<br />
� Today: 859 registered user from 133 companies (close to 100% of AUTOSAR<br />
companies)<br />
� Today: 4 Design members, 10 Contributing members
5<br />
Recent Highlights (2/5).<br />
More and more commercial products based on <strong>Artop</strong> available<br />
� Example: Cessar-CT and AUTOSAR Builder
6<br />
Recent Highlights (3/5).<br />
New subprojects<br />
� ARUnit: Infrastructure for unit testing of AUTOSAR components<br />
� ARText: Framework for defining textual DSLs for AUTOSAR<br />
� Formula Language<br />
� Timing language
7<br />
Recent Highlights (4/5).<br />
Eclipse migration<br />
� AUTOSAR related layer remains<br />
enclosed to the <strong>Artop</strong> User Group<br />
� AUTOSAR independent layer is<br />
migrated to Eclipse Sphinx project<br />
(open to general public, larger<br />
community)<br />
� http://www.eclipse.org/sphinx
8<br />
Recent Highlights (5/5).<br />
AUTOSAR 4.0 support<br />
� Support of the AUTOSAR 4.0 release<br />
� Concepts for handling new features (like variant handling, …)<br />
GAutosar<br />
� Release independent API for all AUTOSAR versions<br />
� Focus on heavily used parts of the metamodel<br />
Success stories<br />
� <strong>Artop</strong> is used in various companies for different use cases, i.e.<br />
� BMW series project on Timing Definition, BMW project AUTOSAR Styleguide Checker,<br />
BMW project PDM tool chain<br />
� OpenSynergy: COQOS Tools
9<br />
Example: OpenSynergy – COQOS - Short Overview<br />
Tool Chain<br />
e.g.<br />
Code<br />
Generators<br />
for AUTOSAR<br />
RTE and BSW<br />
Applications<br />
Real-Time<br />
Applications<br />
COQOS<br />
� COQOS is a scalable framework for automotive ECU's.<br />
Early<br />
Applications<br />
Main Head-Unit Processor<br />
� COQOS makes it possible to take full advantage of Linux and still satisfy typical<br />
automotive requirements.<br />
� With COQOS, e.g. Linux and real-time applications (such as AUTOSAR based<br />
applications) can run safely together on a shared hardware unit.
Example: OpenSynergy - initial COQOS Tools BEFORE <strong>Artop</strong><br />
� Lessons learned during initial implementation (2008-2009):<br />
� >50 % of development effort needed for non-differentiating base functionality<br />
� Deserialization of AUTOSAR XML<br />
� Metamodel<br />
RTE<br />
Gen<br />
OpenSynergy Tool Framework<br />
(deserialization, metamodel, etc.)<br />
Eclipse<br />
� Customization of Eclipse technologies for AUTOSAR<br />
� Additional effort was expected for:<br />
� Support of big AUTOSAR models (performance, memory consumption)<br />
� Support of multiple AUTOSAR releases and revisions<br />
BSW<br />
Gen
Example: OpenSynergy - COQOS Tools with ARTOP<br />
� Metamodel and Deserialization replaced by <strong>Artop</strong><br />
� This improved performance, memory consumption and maintainability<br />
� Additional <strong>Artop</strong> components integrated into COQOS tool development:<br />
� Build system<br />
� Test system<br />
RTE<br />
Gen<br />
BSW<br />
Gen<br />
OpenSynergy Tool Framework<br />
<strong>Artop</strong><br />
(deserialization, metamodel, etc.)<br />
Eclipse (EMF, QVTO, OAW)<br />
� Parts of the OpenSynergy Tool Framework contributed into the <strong>Artop</strong> community
Example: OpenSynergy - Experiences with <strong>Artop</strong> Technology and Community<br />
� Focus of development<br />
� moved to competitive features<br />
� Non-differentiating features<br />
� contributed into <strong>Artop</strong> framework<br />
� Very good support from active community<br />
� Development email list<br />
� Weekly telco<br />
� Direct contact to experts<br />
�<strong>Artop</strong> framework is mature and is a very good base for<br />
AUTOSAR development tools
Change language