Incident and Accident Investigation Techniques to Inform Model-Based Design of Safety-Critical Interactive Systems

Basnyat, Sandra; Chozos, Nick; Johnson, Chris; Palanque, Philippe

doi:10.1007/11752707_5

Cited by 11 publications

(10 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We argue that precision is key to increasing all aspects of system quality including reliability, usability, efficiency, and that MDD offers an approach that provides precision from a range of appropriate perspectives. MDD is increasingly being used for user-centred aspects of systems such as HCI [27,25,24] and safety [1].…”

Section: Model Driven Developmentmentioning

confidence: 99%

A Domain Specific Language for Contextual Design

Barn

Clark

2010

Human-Centred Software Engineering

View full text Add to dashboard Cite

Abstract. This paper examines the role of user-centered design (UCD) approaches to design and implementation of a mobile social software application to support student social workers in their work place. The experience of using a variant of UCD is outlined. The principles and expected norms of UCD raised a number of key lessons. It is proposed that these problems and lessons are a result of the inadequacy of precision of modeling the outcomes of UCD, which prevents model driven approaches to method integration between UCD approaches. Given this, it is proposed that the Contextual Design method is a good candidate for enhancing with model driven principles. A subset of the Work model focussing on Cultural and Flow models are described using a domain specific language and supporting tool built using the MetaEdit+ platform.

show abstract

Section: Model Driven Developmentmentioning

confidence: 99%

A Domain Specific Language for Contextual Design

Barn

Clark

2010

Human-Centred Software Engineering

View full text Add to dashboard Cite

show abstract

“…Responsibilities therefore provide a different type of abstraction from other approaches that have been proposed for modelling socio-technical-systems, such as goal [18] or activity [1] oriented approaches. Describing a socio-technical system in terms of responsibilities is concerned with monitoring and managing some part of the state of a socio-technical system, rather than the performance of specific task or activity.…”

Section: Introductionmentioning

confidence: 99%

Formalising Responsibility Modelling for Automatic Analysis

Simpson

Storer

2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. Modelling the structure of social-technical systems as a basis for informing software system design is a difficult compromise. Formal methods struggle to capture the scale and complexity of the heterogeneous organisations that use technical systems. Conversely, informal approaches lack the rigour needed to inform the software design and construction process or enable automated analysis. We revisit the concept of responsibility modelling, which models social technical systems as a collection of actors who discharge their responsibilities, whilst using and producing resources in the process. Responsibility modelling is formalised as a structured approach for socio-technical system requirements specification and modelling, with well-defined semantics and support for automated structure and validity analysis. The effectiveness of the approach is demonstrated by two case studies of software engineering methodologies.

show abstract

“…However, the problem of integrating the findings in future system and safety analysis remains unresolved. This problem is somewhat addressed in Basnyat et al [1] through the use of Goal Structuring Notation (GSN) [8] but is restricted to analysis of single accidents and does not support learning across a large set of accidents in a system domain.…”

Section: Introductionmentioning

confidence: 99%

Modeling and Learning Interaction-based Accidents for Safety-Critical Software Systems

Mahmood

Kazmierczak

Kelly

et al. 2007

14th Asia-Pacific Software Engineering Conference (APSEC'07)

View full text Add to dashboard Cite

Analyzing accidents is a vital exercise in the development of safety-critical software systems to prevent past accidents from reoccurring in the future. Current practices such as causal event analysis are insufficient in light of a growing trend of accidents involving complex interactions between components with and without the occurrence of failures. Furthermore, the reuse of accident knowledge in current practices relies heavily on human expert recall and interpretation. In this paper, we propose an ontological classification mechanism to acquire and reuse knowledge from past accidents that focuses on the interactions taking place in a system. A set of knowledge bases are constructed independently using a feature-based classification and a domain specific ontology to organize the term spaces of each feature. Similarity mechanisms are introduced to retrieve and integrate the acquired knowledge into the new system analyses. Our experiments show how our approach reuses accident knowledge to uncover potential safety concerns in future safety analysis that may otherwise have been incorrectly classified in traditional approaches.

show abstract

Incident and Accident Investigation Techniques to Inform Model-Based Design of Safety-Critical Interactive Systems

Cited by 11 publications

References 7 publications

A Domain Specific Language for Contextual Design

A Domain Specific Language for Contextual Design

Formalising Responsibility Modelling for Automatic Analysis

Modeling and Learning Interaction-based Accidents for Safety-Critical Software Systems

Contact Info

Product

Resources

About