Abstract
The desire for closure after an accident may be hastened by the attribution of blame. This is particularly attractive in situations where complex factors may distance the understanding of attribution from those who may not be familiar with all vectors towards the failure causing the accident. The keyword here is ‘accident’ suggesting that deliberate action/s have not been the cause. It is pertinent to establish systems – such as those responsible for process control where it may be argued that the risk of remote, malicious intervention was not readily foreseeable at the time of their realization. The paper puts forward a framework for the elaboration of requirements with a focus on organizational factors as a way of teasing out problems in early development. The objective is to achieve a sense of assurance that due diligence is both done and seen to be done in an increasingly non-deterministic operational environment.
Recommended Citation
Garfield, Joy and Dresner, Daniel, "J'Accuse! ATTRIBUTION OF BLAME WHEN SOFTWARE IS AN ACTOR (11)" (2016). UK Academy for Information Systems Conference Proceedings 2016. 18.
https://aisel.aisnet.org/ukais2016/18