How to meet compliance to software architectural design principles 2019-01-1040
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 more formally define the software architecture and verify that the implementation satisfies all of the architecture requirements.
Two factors impacting how many companies approach software architectures include their past history with not defining the architecture and converting existing models/code to comply with the newly defined architecture.
Because defining the software architecture is new for many companies, they do not know what properties are important to specify. Also lacking are techniques needed to verify that the implementation is a “good” architecture and to improve an existing architecture.
This paper/talk 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