A metric-based safety workflow for electric/electronic architectures of vehicles
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
Model-Based consistency checks of electric and electronic architectures against requirements
MODELS'11 Proceedings of the 2011th international conference on Models in Software Engineering
Early safety evaluation of design decisions in E/E architecture according to ISO 26262
Proceedings of the 3rd international ACM SIGSOFT symposium on Architecting Critical Systems
Requirement decomposition and testability in development of safety-critical automotive components
SAFECOMP'12 Proceedings of the 31st international conference on Computer Safety, Reliability, and Security
| Hi-index | 0.00 |
The draft international standard under development ISO 26262 describes a safety lifecycle for road vehicles and thereby influences all parts of development, production, operation and decommissioning. All systems affected by the standard, like anti-trap protection or advanced driver assistance systems, contain hierarchical electric and electronic parts. After publishing the final version, they all should be designed, assessed and documented to the demands of ISO 26262. The intercommunication structure of the distributed automotive control system, consisting of electronic control units (ECU), sensors and actuators, and functions computed by this control system, are specified by the electric and electronic architecture (EEA). In the context of the ISO 26262, the EEA contributes to the intercommunication of distributed, safety related functions plus the determination of architectures. This article discusses the impact of the standard on the EEA development and the handling of safety requirements demanded by ISO 26262 during early development phases.