Skip to main content
Jump to: navigation, search

Difference between revisions of "Auto IWG"

(Meetings and Activities)
(Objectives)
 
(95 intermediate revisions by 10 users not shown)
Line 1: Line 1:
This is the starting page for the Automotive Industry Working Group at Eclipse.
+
'''Open Source Initiative for Automotive Software Development Tools'''
 +
 
 +
''' This Working Group is no longer active. Content is kept for historical reason '''
 +
 
  
 
== Objectives ==
 
== Objectives ==
 +
 +
Innovation in the automotive industry is mostly achieved by electronics and software functions.  The system automobile is becoming increasingly complex, an open developer tool workbench that extends throughout the supply-chain is becoming a must for the industry.  Improvements and innovations to these software development tools are required to accelerate product development, create high quality software features and improve integration across the automotive supply chain.
 +
 +
The Eclipse Foundation is pleased to announce the creation of a new open source initiative to define and implement a standard platform for the software development tools used in the automotive industry. The new Eclipse Automotive Working Group will be open to any organizations that want to participate in the goal of establishing a standard tools platform that will be used throughout the automotive supply chain.
 
   
 
   
 
* To provide an infrastructure for tool development required by the automotive industry
 
* To provide an infrastructure for tool development required by the automotive industry
Line 8: Line 15:
 
* To join forces and meet current and future requirements in terms of tool runtime performance and memory consumption
 
* To join forces and meet current and future requirements in terms of tool runtime performance and memory consumption
  
== Current Meetings and Activities ==
+
The charter of group can be found here.
  
=== Tech Meeting Kornwestheim 19. July 2010 ===
+
== Organization and Contact ==
Was held at the KuglerMaag Cie. facilities in Kornwestheim. The minutes fo the meeting were prepared by Andreas Graf, Itemis AG. They are available in the mailing list [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00033.html].
+
{|
 +
|<b>Spokesperson</b>: || n/a
 +
|-
 +
|<b>IWG Chair</b>:|| Andreas Graf, itemis AG
 +
|-
 +
|<b>Steering Committee</b>: || BMW Group, Robert Bosch GmbH, itemis AG
 +
|-
 +
|}
  
== Eclipse distribution for Automotive Tool Developers ==
+
<b>Member Companies</b>
 +
# [http://www.bmw.com BMW Group]
 +
# [http://www.bosch.com/worldsite_startpage/en/default.aspx Robert Bosch GmbH]
 +
# [http://www.itemis.com/ itemis AG]
 +
# [http://vif.tugraz.at/en/ Virtual Vehicle GmbH]
 +
# [http://eclipsesource.com/ EclipseSource]
 +
# [http://www.timing-architects.com/ TimingArchitects]
 +
# [http://intecs.it/eng/home.asp Intecs]
  
A dedicated Eclipse distribution for Automotive Tool Developers could be a first concrete step and deliverable of this IWG. The idea is to identify a set of existing Eclipse projects and components that are typically required and used in automotive tool development and make them available as a new Eclipse distribution at Eclipse.org. Though not including any automotive specific content yet, we believe that such an Eclipse distribution makes anyway sense because of the following reasons:
+
For more information, contact ralph (dot) mueller (at) eclipse (dot) org
  
