This content is not included in your SAE MOBILUS subscription, or you are not logged in.
How to Meet Compliance to Software Architecture Design Principles
ISSN: 0148-7191, e-ISSN: 2688-3627
Published April 02, 2019 by SAE International in United States
Annotation ability available
As demand for ADAS and autonomous systems grows, as well as the need to avoid lawsuits from software bugs, the desire for high integrity and functional safety applications is growing. While there are many process and technical factors that contribute to the overall quality of the software, it is becoming increasingly important to define the software architecture and verify that the implementation satisfies all of the architecture requirements. Because defining the software architecture is new for many companies, there is a need to know what properties are important to specify. Also lacking are techniques needed to verify that the implementation is a “good” architecture. This paper will address: important qualities to include in the software architecture definition; discussion on what ISO 26262 recommends for the software architecture; recommendations for implementing the software architecture in Simulink®; ways to measure the quality of the software architecture; elaboration of refactoring operations to improve compliance with architectural design principles
CitationRanville, S. and Bachmann, F., "How to Meet Compliance to Software Architecture Design Principles," SAE Technical Paper 2019-01-1040, 2019, https://doi.org/10.4271/2019-01-1040.
- Mäurer et al. On Bringing Object-Oriented Software Metrics into the Model-Based World - Verifying ISO 26262 Compliance in Simulink 8th International Conference, SAM 2014 Valencia, Spain 2014
- Gerlitz , T. , Minh Tran , Q. , and Dziobek , C. Detection and Handling of Model Smells for MATLAB/Simulink Models Proc. Proceedings of the International Workshop on Modelling in Automotive Software Engineering, CEUR 2015 13 22