Object-Oriented Software Construction
Object-Oriented Software Construction
A contract-based approach to designing safe systems
SCS '03 Proceedings of the 8th Australian workshop on Safety critical systems and software - Volume 33
Modelling Support for Design of Safety-Critical Automotive Embedded Systems
SAFECOMP '08 Proceedings of the 27th international conference on Computer Safety, Reliability, and Security
A road-map for enabling system analysis of AUTOSAR-based systems
Proceedings of the 1st Workshop on Critical Automotive applications: Robustness & Safety
A Fault-aware Sensor Architecture for Cooperative Mobile Applications
IPDPSW '12 Proceedings of the 2012 IEEE 26th International Parallel and Distributed Processing Symposium Workshops & PhD Forum
| Hi-index | 0.00 |
Looking at functional safety of vehicles, we have seen an evolution from federated to integrated E/E architectures. When extending the way of specifying and analysing functional safety to also address cooperative functionality, it is not possible to keep a static view of the boundaries of the system for which to ensure safety. This is because the set of vehicles realizing a cooperative function may change a lot during the execution of the cooperative function. In this work in progress paper we suggest to move part of the task to show safety, from design time to run time. This implies that it will become necessary to monitor the system at run time, continuously calculate its quality and share that information between the individual vehicles to assert that the system is safe. In order to accomplish this, appropriate metrics are needed, both during design time and run time. Inspired by information theory, this paper sketches some common properties for metrics, and indicates how that can be beneficial.