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.
- Ameller, D., Galster, M., Avgeriou, P. and Franch, X. 2015. A survey on quality attributes in service-based systems. Software Quality Journal. (Feb. 2015), 1--29.Google Scholar
- Angelov, S., Grefen, P. and Greefhorst, D. 2012. A framework for analysis and design of software reference architectures. Information and Software Technology. 54, 4 (2012), 417--431. Google ScholarDigital Library
- Angelov, S., Trienekens, J. and Kusters, R. 2013. Software reference architectures-exploring their usage and design in practice. Software Architecture (2013), 17--24. Google ScholarDigital Library
- Artop - AUTOSAR Tool Platform User Group: http://www.artop.org/. Accessed: 2015-03-11.Google Scholar
- AUTOSAR 2013. AUTOSAR -- The Worldwide Automotive Standard for E/E Systems. ATZextra worldwide. 18, 9 (Oct. 2013), 5--12.Google Scholar
- Ciolkowski, M., Laitenberger, O., Vegas, S. and Biffl, S. 2003. Practical experiences in the design and conduct of surveys in empirical software engineering. Empirical Methods and Studies in Software Engineering. (2003), 104--128.Google Scholar
- Development Partnership AUTOSAR to extend scope of applications to non-automotive areas: 2011. http://www.autosar.org/fileadmin/files/media_release/Development_Partnership_AUTOSAR_to_extend_scope_of_applications_to_non-automotive_areas_EN.pdf. Accessed: 2015-03-11.Google Scholar
- Durisic, D., Staron, M., Tichy, M. and Hansson, J. 2014. Evolution of Long-Term Industrial Meta-Models -- An Automotive Case Study of AUTOSAR. 2014 40th EUROMICRO Conference on Software Engineering and Advanced Applications (Aug. 2014), 141--148. Google ScholarDigital Library
- Eklund, U. and Bosch, J. 2014. Architecture for Embedded Open Software Ecosystems. Journal of Systems and Software. (2014).Google Scholar
- Engineering Standards beyond AUTOSAR: http://www.autosar.org/fileadmin/files/events/2013--11--13--6th-autosar-open/AUTOSAR_Engineering_Standards_Uni_Paderborn_Mueller.pdf. Accessed: 2015-03--11.Google Scholar
- Falessi, D., Babar, M.A.M., Cantone, G. and Kruchten, P. 2010. Applying empirical software engineering to software architecture: challenges and lessons learned. Empirical Software Engineering. 15, 3 (2010), 250--276. Google ScholarDigital Library
- Fürst, S. 2009. AUTOSAR -- A Worldwide Standard is on the Road. 14th International VDI Congress Electronic Systems for Vehicles (2009).Google Scholar
- Future Vehicle Software Architectures - Fraunhofer ESK: http://www.esk.fraunhofer.de/en/projects/adaptives_bordnetz.html. Accessed: 2015-03-09.Google Scholar
- Home: AUTOSAR: http://www.autosar.org/. Accessed: 2015-03-09.Google Scholar
- Jaspar WebSite - Jaspar HOME english: https://www.jaspar.jp/english/index_e.php. Accessed: 2015-03-09.Google Scholar
- Krdzalic, G. and Driss, A. 2014. Software Architecture Without Autosar. Auto Tech Review. 3, 4 (Apr. 2014), 28--31.Google ScholarCross Ref
- Martínez-Fernández, S., Ayala, C.P., Franch, X. and Marques, H. 2013. Benefits and drawbacks of reference architectures. Software Architecture. 7th European Conference, ECSA 2013, Montpellier, France, July 1--5, 2013. Proceedings (2013), 307--310. Google ScholarDigital Library
- Martínez-Fernández, S., Ayala, C.P., Franch, X., Marques, H. and Ameller, D. 2014. Towards Guidelines for Building a Business Case and Gathering Evidence of Software Reference Architectures in Industry. Journal of Software Engineering Research and Development (JSERD). 2, 7 (2014).Google Scholar
- Overview on AUTOSAR Development: 2013. http://www.autosar.org/fileadmin/files/events/2013-11-13-6th-autosar-open/AUTOSAR_Keynote_PSA_Salessy.pdf. Accessed: 2015-03-11.Google Scholar
- Runeson, P. and Höst, M. 2009. Guidelines for conducting and reporting case study research in software engineering. Empirical software engineering. 14, 2 (2009), 131--164. Google ScholarDigital Library
- Seddon, P.B. and Scheepers, R. 2011. Towards the improved treatment of generalization of knowledge claims in IS research: drawing general conclusions from samples. European Journal of Information Systems. 21, 1 (Apr. 2011), 6--21.Google Scholar
- Selim, G.M.K., Wang, S., Cordy, J.R. and Dingel, J. 2013. Model transformations for migrating legacy deployment models in the automotive industry. Software & Systems Modeling. 14, 1 (Jul. 2013), 365--381. Google ScholarDigital Library
- Wiesbaden, S.A.M. "AUTOSAR has Become Mature and Accepted." ATZextra worldwide. 18, 9, 13--15.Google Scholar
- Wohlin, C., Höst, M. and Henningsson, K. 2003. Empirical research methods in software engineering. Empirical Methods and Studies in Software Engineering. (2003), 7--23.Google Scholar
Index Terms
- A Survey on the Benefits and Drawbacks of AUTOSAR
Recommendations
Benefits and drawbacks of software reference architectures
ContextSoftware Reference Architectures (SRAs) play a fundamental role for organizations whose business greatly depends on the efficient development and maintenance of complex software applications. However, little is known about the real value and ...
A Survey of Controlled Experiments in Software Engineering
The classical method for identifying cause-effect relationships is to conduct controlled experiments. This paper reports upon the present state of how controlled experiments in software engineering are conducted and the extent to which relevant ...
An aspect-oriented reference architecture for Software Engineering Environments
Abstract: Reusable and evolvable Software Engineering Environments (SEEs) are essential to software production and have increasingly become a need. In another perspective, software architectures and reference architectures have played a significant role ...
Comments