Jump to: navigation, search

Difference between revisions of "Auto IWG"

(Meetings and Activities)
(45 intermediate revisions by 7 users not shown)
Line 15: Line 15:
  
 
== Organization and Contact ==
 
== Organization and Contact ==
 +
{|
 +
|<b>Spokesperson</b>: || Ignacio Garro, Continental AG
 +
|-
 +
|<b>IWG Chair</b>:|| Andreas Graf, itemis AG
 +
|-
 +
|<b>Steering Committee</b>: || BMW Group, Continental AG, Robert Bosch GmbH, itemis AG
 +
|-
 +
|}
  
Spokesperson: Andreas Graf, itemis AG
+
<b>Member Companies</b>
 
+
# [http://www.bmw.com BMW Group]
Steering Committee Chair: Ignacio Garro, Continental AG
+
# [http://www.bosch.com/worldsite_startpage/en/default.aspx Robert Bosch GmbH]
 
+
# [http://www.conti-online.com/generator/www/start/com/en/index_en.html Continental AG]
Steering Committee: Awaiting management approval - see [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00069.html]
+
# [http://www.itemis.com/ itemis AG]
 +
# [http://www.validas.de/index.html Validas 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]
  
 
For more information, contact ralph (dot) mueller (at) eclipse (dot) org
 
For more information, contact ralph (dot) mueller (at) eclipse (dot) org
  
See also the  [https://dev.eclipse.org/mailman/listinfo/auto-iwg Auto IWG Mailing List] <br \>
+
[https://dev.eclipse.org/mailman/listinfo/auto-iwg Auto IWG Mailing List] <br \>
  
 
== Meetings and Activities ==
 
== Meetings and Activities ==
  
A list of meetings and meeting minutes is at [[Auto IWG Meetings]]
+
A list of past meetings and meeting minutes is at past [[Auto IWG Meetings]]
  
=== Tech Meeting Suttgart 08. June 2011 ===
+
== Work Packages ==
Was held at the Itemis AG office in Stuttgart / Vaihingen. The minutes of the meeting were prepared by Ralph Mueller, Eclipse foundation. They are available in the mailing list [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00069.html]
+
  
=== Proposal for Creation of Auto IWG published ===
+
=== WP1: Eclipse Automotive Tool Platform ===
You can find the proposal here [http://dev.eclipse.org/mhonarc/lists/auto-iwg/msg00059.html]
+
Definition of a common Eclipse Automotive Tool Platform as reference for vendors and users of
 +
Eclipse-based automotive software design tools.
  
=== Tech Meeting Kornwestheim 21. October 2010 ===
+
More information here: [[Auto_IWG_WP1]]
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/msg00055.html].
+
  
=== Tech Meeting Kornwestheim 19. July 2010 ===
+
=== WP2: Big Model Support ===
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].
+
Addresses performance and memory consumption issues of existing Eclipse technology when being used processing real-world automotive software engineering models.
  
== Eclipse distribution for Automotive Tool Developers ==
+
More information here: [[Auto_IWG_WP2]]
  
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:
+
=== 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.  
  
* It points out which Eclipse projects and components are actively used in the automotive industry
+
More information here: [[Auto_IWG_WP3]]
* 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.
+
=== 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.  
  
[[Proposed Components]]
+
More information here: [[Auto_IWG_WP4]]
  
== Wishlist ==
+
=== WP5: Eclipse Qualification Kit (ISO26262) ===
 +
Definition of qualification support elements for the functional safety qualification of eclipse based 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_WP5]]
  
* Broad support of MISRA-C in the components
+
== News, Press Releases, Articles ==
* Target Device emulation / Simulation
+
 
* Strategy for a model repository / distributed collaboration aspects
+
Press Release 20. 07. 2011: [http://www.eclipse.org/org/press-release/20110720_autoiwg.php New Open Source Initiative for Automotive Software Development Tools]
* Support for Component testing and Code Coverage Analysis
+
 
* Full Debugger Support
+
== Documents ==
* Build management support
+
 
* C preprosessor enhancement
+
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]
* Product line support / Variant management.  
+
* C metamodel that includes preprocessor statements.
+
* C++ (ANSI-C++ and/or embedded specific dialects like Extended Embedded C++ )
+
  
 
== Related Eclipse Projects ==
 
== Related Eclipse Projects ==
  
 
incomplete:  
 
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/cdt/ CDT]
+
New proposal:  
[http://www.eclipse.org/modeling/mdt/papyrus/ Papyrus]
+
[http://www.eclipse.org/sphinx/ Sphinx]
+
  
New proposal: [http://www.eclipse.org/proposals/modeling.mdt.rmf/ Requirements Modeling Framework]
+
[http://www.eclipse.org/rmf/ Requirements Modeling Framework]
  
 
== External Links ==
 
== External Links ==
Line 84: Line 96:
 
[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.safe-project.eu/ SAFE project]
 +
 +
[[Category:Eclipse IWG]]

Revision as of 11:37, 16 November 2012

Open Source Initiative for Automotive Software Development Tools

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 Industry 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: Ignacio Garro, Continental AG
IWG Chair: Andreas Graf, itemis AG
Steering Committee: BMW Group, Continental AG, Robert Bosch GmbH, itemis AG

Member Companies

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

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

Auto IWG Mailing List

Meetings and Activities

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 Kit (ISO26262)

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

More information here: Auto_IWG_WP5

News, Press Releases, Articles

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

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:

New proposal:

Requirements Modeling Framework

External Links

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