* It points out which Eclipse projects and components are actively used in the automotive industry
+
[https://dev.eclipse.org/mailman/listinfo/auto-iwg Auto IWG Mailing List] <br \>
* It gives an orientation regarding the Eclipse release which automotive tool development is typically based on
+
* It eases the provision and maintenance of the Eclipse platform required for automotive tool development
+
  
It is important to note that such an Eclipse distribution is addressed to automotive tool developers but not to automotive tool users. In other words, it is not meant as something that ECU software developers could use out of the box and find useful. It is intended as starting point and target platform which ECU software tool developers can base their work on. What ECU software developers will eventually be provided with, are mostly the tools resulting for the ECU software tool development plus the dependent parts of the Eclipse Tool Developer distribution.
+
== Events, Activities and News ==
  
Based on the current state of discussion the following Eclipse projects and components have been deemed relevant to an Eclipse distribution for Automotive Tool Developers:
 
  
From Artop (see [http://www.artop.org]):
+
For more information, review http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00445.html this list entry].
 +
Agenda will be published shortly. If you want to add to the agenda, please use the [https://dev.eclipse.org/mailman/listinfo/auto-iwg mailing list].
  
* Eclipse SDK 3.4.2 (Ganymede)
+
<b>News:</b> [https://projects.eclipse.org/proposals/app4mc APP4MC] proposal. The proposal aims to transfer the results and future development of the ITEA Amalthea and Amalthea4Public research activities into an Eclipse open source project
* EMF Query SDK 1.2.0
+
* EMF SDO XSD SDK 2.4.2
+
* EMF Transaction SDK 1.2.3
+
* EMF Validation SDK 1.2.1
+
* GEF SDK 3.4.2
+
* GMF SDK 2.1.3
+
* MDT OCL SDK 1.2.3
+
* MDT UML2 SDK 2.2.2
+
* Orbit R20080807152315
+
  - org.apache.commons.lang 2.3.0
+
  - org.jdom 1.0.0
+
  
Additional projects and components from EDONA (see [http://www.edona.fr/scripts/home/publigen/content/templates/show.asp?L=EN&P=55&vTicker=alleza]):
+
<b>News:</b> [http://eclipse.org/proposals/modeling.eatop/ EATOP] accepted as Eclipse Project in the Modeling Top Level Project
  
* Acceleo 2.4.0 SDK
+
<b>News:</b> [http://www.itea2.org/project/index/view/?project=10015 Amalthea project] applying for second phase at ITEA2
* Antlr 4.1.1
+
* M2M ATL SDK 2.0.2
+
* M2T MTL SDK 0.7.0RC1
+
* Papyrus 1.11.0
+
  - Papyrus EADL 1.9.7.1
+
  - Papyrus SYSML 1.1.5
+
* HMI svg format
+
* East-adl 2 experimentation
+
  
Additional projects and components requested by IWG members:
+
A list of past meetings and meeting minutes is at past [[Auto IWG Meetings]]
  
* oAW (open Architecture Ware)
+
== Work Packages ==
* CDT 4.0
+
* CDT 5.0
+
* WST (XML Editor 3.0)
+
* JDT
+
* BIRT
+
* DTP
+
* JET
+
* Nebula Widgets
+
* company specific plugins
+
* Mylyn
+
* M2M (QVT Operational)
+
* CLI, Log4J
+
* TCF
+
* P2 (Update / Install Manager)
+
* Device Debugging Memory View 0.9
+
* Update Manager
+
  
== Wishlist ==
+
=== WP1: Eclipse Automotive Tool Platform ===
 +
Definition of a common Eclipse Automotive Tool Platform as reference for vendors and users of
 +
Eclipse-based automotive software design tools.
  
In addition to the list of frequently used components, the working group also identified a list of topics that should be adressed in future distributions:
+
More information here: [[Auto_IWG_WP1]]
  
* Broad support of MISRA-C in the components
+
=== WP2: Big Model Support ===
* Target Device emulation / Simulation
+
Addresses performance and memory consumption issues of existing Eclipse technology when being used processing real-world automotive software engineering models.
* Strategy for a model repository / distributed collaboration aspects
+
 
* Support for Component testing and Code Coverage Analysis
+
More information here: [[Auto_IWG_WP2]]
* Full Debugger Support
+
 
* Build management support
+
=== WP3: CDT Extensions ===
* C preprosessor enhancement
+
The development of embedded systems in the automotive area has additional requirements to CDT that will be collected, analyzed and
* Product line support / Variant management.  
+
supported from this working group.
* C metamodel that includes preprocessor statements.
+
 
* C++ (ANSI-C++ and/or embedded specific dialects like Extended Embedded C++ )
+
More information here: [[Auto_IWG_WP3]]
 +
 
 +
=== WP4: Functional Safety Relevant Development Process and Environment ===
 +
Focus of this WP shall be to analyze which functions should have a toolchain in a safety environment.
 +
 
 +
More information here: [[Auto_IWG_WP4]]
 +
 
 +
=== WP5: Eclipse Qualification Roadmap (DO-330) ===
 +
Definition of qualification support elements for the functional safety qualification of eclipse based tools.
 +
 
 +
More information here: [[Auto_IWG_WP5]]
 +
 
 +
=== WP6: Build Framework ===
 +
A common build framework to support all the build steps for modern ECU-SW development
 +
 
 +
More information here: [[Auto_IWG_WP6]]
 +
 
 +
== Past News and Articles ==
 +
 
 +
Press Release 20. 07. 2011: [http://www.eclipse.org/org/press-release/20110720_autoiwg.php New Open Source Initiative for Automotive Software Development Tools]
 +
 
 +
== Relevant Conferences ==
 +
 
 +
More information here: [[Auto_IWG_Conferences]]
 +
 
 +
== Publications ==
 +
 
 +
* [https://wiki.eclipse.org/images/e/e6/TA_BTF_Specification_2.1.3_Eclipse_Auto_IWG.pdf Trace format specification BTF version 2.1.3 ], extended in the context of the ITEA2 project AMALTHEA (ID 01IS11020E)
 +
 
 +
* [https://wiki.eclipse.org/images/6/65/AMALTHEA_HTF_Specification_1.0_Eclipse_Auto_IWG.pdf Trace format specification HTF version 1.0], created in the context of the ITEA2 project AMALTHEA (ID 01IS11020E)
 +
 
 +
== Documents ==
 +
 
 +
From F2F Meeting Stuttgart Feb 16, 2012: [http://wiki.eclipse.org/images/1/1f/Auto_IWG_Minutes_Feb-16-2012.pdf Minutes], [http://wiki.eclipse.org/images/d/d4/EATOP_Presentation_16-02-2012.pdf Continental Presentation (EATOP)] , [http://wiki.eclipse.org/images/9/96/Tool_Qualification_ISO_26262_%28Validas_16-02-2012%29.pdf Validas Presentation (Tool Qualification Short - ISO 26262)], [http://wiki.eclipse.org/images/6/60/Bosch-iCTeam-AutoIWG-16Feb2012.pdf Bosch iCTeam Presentation]
 +
 
 +
== Related Eclipse Projects ==
 +
 
 +
incomplete:
 +
* [http://www.eclipse.org/cdt/ CDT]
 +
* [http://www.eclipse.org/modeling/mdt/papyrus/ Papyrus]
 +
* [http://www.eclipse.org/sphinx/ Sphinx]
 +
* [http://www.eclipse.org/rmf/ Requirements Modeling Framework]
 +
* [http://eclipse.org/proposals/modeling.eatop/ EATOP]
 +
 
 +
== External Links ==
  
== Links ==
 
[https://dev.eclipse.org/mailman/listinfo/auto-iwg Auto IWG Mailing List] <br \>
 
 
[http://artop.org AUTOSAR Tool Platform (Artop)] <br \>
 
[http://artop.org AUTOSAR Tool Platform (Artop)] <br \>
 
[http://www.edona.fr/scripts/home/publigen/content/templates/show.asp?L=EN&P=55&vTicker=alleza Edona Project] <br \>
 
[http://www.edona.fr/scripts/home/publigen/content/templates/show.asp?L=EN&P=55&vTicker=alleza Edona Project] <br \>
 
[http://topcased.org/ Topcased Project] <br \>
 
[http://topcased.org/ Topcased Project] <br \>
[http://www.eclipse.org/proposals/sphinx/ Sphinx Proposal] <br \>
+
[http://www.safe-project.eu/ SAFE project] <br \>
 +
[http://www.amalthea-project.org/ AMALTHEA project]
 +
 
 +
[[Category:Eclipse IWG]]

Latest revision as of 07:34, 30 October 2019

Open Source Initiative for Automotive Software Development Tools

This Working Group is no longer active. Content is kept for historical reason


Objectives

Innovation in the automotive industry is mostly achieved by electronics and software functions. The system automobile is becoming increasingly complex, an open developer tool workbench that extends throughout the supply-chain is becoming a must for the industry. Improvements and innovations to these software development tools are required to accelerate product development, create high quality software features and improve integration across the automotive supply chain.

The Eclipse Foundation is pleased to announce the creation of a new open source initiative to define and implement a standard platform for the software development tools used in the automotive industry. The new Eclipse Automotive Working Group will be open to any organizations that want to participate in the goal of establishing a standard tools platform that will be used throughout the automotive supply chain.

  • To provide an infrastructure for tool development required by the automotive industry
  • To address and support the needs for the whole automotive software development cycle
  • To avoid that the same non-competitive basic tool functionality is redeveloped over and over again
  • To join forces and meet current and future requirements in terms of tool runtime performance and memory consumption

The charter of group can be found here.

Organization and Contact

Spokesperson: n/a
IWG Chair: Andreas Graf, itemis AG
Steering Committee: BMW Group, Robert Bosch GmbH, itemis AG

Member Companies

  1. BMW Group
  2. Robert Bosch GmbH
  3. itemis AG
  4. Virtual Vehicle GmbH
  5. EclipseSource
  6. TimingArchitects
  7. Intecs

For more information, contact ralph (dot) mueller (at) eclipse (dot) org

Auto IWG Mailing List

Events, Activities and News

For more information, review http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00445.html this list entry]. Agenda will be published shortly. If you want to add to the agenda, please use the mailing list.

News: APP4MC proposal. The proposal aims to transfer the results and future development of the ITEA Amalthea and Amalthea4Public research activities into an Eclipse open source project

News: EATOP accepted as Eclipse Project in the Modeling Top Level Project

News: Amalthea project applying for second phase at ITEA2

A list of past meetings and meeting minutes is at past Auto IWG Meetings

Work Packages

WP1: Eclipse Automotive Tool Platform

Definition of a common Eclipse Automotive Tool Platform as reference for vendors and users of Eclipse-based automotive software design tools.

More information here: Auto_IWG_WP1

WP2: Big Model Support

Addresses performance and memory consumption issues of existing Eclipse technology when being used processing real-world automotive software engineering models.

More information here: Auto_IWG_WP2

WP3: CDT Extensions

The development of embedded systems in the automotive area has additional requirements to CDT that will be collected, analyzed and supported from this working group.

More information here: Auto_IWG_WP3

WP4: Functional Safety Relevant Development Process and Environment

Focus of this WP shall be to analyze which functions should have a toolchain in a safety environment.

More information here: Auto_IWG_WP4

WP5: Eclipse Qualification Roadmap (DO-330)

Definition of qualification support elements for the functional safety qualification of eclipse based tools.

More information here: Auto_IWG_WP5

WP6: Build Framework

A common build framework to support all the build steps for modern ECU-SW development

More information here: Auto_IWG_WP6

Past News and Articles

Press Release 20. 07. 2011: New Open Source Initiative for Automotive Software Development Tools

Relevant Conferences

More information here: Auto_IWG_Conferences

Publications

Documents

From F2F Meeting Stuttgart Feb 16, 2012: Minutes, Continental Presentation (EATOP) , Validas Presentation (Tool Qualification Short - ISO 26262), Bosch iCTeam Presentation

Related Eclipse Projects

incomplete:

External Links

AUTOSAR Tool Platform (Artop)
Edona Project
Topcased Project
SAFE project
AMALTHEA project

Back to the top