1 / 9

Challenges in Automotive Software Engineering

Challenges in Automotive Software Engineering. by Manfred Broy 2006 ICSE pp. 33-42 Poster by: Matt Jankowski. Summary. The amount of software in cars has been growing exponentially Software engineering is just in its beginning stages as it relates to cars

levana
Download Presentation

Challenges in Automotive Software Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Challenges in Automotive Software Engineering by Manfred Broy 2006 ICSE pp. 33-42 Poster by: Matt Jankowski

  2. Summary • The amount of software in cars has been growing exponentially • Software engineering is just in its beginning stages as it relates to cars • There are several challenges facing the automotive industry in regard to the design and implementation of software in cars • Many opportunities exist for research and improvement

  3. Background • Software first began appearing in cars just 30 years ago • Auto manufactures intentionally evolved into assemblers of components which were designed and created by suppliers • Initial software was very local; tasks and components were isolated to Electronic Control Units (ECU)

  4. Background • Software now controls all aspects of an automobile • It is necessary for many of these systems to communicate with each other • Today’s luxury cars contain over 70 ECU's, over 10,000,000 lines of code and can complete over 2000 functions

  5. Challenges • Current systems were slowly built from bottom up rather than designed from the top down • Modular approach does not work well when considering a complex system • Auto companies use mostly proprietary solutions

  6. Challenges • Significant retraining of labor has been necessary • Engineers typically remain in the industry for long periods of time • Universities not producing software engineers skilled in embedded systems • New skills needed for those in auto repair

  7. Future • Functionality will continue to grow • Cost control will remain a priority • Areas of focus / research • Move towards system engineering • Reevaluate Use of tools • Development process redesign • Quality improvements

  8. Critique • Paper does a good job of explaining why the auto industry is unique in regard to software engineering • Both challenges and potential solutions are presented well • Paper should better describe what auto companies are currently doing to address the challenges • Paper is not clearly laid out

  9. Questions • What percentage of a car’s cost is related to software and electronics? • Why is there currently little reuse of code? • What is the main reason software is so modularized in cars?

More Related