Auto IWG

From Eclipsepedia

Jump to: navigation, search

Open Source Initiative for Automotive Software Development Tools

Contents

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: Andreas Graf, itemis AG
Steering Committee Chair: Ignacio Garro, Continental AG
Steering Committee: Awaiting management approval - see [1]

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

See also the Auto IWG Mailing List

Meetings and Activities

The next meeting is September 13th

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

Work Packages

WP1: Technology Recommendations : Eclipse Automotive Tools Platform

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:

  • It points out which Eclipse projects and components are actively used in the automotive industry
  • 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.

WP2: Huge Models Support

Large models that exist in the automotive engineering space tend to create performance, loading, saving and other problems with the existing Eclipse implementations. The work package intents to find resolutions for these issues.

WP3: CDT Extensions

WP4: Functional Safety Relevant Development Process and Environment

Functional Safety has an impact on Eclipse based tooling in two dimensions: First, which tools can be used to develop safety-relevant functions. Secondly, what are the implications of standards like ISO26262 on the development of Eclipse-based tooling?

This work package has one initial task: Every company rep to discuss internally who the right people within the organizations are to connect to

  • Identify the stakeholders in the IWG member companies, then (unless otherwise decided)
  • Definition of scope
  • Clarification of requirements
  • Define approach
  • Connect to OPEES, OpenETCS

Proposed Components

Wishlist

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:

  • Broad support of MISRA-C in the components
  • Target Device emulation / Simulation
  • Strategy for a model repository / distributed collaboration aspects
  • Support for Component testing and Code Coverage Analysis
  • Full Debugger Support
  • Build management support
  • C preprosessor enhancement
  • 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

incomplete:

CDT Papyrus Sphinx

New proposal: Requirements Modeling Framework

External Links

AUTOSAR Tool Platform (Artop)
Edona Project
Topcased Project