An Eclipse based Design Tool for Automotive Applications

1. Artus
An Eclipse based Design Tool for Automotive
Applications
Christof Hammel Markus Kopf

2. Contents
• The Automotive domain
• Embedded Software Technology
• Component Technology
• Development Process
• Bosch way to Eclipse
• Architecture
• Features
• Outlook

3. The Automotive
Domain
2008
Software as Key
1997 Competence
1st CommonRail
(software as integral
part in of the system)
1986
1st EDC
(Electronic Control Unit
1927 without software)
In-line pump

4. Embedded Software
Technology
• Worldwide development / concurrent (globalized) engineering
• SW exchange with development partners
• Huge diversity in software (many OEMʼs = car manufacturers)
• Limited Hardware ressources (memory, performance)
Component technology seems to be the right approach
State-of-the-art Component Models (e.g. CORBA, OSGi, AADL,…) are
not applicable to our domain
Component technology “BlueArX”

5. Component Technology
ANSI C language is “state-of-the-art” in the automotive world
But: C does not support architecture based development
• Component Technology is build on top of C

6. Component Technology

7. Development Process

9. Bosch way to Eclipse
• 2002: Simple editor by using eclipse as development kit
• 2004: First Eclipse-Application at Bosch
• 2004: Architecture Visualization GEF
• 2005: Architecture Validation & Configuration Editor
• 2007: Merge of editor and validation in one platform
• 2008: GMF based visualization
• Future: Full build process integration

10. Architecture
Validation Editors Analyse Visualisation
GOM Shadow Model
Loader

11. Interface Editor

12. Connection to code

13. Visualization

14. Visualization

15. Outlook
• Migration to new object model
• Code completion
• Hover
• Incremental loader
• Support Datapools
• Graphical editors

16. Christof Hammel
christof.hammel@de.bosch.com
Markus Kopf
markus.kopf@itemis.de