This content is not included in your SAE MOBILUS subscription, or you are not logged in.
Methodology for Migration of Traditional Application Software to AUTOSAR Architecture
ISSN: 0148-7191, e-ISSN: 2688-3627
Published April 01, 2014 by SAE International in United States
Annotation ability available
AUTOSAR introduces standardization of software development in three areas, namely Architecture, Application Interfaces and Methodology.
The most frequently employed method for application SW migration is the Bottom-up approach, wherein the existing software architecture is reused with no or minimal change. This approach can introduce software performance and maintainability issues. Still, it is often preferred, as it is relatively easy to implement, because of experience with the architecture and the need for quick results.
In the Top-down approach, on the other hand, the entire AUTOSAR architecture is created from a Vehicle System and Control System perspective. The Top-down method has potential for a superior result, although it is effort-intensive.
A custom methodology for migration from a traditional SW architecture to AUTOSAR architecture is described in this paper. The approach seeks an optimum combination of the Top-down and the Bottom-up approaches to obtain a suitable compromise between the lower effort of the latter and the completeness of the former approach.
The migration methodology is derived by unifying
- 1Standard architecture practices,
- 2AUTOSAR architecture implementation methods, and
- 3System Architecture Knowledge
Three levels of migration are defined in the proposed methodology:
- 1Level 0: Migration of traditional to AUTOSAR architecture with no implementation changes
- 2Level 1: Migration by using re-factoring techniques for structural and implementation changes
- 3Level 2: Migration by re-designing system, control architecture and Level 1 changes
The need for re-architecting the software to meet the architecture requirements is determined, both for the entire software and also for the individual software components. Following the up-front evaluation, the migration of the software is implemented at the required migration levels.
|Technical Paper||A Real-Time Virtual Simulation Environment for Advanced Driver Assistance System Development|
CitationAnantharam, R. and Kulkarni, P., "Methodology for Migration of Traditional Application Software to AUTOSAR Architecture," SAE Technical Paper 2014-01-0191, 2014, https://doi.org/10.4271/2014-01-0191.
- AUTOSAR: Specification of Interaction with Behavioral Models V 1.0.5. AUTOSAR, R3.0 Rev 0002 http://www.autosar.org/download/R3.0/AUTOSAR_InteractionBehavioralModels.pdf
- Krause M. , Bringmann O. , Hergenhan A. , Tabanoglu G. , and Rosentiel W. Timing simulation of interconnected AUTOSAR software components Design, Automation & Test in Europe Conference & Exhibition, 2007 07 April 2007
- AUTOSAR: Applying Simulink to AUTOSAR V 1.0.5. AUTOSAR, R3.0 Rev 0001 http://www.autosar.org/download/AUTOSAR_SimulinkStyleguide.pdf
- IEEE Recommended practice for Architectural Descriptions of Software-Intensive Systems IEEE Std-1471-2000
- Kang , K.C. and Cohen , S.G. and Hess , J.A. and Novak , W.E. and Peterson , A.S. Feature-oriented domain analysis (FODA) feasibility study Technical Report CMU/SEI-90-TR-021 SEI, Carnegie Mellon University November 1990
- Sandmann , G. , Thompson , R. Development of AUTOSAR Software Components within Model-Based Design. Tech http://www.mathworks.com/tagteam/49372_2008-01-0383_Sandmann_Final_1.10.08.pdf
- Fowler Martin Refactoring: Improving the Design of Existing Code Boston Addison-Wesley 1999