evel (ASIL) of the function under development, the standard, e.g., prescribes the use of (semi)formal methods for the verification of requirements, (semi-)formal notations for software design, the use of control and data flow ana- lysis techniques, static and semantic code analysis, the use of test case generation, or in-the-loop verificationmechanisms. Furthermore, the standard specifically ac- knowledges the application of model-based development in automotive software engineering. Currently, several of these rather advanced techniques are only required for higher safety integrity levels. Consequently, even though embedded software has become the leading innovation factor in automotive applications, many highly safety-critical automotive functionalities are only reluctantly implemented with software-based solutions. Here, by advancing the applicability and scalability of these advanced technologies and providing support in form of qualified tool chains, a substantial change in the development of automotive software can be achieved, allowing not only to virtualize and thus substitute physical solutions of automotive functions (e.g., X-by-wire solutions), but also to implement a new range of functionalities (e.g., autonomic driving).
CITATION STYLE
Schätz, B. (2010). Certification of Embedded Software – Impact of ISO DIS 26262 in the Automotive Domain (pp. 3–3). https://doi.org/10.1007/978-3-642-16558-0_2
Mendeley helps you to discover research relevant for your work.