1 / 24

Automotive Software Engineering

Automotive Software Engineering. Yaswanth Amaraneni Varun Ayanala. Agenda. Introduction What is Automotive Software Engineering all about? History Roadmap Pros and Cons Conclusion References. Introduction.

sylvia-ware
Download Presentation

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. Automotive Software Engineering Yaswanth Amaraneni Varun Ayanala

  2. Agenda • Introduction • What is Automotive Software Engineering all about? • History • Roadmap • Pros and Cons • Conclusion • References

  3. Introduction • In many technical products, software plays a dominate role today. In cars, this applies even to the extreme. • The amount of software in modern cars is increasing at breathing pace. • 80 % of future innovations in the automobile industry will base upon electronics, 90 % of these on software.

  4. Framework for Automotive SE • There are two reasons for rapid inclusion of new software into our cars: • New functionalities that are considered unique selling points as well as • Cheaper and better technical solutions substituting the realization of existing functionalities.

  5. Outlines the software-based technical revolution in the car and the associated software engineering challenges Figure 1 : Frameworks for automotive systems and software engineering [2].

  6. Digital automotive revolution • Software in cars : The software amount and the number of software based functions in cars is growing exponentially size, role, interaction and distribution. • Connectivity • User Experience Concepts and design • Navigation • Human machine interface • IT system services

  7. Connectivity

  8. User Experience

  9. Navigation

  10. Fields of focus in automotive SE • Reliability, quality, supplier management, portability and reusability, costs, engineering tools. • Scientific challenges • Software logistics: • There are three main lines of hope to improve the state of the art: • Improved development processes • Modeling techniques • Domain specific architectures • Tool Support

  11. History • The role of software in cars. • Just 30 year ago, software was deployed into cars to control the engine and, in particular, the ignition. The future • Innovative in functionality • cost reduction • innovative architecture

  12. Challenges  Competency and Improved Process  Innovation in Architecture  Development and Maintenance Process  Hardware and Technical Infrastructure  Cost Issues • Research challenges  Comprehensive Architecture for car Reducing Complexity  Improving Process

  13. Figure 2 : Comprehensive Architecture [2].  Seamless Model Driven Development Integrated Tool Support

  14. Research At TUM Distributed Systems Models Figure 3: Screenshot from Tool AutoFocus [2]. Adapted Development Process Tool Support

  15. A Roadmap • Domain profile • Research challenges in SE • Model-based development • Overview of ArchE and availability reasoning framework.

  16. Model-based automotive SE • Three key factors:  The rapidly growing number of networked software future.  The resulting integration of more and more suppliers.  Rising model variability.

  17. Overview of ArchE • Basic ArchE Concepts Figure 4: Example Quality Attribute Scenario [5].

  18. Elements of a Reasoning Framework • Scenario and Responsibility Parameter Definition • Initial Design Creation • Model Interpretation and Evaluation • Suggest Design Tactics • Apply Design Tactics

  19. Overview of ArchE • To monitor the software running on the electronic control units (ECU’s) • Fig 2: Timeline showing system and watchdog interaction when a f Fig 5: Timeline showing system and watchdog interaction when a failure occurs [5].

  20. Pros & Cons • Communication services • Safety and security • Error diagnosis and recovery • Reuse • Cost • Connectivity Problems

  21. Conclusion • Software is playing an increasing role in an economically highly interesting market. • We have highlighted some of the salient features of software engineering for automotive systems and shown how they impact current software engineering.

  22. References [1] Botaschanjan J., Kof L., Kuhnel C., Spichkova M., Towards verified automotive software. Proceedingof SEAS’05 (2005, New York, NY, USA). 1-6. [2] Broy M., Challenges in Automotive Software Engineering. Proceeding of ICSE’06 (May 2006, Shanghai, China), 33-42. [3] Pernstal J., Magazinovic A., Ohman P., A multiple case study investigating the interaction between manufacturing and development organizations in automotive software engineering. Proceedingof ESEM’08 (2008, New York, NY, USA), 12 – 21.

  23. [4] Pretschner A., Broy M., Kruger I., Stauner T., Software Engineering for Automotive Systems: A Roadmap. Proceeding of FOSE '07(July 2007, Washington, DC, USA), 55-71. [5] Shelton C., Martin C., Using Models to Improve the Availability of Automotive Software Architectures. Proceeding of SEAS'07(2007, Washington, DC, USA), 9. [6] Vogler G., Flor Thomas., Eichler H., Kasprowicz M., An Open Model Infrastructure for Automotive Software. Proceeding of OOPSLA’04 (Oct 2004, Vancouver, British Columbia, Canada).

  24. Thank you

More Related