Difference between revisions of "AUTO-CAAS"
| Line 37: | Line 37: | ||
* [[AUTO-CAAS Project Kick-Off Meeting]] | * [[AUTO-CAAS Project Kick-Off Meeting]] | ||
* [[AUTO-CAAS Project Meeting 14 September 2015]] | * [[AUTO-CAAS Project Meeting 14 September 2015]] | ||
| + | * [[AUTO-CAAS Project Meeting 18 January 2016]] | ||
* [http://www.hh.se/english/news/news/newwarningsystemforcarmanufacturing.65443714.html Press release in English] and [http://www.hh.se/omhogskolan/aktuellt/nyheter/nyheter/nyheter/nyttvarningssystemvidbiltillverkning.65443706.html in Swedish] , [http://www.elinor.se/index.php/Nytt-varningssystem-vid-biltillverkning.html Article in Elektronik i Norden] | * [http://www.hh.se/english/news/news/newwarningsystemforcarmanufacturing.65443714.html Press release in English] and [http://www.hh.se/omhogskolan/aktuellt/nyheter/nyheter/nyheter/nyttvarningssystemvidbiltillverkning.65443706.html in Swedish] , [http://www.elinor.se/index.php/Nytt-varningssystem-vid-biltillverkning.html Article in Elektronik i Norden] | ||
Revision as of 20:51, 10 January 2016
Contents
Automated Consequence Analysis for Automotive Standards
Brief Description
The Automotive Open System Architecture (AUTOSAR) standard is gaining momentum with several automotive manufacturers and there is a growing trend towards new vehicle platforms based on the latest versions of this standard. The standard enables manufacturers to allow Tier-1 suppliers to contract arbitrary Tier-2 software developer for ECUs, as long as the developed software conforms to the specified behavior according to AUTOSAR. This is in clear contrast to earlier situation, in which a preferred Tier-2 developer was appointed to develop software for all Tier-1 hardware suppliers. This paradigm shift brings about economical and financial benefits (both for suppliers and manufacturers). However, it also introduces certain risks and challenges.
The AUTOSAR standard is complex and does leave room for interpretation and optimizations. In order to be competitive, Tier-2 developers strive after implementing several optimizations and utilizing room for interpretation of the standard to make their product out-perform the competition.
The goal of this project is to exploit the technology of model-based testing in order to detect deviations from the AUTOSAR standard and furthermore trace the consequences of such deviations into visible deviating behavior (failures). To this end, we will use and enhance the model-based testing framework developed at QuviQ to detect deviations from the AUTOSAR standard. This framework is, for example, used by SP (Technical Research Institute of Sweden) to certify software delivered to Volvo Car Corporation. As noted before, one of the major obstacles in using the current model-based framework is the different interpretations of the standard. Unless the consequences of these interpretations are properly analyzed, such variations are justified by the developers. This poses a major challenge for the widespread application of the standard as a model for certifying components, modules, ECUs and vehicle functions.
Project Team
- Thomas Arts, Co-Founder and CTO of QuviQ AB
- John Hughes, Co-Founder and CEO of QuviQ AB, Professor at Chalmers University of Technology
- Wojciech Mostowski, Assistant Professor, AUTO-CAAS Project
- Mohammad Mousavi, Group Leader, Principal Investigator for AUTO-CAAS Project
- Michael Svenstam, ArcCore AB
Publications
- T. Arts and M.R. Mousavi. Automatic Consequence Analysis of Automotive Standards (AUTO-CAAS) [Position Paper] . First International Workshop on Automotive Software Architectures (WASA 2015), ACM Press, 2015.
Outreach and Dissemination
- AUTO-CAAS Project Kick-Off Meeting
- AUTO-CAAS Project Meeting 14 September 2015
- AUTO-CAAS Project Meeting 18 January 2016
- Press release in English and in Swedish , Article in Elektronik i Norden
Contact
Mohammad Mousavi, Professor of Computer Systems Engineering
