SafetyMet: A Metamodel for Safety Standards

Vara, José Luis de la; Panesar-Walawege, Rajwinder Kaur

doi:10.1007/978-3-642-41533-3_5

Cited by 24 publications

(24 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The specification and validation of the RAF metamodel consists of over two years of extensive and continuous work in the OPENCOSS project, including industrial case studies in the automotive, railway, and avionics domains.! This paper extends the results in [13], where we presented the initial version of the metamodel. The extension is mainly based on: (1) the introduction of new classes and associations in the metamodel and the refinement of others in order to meet further industry requirements and expectations on the specification of safety compliance needs; (2) the provision of further information about the metamodel and its usage; (3) a wider validation of the metamodel, with a higher number of standards (from four to 37 standards) and in the context of three specific industrial case studies, and; (4) feedback from practitioners, including the organization of a workshop with practitioners at which they provided feedback on the metamodel and its use.…”

supporting

confidence: 75%

“…We have selected the terms for naming the concepts in the RAF metamodel from the terminology used in safety standards, related work, and practitionersÕ feedback on their suitability. For example, Reference Assurance Framework was formerly named Safety Standard [13]. This change was based on practitionersÕ opinion regarding the common association of the term safety standard to international standards, but not for example to company-specific or recommended practices.…”

Section: Terminology Differences With Specific Safety Standards!mentioning

confidence: 99%

“…This paper aims to fill this gap by providing a generic, safety standard-independent metamodel for the holistic specification of safety compliance needs. To our knowledge, no other model or metamodel has achieved this objective, except our previous work presented in [13]. Therefore, we provide the first common, unifying model of safety compliance needs for critical systems.!…”

mentioning

confidence: 99%

“…2.2 Related work! As discussed in [13], compliance has received great attention in the requirements engineering and business process management communities, including model-based compliance. Models can also be used for safety-critical system specification.!…”

mentioning

confidence: 99%

“…When compared to the version presented in [13], the RAF metamodel has both grown (e.g. from 12 to 19 classes and from 26 to 33 associations) and been adjusted (e.g.…”

mentioning

confidence: 99%

See 4 more Smart Citations

Model-based specification of safety compliance needs for critical systems: A holistic generic metamodel

Ruíz

Attwood

Espinoza

et al. 2016

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

eprints@whiterose.ac.uk https://eprints.whiterose.ac.uk/ Reuse Unless indicated otherwise, fulltext items are protected by copyright with all rights reserved. The copyright exception in section 29 of the Copyright, Designs and Patents Act 1988 allows the making of a single copy solely for the purpose of non-commercial research or private study within the limits of fair dealing. The publisher or other rights-holder may allow further reproduction and re-use of this version -refer to the White Rose Research Online record for this item. Where records identify the publisher as the copyright holder, users can verify any specific terms of use on the publisher's website. TakedownIf you consider content in White Rose Research Online to be in breach of UK law, please notify us by emailing eprints@whiterose.ac.uk including the URL of the record and the reason for the withdrawal request. Model-Based Specification of Safety Compliance Needs for CriticalSystems: A Holistic Generic Metamodel! Abstract!Context: Many critical systems must comply with safety standards as a way of providing assurance that they do not pose undue risks to people, property, or the environment. Safety compliance is a very demanding activity, as the standards can consist of hundreds of pages and practitioners typically have to show the fulfilment of thousands of safety-related criteria. Furthermore, the text of the standards can be ambiguous, inconsistent, and hard to understand, making it difficult to determine how to effectively structure and manage safety compliance information. These issues become even more challenging when a system is intended to be reused in another application domain with different applicable standards.Objective: This paper aims to resolve these issues by providing a metamodel for the specification of safety compliance needs for critical systems. Method: The metamodel is holistic and generic, and abstracts common concepts for demonstrating safety compliance from different standards and application domains. Its application results in the specification of Òreference assurance frameworksÓ for safety-critical systems, which correspond to a model of the safety criteria of a given standard. For validating the metamodel with safety standards, parts of several standards have been modelled by both academic and industry personnel, and other standards have been analysed. We further augment this with feedback from practitioners, including feedback during a workshop. Results:The results from the validation show that the metamodel can be used to specify safety compliance needs for aerospace, automotive, avionics, defence, healthcare, machinery, maritime, oil and gas, process industry, railway, and robotics. Practitioners consider that the metamodel can meet their needs and find benefits in its use. Conclusion:The metamodel supports the specification of safety compliance needs for most critical computer-based and software-intensive systems. The resulting models can provide an effective means of structuring and managing safety compliance infor...

show abstract

supporting

confidence: 75%

Section: Terminology Differences With Specific Safety Standards!mentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

“…When compared to the version presented in [13], the RAF metamodel has both grown (e.g. from 12 to 19 classes and from 26 to 33 associations) and been adjusted (e.g.…”

mentioning

confidence: 99%

See 3 more Smart Citations

Model-based specification of safety compliance needs for critical systems: A holistic generic metamodel

Ruíz

Attwood

Espinoza

et al. 2016

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

show abstract

Safety Architecture Overview Framework for the Prediction, Explanation and Control of Risks of ERTMS

Schuitemaker

Bonnema

Kuijsten

et al. 2018

Complex Systems Design &Amp; Management

View full text Add to dashboard Cite

Patterns for Certification Standards

Delmas

Pagetti

Polacsek

2020

Advanced Information Systems Engineering

View full text Add to dashboard Cite

One of the absolute preconditions for a safety-critical system to enter the market is to be issued a certificate by the regulating authorities. To this end, the "applicant" must demonstrate the compliance of its product with the domain's standards. The high complexity of this process has led applicants to rely on assurance cases made for certification in the medical, nuclear, or aeronautic domains. In this paper, we propose a generic method that guides the applicant through the specification of assurance cases for a complex standard. Unlike existing works focused on a single context, our objective is to provide an approach that is both generic and domain-agnostic. In order to illustrate this new approach, we present the results of its application on a real-world case study, which pointed out new issues and led to improvements.

show abstract

SafetyMet: A Metamodel for Safety Standards

Cited by 24 publications

References 35 publications

Model-based specification of safety compliance needs for critical systems: A holistic generic metamodel

Model-based specification of safety compliance needs for critical systems: A holistic generic metamodel

Safety Architecture Overview Framework for the Prediction, Explanation and Control of Risks of ERTMS

Patterns for Certification Standards

Contact Info

Product

Resources

About