This paper provides some background and the roadmap of the AUTO-CAAS project, which is a 3-year project financed by the Swedish Knowledge Foundation and is ongoing as a joint project among three academic and industrial partners. The aim of the project is to exploit the formal models of the AUTOSAR standard, developed by the industrial partner of the project Quviq AB, in order to predict possible future failures in concrete implementations of components. To this end, the deviations from the formal specification will be exploited to generate test-cases that can push concrete components to the corners where such deviation will result in observable failures. The same information will also be used in the diagnosis of otherwise detected failures in order to pinpoint their root causes.
{"title":"Automatic consequence analysis of automotive standards (AUTO-CAAS)","authors":"T. Arts, M. Mousavi","doi":"10.1145/2752489.2752495","DOIUrl":"https://doi.org/10.1145/2752489.2752495","url":null,"abstract":"This paper provides some background and the roadmap of the AUTO-CAAS project, which is a 3-year project financed by the Swedish Knowledge Foundation and is ongoing as a joint project among three academic and industrial partners. The aim of the project is to exploit the formal models of the AUTOSAR standard, developed by the industrial partner of the project Quviq AB, in order to predict possible future failures in concrete implementations of components. To this end, the deviations from the formal specification will be exploited to generate test-cases that can push concrete components to the corners where such deviation will result in observable failures. The same information will also be used in the diagnosis of otherwise detected failures in order to pinpoint their root causes.","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"11 1","pages":"35-38"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"85148340","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
In the safety domain, safety standards are used as development guidelines to keep the risk at an acceptable level. Safety of the safety-critical systems can be assessed according to those safety standards. This assessment process is called safety assurance. Due to the manual work, safety assurance process is usually costly, time consuming, and hard to be evaluated. In this paper we propose to use the existing PSM framework into the automotive domain to design metrics according to the ISO 26262 standard. These metrics can identify costly processes in the safety assurance process. To demonstrate the method, a case study is carried on ISO 26262 part 3 (Conceptual Phase).
{"title":"Functional safety measurement in the automotive domain: adaptation of PSM","authors":"Yaping Luo, Jaap Stelma, M. van den Brand","doi":"10.1145/2752489.2752492","DOIUrl":"https://doi.org/10.1145/2752489.2752492","url":null,"abstract":"In the safety domain, safety standards are used as development guidelines to keep the risk at an acceptable level. Safety of the safety-critical systems can be assessed according to those safety standards. This assessment process is called safety assurance. Due to the manual work, safety assurance process is usually costly, time consuming, and hard to be evaluated. In this paper we propose to use the existing PSM framework into the automotive domain to design metrics according to the ISO 26262 standard. These metrics can identify costly processes in the safety assurance process. To demonstrate the method, a case study is carried on ISO 26262 part 3 (Conceptual Phase).","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"19 1","pages":"11-17"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"81612609","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
As the Technology Readiness Levels (TRLs) of self-driving vehicles increase, it is necessary to investigate the Electrical/Electronic(E/E) system architectures for autonomous driving, beyond proof-of-concept prototypes. Relevant patterns and anti-patterns need to be raised into debate and documented. This paper presents the principal components needed in a functional architecture for autonomous driving, along with reasoning for how they should be distributed across the architecture. A functional architecture integrating all the concepts and reasoning is also presented.
{"title":"A functional architecture for autonomous driving","authors":"Sagar Behere, M. Torngren","doi":"10.1145/2752489.2752491","DOIUrl":"https://doi.org/10.1145/2752489.2752491","url":null,"abstract":"As the Technology Readiness Levels (TRLs) of self-driving vehicles increase, it is necessary to investigate the Electrical/Electronic(E/E) system architectures for autonomous driving, beyond proof-of-concept prototypes. Relevant patterns and anti-patterns need to be raised into debate and documented. This paper presents the principal components needed in a functional architecture for autonomous driving, along with reasoning for how they should be distributed across the architecture. A functional architecture integrating all the concepts and reasoning is also presented.","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"25 1","pages":"3-10"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"89813415","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Silverio Martínez-Fernández, Claudia P. Ayala, Xavier Franch, E. Nakagawa
The use of software reference architectures plays a fundamental role in software development, as it could bring several benefits such as providing means to design applications' software architectures with higher productivity and quality. However, many organizations still find scarce the existing empirical evidence about the benefits and drawbacks of software reference architectures. Organizations need such evidence to make informed decisions whether or not to adopt a software reference architecture for the development and maintenance of software applications. In this context, this paper aims to gather evidence on AUTOSAR, a mature and accepted software reference architecture for automotive applications used worldwide by more than 180 organizations. We designed and executed a web-based survey addressed to practitioners with experience in using AUTOSAR. We obtained 51 valid responses. The survey results indicate that the most popular benefits of AUTOSAR are standardization (88%), reuse (80%) and interoperability (51%) whereas its most important drawbacks are complexity (65%), initial investment (59%) and learning curve (51%). The respondents of the survey also gave directions to handle the major drawbacks of AUTOSAR, such as the need of a tool environment to improve its usability and handle its complexity, and the need of more stable releases of AUTOSAR to decrease the cost of migrating among versions.
{"title":"A survey on the benefits and drawbacks of AUTOSAR","authors":"Silverio Martínez-Fernández, Claudia P. Ayala, Xavier Franch, E. Nakagawa","doi":"10.1145/2752489.2752493","DOIUrl":"https://doi.org/10.1145/2752489.2752493","url":null,"abstract":"The use of software reference architectures plays a fundamental role in software development, as it could bring several benefits such as providing means to design applications' software architectures with higher productivity and quality. However, many organizations still find scarce the existing empirical evidence about the benefits and drawbacks of software reference architectures. Organizations need such evidence to make informed decisions whether or not to adopt a software reference architecture for the development and maintenance of software applications. In this context, this paper aims to gather evidence on AUTOSAR, a mature and accepted software reference architecture for automotive applications used worldwide by more than 180 organizations. We designed and executed a web-based survey addressed to practitioners with experience in using AUTOSAR. We obtained 51 valid responses. The survey results indicate that the most popular benefits of AUTOSAR are standardization (88%), reuse (80%) and interoperability (51%) whereas its most important drawbacks are complexity (65%), initial investment (59%) and learning curve (51%). The respondents of the survey also gave directions to handle the major drawbacks of AUTOSAR, such as the need of a tool environment to improve its usability and handle its complexity, and the need of more stable releases of AUTOSAR to decrease the cost of migrating among versions.","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"181 1","pages":"19-26"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"85431766","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Hariharan Venkitachalam, J. Richenhagen, A. Schloßer, T. Tasky
The key challenges to software development in the powertrain domain are an exploding complexity, short development cycles and increasing quality and safety requirements. Architecture design addresses these challenges by structuring development over the entire lifecycle. Being a work product of the very early stage of development, architecture design errors lead to rework and higher development costs at any following development step. Verification and validation on architecture level leads to significant quality increase and reduces development risks. To approach this in a structured manner, the authors propose automated metric based evaluation of the software architecture. Metrics are identified and developed based on the Goal Question Metric approach. Quality goals for the architecture are derived from international standards, organizational goals and domain specific requirements. Questions are developed based on the goals to derive metrics for the evaluation of software quality criteria. The metrics developed are integrated into the software development process. At the end, application examples from series hybrid control software projects are shown. By the automated, metric-based approach so far extensive manual reviews and scenario analyses are supported by objective and measurable criteria. As an added value to state-of-the-art development strategies, frontloading of the costs is achieved by early evaluation of the software architecture.
{"title":"Metrics for verification and validation of architecture in powertrain software development","authors":"Hariharan Venkitachalam, J. Richenhagen, A. Schloßer, T. Tasky","doi":"10.1145/2752489.2752496","DOIUrl":"https://doi.org/10.1145/2752489.2752496","url":null,"abstract":"The key challenges to software development in the powertrain domain are an exploding complexity, short development cycles and increasing quality and safety requirements. Architecture design addresses these challenges by structuring development over the entire lifecycle. Being a work product of the very early stage of development, architecture design errors lead to rework and higher development costs at any following development step. Verification and validation on architecture level leads to significant quality increase and reduces development risks. To approach this in a structured manner, the authors propose automated metric based evaluation of the software architecture. Metrics are identified and developed based on the Goal Question Metric approach. Quality goals for the architecture are derived from international standards, organizational goals and domain specific requirements. Questions are developed based on the goals to derive metrics for the evaluation of software quality criteria. The metrics developed are integrated into the software development process. At the end, application examples from series hybrid control software projects are shown. By the automated, metric-based approach so far extensive manual reviews and scenario analyses are supported by objective and measurable criteria. As an added value to state-of-the-art development strategies, frontloading of the costs is achieved by early evaluation of the software architecture.","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"1 1","pages":"27-33"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"87558482","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Identification of similar fragments of software systems, or clones, has many applications in software engineering and maintenance, including quality control and improvement, standards compliance, test management and failure analysis and prevention. Code similarity analysis systems, or clone detectors, are a mature and widely used technology in traditional software code maintenance. As model driven engineering continues to advance, technologies such as Simulink are increasingly widely used to design and implement automotive software systems. Automotive Simulink models are particularly prone to cloning due to the copy-paste authoring paradigm of the Simulink IDE, and the inherent similarity of elements and tasks in automotive applications. Thus the ability to find Simulink model clones is equally important, but is much less thoroughly studied and used.
{"title":"SIMONE: architecture-sensitive near-miss clone detection for Simulink models","authors":"J. Cordy","doi":"10.1145/2752489.2752498","DOIUrl":"https://doi.org/10.1145/2752489.2752498","url":null,"abstract":"Identification of similar fragments of software systems, or clones, has many applications in software engineering and maintenance, including quality control and improvement, standards compliance, test management and failure analysis and prevention. Code similarity analysis systems, or clone detectors, are a mature and widely used technology in traditional software code maintenance. As model driven engineering continues to advance, technologies such as Simulink are increasingly widely used to design and implement automotive software systems. Automotive Simulink models are particularly prone to cloning due to the copy-paste authoring paradigm of the Simulink IDE, and the inherent similarity of elements and tasks in automotive applications. Thus the ability to find Simulink model clones is equally important, but is much less thoroughly studied and used.","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"31 1","pages":"1-2"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"74995144","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Developing automotive functions involves complex software to a growing extent while still following a consecutive waterfall-like development process: Integrating and testing software with other software and with hardware components is conducted towards the final phases during the development. For example, ambiguous requirements or unclear semantics in system interfaces show up very late and mostly not before integration testing. In this article, we are reporting about results from conducting interviews with integration and test engineers at a large automotive OEM about today's most resource-intense challenges when dealing with software integration testing tasks at interconnected hardware-in-the-loop test rig environments. Challenges in processes, communication, and implementation were mentioned most often as emerging topics to be tackled over and over again during this phase in a vehicle series development project.
{"title":"Challenges from integration testing using interconnected hardware-in-the-loop test rigs at an automotive OEM – an industrial experience report","authors":"Jan Schroeder, C. Berger, T. Herpel","doi":"10.1145/2752489.2752497","DOIUrl":"https://doi.org/10.1145/2752489.2752497","url":null,"abstract":"Developing automotive functions involves complex software to a growing extent while still following a consecutive waterfall-like development process: Integrating and testing software with other software and with hardware components is conducted towards the final phases during the development. For example, ambiguous requirements or unclear semantics in system interfaces show up very late and mostly not before integration testing. In this article, we are reporting about results from conducting interviews with integration and test engineers at a large automotive OEM about today's most resource-intense challenges when dealing with software integration testing tasks at interconnected hardware-in-the-loop test rig environments. Challenges in processes, communication, and implementation were mentioned most often as emerging topics to be tackled over and over again during this phase in a vehicle series development project.","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"17 5 1","pages":"39-42"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"77926769","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Although many architecture evolution techniques exist, most of them are not able to perform a quality impact prediction. Most of these techniques concentrate on analyzing the expected performance and reliability of design alternatives on prototypes or previous experiences. In this paper, we propose a novel model-driven prediction approach, which is estimated, based on the extractable information from the User Behavioral Flow and the Continues-Time Markov Chain (CTMC) and its corresponding Hidden Markov Mode (HMM). This paper also reports our experience and the lessons we learned in applying this approach on MyUAlberta applications as a large-scale case study.
{"title":"Reliability analysis and quality impact prediction in application architecture evolution","authors":"Sepideh Emam, John Komick","doi":"10.1145/2752489.2752490","DOIUrl":"https://doi.org/10.1145/2752489.2752490","url":null,"abstract":"Although many architecture evolution techniques exist, most of them are not able to perform a quality impact prediction. Most of these techniques concentrate on analyzing the expected performance and reliability of design alternatives on prototypes or previous experiences. In this paper, we propose a novel model-driven prediction approach, which is estimated, based on the extractable information from the User Behavioral Flow and the Continues-Time Markov Chain (CTMC) and its corresponding Hidden Markov Mode (HMM). This paper also reports our experience and the lessons we learned in applying this approach on MyUAlberta applications as a large-scale case study.","PeriodicalId":6489,"journal":{"name":"2015 First International Workshop on Automotive Software Architecture (WASA)","volume":"47 1","pages":"43-46"},"PeriodicalIF":0.0,"publicationDate":"2015-05-04","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"82957460","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：