Abstract:Abstract:Context: Critical systems in domains such as aviation, railway, and automotive are often subject to a formal process of safety certification. The goal of this process is to ensure that these systems will operate safely without posing undue risks to the user, the public, or the environment. Safety is typically ensured via complying with safety standards. Demonstrating compliance to these standards involves providing evidence to show that the safety criteria of the standards are met.
Objective:In order … Show more
“…Their importance is also growing as a result of their recent introduction in domains such as automotive and healthcare [4]. An example of system assurance is safety certification, which can be roughly defined as a formal assurance by a third party (e.g., a certification authority) that a system fulfils its safety requirements and thus that the system does not pose undue risks to people, property, or the environment [5]. This formal assurance is typically based on the compliance with safety standards, such as IEC 61508 for electrical, electronic, and programmable electronic systems in a wide range of industries, DO-178C for avionics, the CENELEC standards for railway (e.g., EN 50128), and ISO 26262 for the The analysis has resulted in the identification of elements that need to be clarified, might be inconsistent, might not be suitable, or could be included in SACM for safety evidence management.…”
Section: Fig 1 Example Of Assurance Cases With (A) Gsn and (B) Caementioning
confidence: 99%
“…Other publications have indicated the potential relationship of SACM with their proposals for safety evidence lifecycle [23], for characterising safety evidence assessment [24], and for characterising safety evidence in general [25,26]. Nair et al [5] indicate that SACM does not provide a thorough and sufficiently detailed analysis of the possible evidence types to provide for safety certification and of how to structure and assess evidence. Li et al [27] consider that SACM lacks support for the evidence collection process.…”
Section: Related Workmentioning
confidence: 99%
“…To the best of our knowledge, no publication up to now has studied in depth how safety evidence management can be addressed with all the classes and associations of SACM. Regarding prior work on safety evidence management, recent publications have presented large studies on the state of the art [5] and on the state of the practice [6,7]. It is also easy to find deliverables in research projects that have reviewed the literature and industrial practices (e.g., [26]).…”
Section: Related Workmentioning
confidence: 99%
“…For example, the inexistence of residual errors cannot be demonstrated. Therefore, and as introduced above, safety evidence can be defined as artefacts that contribute to developing confidence in the safe operation of a system and that can be used to show the fulfilment of the criteria of a safety standard [5]. For example, a hazard log cannot be used as proof of a complete absence of hazards for a system, but can help a certifier develop confidence in its safe operation.…”
Section: Notion Of Evidencementioning
confidence: 99%
“…4), Evidence Item is defined as an abstract class that represents objects that are collected as evidence. For example, a hazard log would be a document, and an evidence group might be created for compiling this log and other artefacts related to safety analysis results [5], such as documents with fault tree analysis, failure mode and effect analysis, etc. In our opinion, and in line with the explanation in Section 3.1, some classes that specialise Evidence Item should not be regarded as safety evidence.…”
“…Their importance is also growing as a result of their recent introduction in domains such as automotive and healthcare [4]. An example of system assurance is safety certification, which can be roughly defined as a formal assurance by a third party (e.g., a certification authority) that a system fulfils its safety requirements and thus that the system does not pose undue risks to people, property, or the environment [5]. This formal assurance is typically based on the compliance with safety standards, such as IEC 61508 for electrical, electronic, and programmable electronic systems in a wide range of industries, DO-178C for avionics, the CENELEC standards for railway (e.g., EN 50128), and ISO 26262 for the The analysis has resulted in the identification of elements that need to be clarified, might be inconsistent, might not be suitable, or could be included in SACM for safety evidence management.…”
Section: Fig 1 Example Of Assurance Cases With (A) Gsn and (B) Caementioning
confidence: 99%
“…Other publications have indicated the potential relationship of SACM with their proposals for safety evidence lifecycle [23], for characterising safety evidence assessment [24], and for characterising safety evidence in general [25,26]. Nair et al [5] indicate that SACM does not provide a thorough and sufficiently detailed analysis of the possible evidence types to provide for safety certification and of how to structure and assess evidence. Li et al [27] consider that SACM lacks support for the evidence collection process.…”
Section: Related Workmentioning
confidence: 99%
“…To the best of our knowledge, no publication up to now has studied in depth how safety evidence management can be addressed with all the classes and associations of SACM. Regarding prior work on safety evidence management, recent publications have presented large studies on the state of the art [5] and on the state of the practice [6,7]. It is also easy to find deliverables in research projects that have reviewed the literature and industrial practices (e.g., [26]).…”
Section: Related Workmentioning
confidence: 99%
“…For example, the inexistence of residual errors cannot be demonstrated. Therefore, and as introduced above, safety evidence can be defined as artefacts that contribute to developing confidence in the safe operation of a system and that can be used to show the fulfilment of the criteria of a safety standard [5]. For example, a hazard log cannot be used as proof of a complete absence of hazards for a system, but can help a certifier develop confidence in its safe operation.…”
Section: Notion Of Evidencementioning
confidence: 99%
“…4), Evidence Item is defined as an abstract class that represents objects that are collected as evidence. For example, a hazard log would be a document, and an evidence group might be created for compiling this log and other artefacts related to safety analysis results [5], such as documents with fault tree analysis, failure mode and effect analysis, etc. In our opinion, and in line with the explanation in Section 3.1, some classes that specialise Evidence Item should not be regarded as safety evidence.…”
The processes used to develop software need to comply with normative requirements (e.g., standards and regulations) to align with the market and the law. Manual compliance checking is challenging because there are numerous requirements with changing nature and different purposes. Despite the importance of automated techniques, there is not any systematic study in this field. This lack may hinder organizations from moving toward automated compliance checking practices. In this paper, we characterize the methods for automatic compliance checking of software processes, including used techniques, potential impacts, and challenges. For this, we undertake a systematic literature review (SLR) of studies reporting methods in this field. As a result, we identify solutions that use different techniques (e.g., anthologies and metamodels) to represent processes and their artifacts (e.g., tasks and roles). Various languages, which have diverse capabilities for managing competing and changing norms, and agile strategies, are also used to represent normative requirements. Most solutions require tool‐support concretization and enhanced capabilities to handle processes and normative diversity. Our findings outline compelling areas for future research. In particular, there is a need to select suitable languages for consolidating a generic and normative‐agnostic solution, increase automation levels, tool support, and boost the application in practice by improving usability aspects.
Context and motivation]Safety-critical systems in application domains such as aerospace, automotive, healthcare, and railway are subject to assurance processes to provide confidence that the systems do not pose undue risks to people, property, or the environment. The development of safety cases is usually part of these processes to justify that a system satisfies its safety requirements and thus is dependable. [Question/problem] Although safety cases have been used in industry for over two decades, their management still requires improvement. Important weaknesses have been identified and means to assess the quality of safety cases are limited. [Principal ideas/results] This paper presents a research preview on the assessment of the quality of safety cases. We explain how the area should develop and present our preliminary work towards enabling the assessment with Verification Studio, an industrial tool for system artefact quality analysis. [Contribution] The insights provided allow researchers and practitioners to gain an understanding of why safety case quality requires further investigation, what aspects must be considered, and how quality assessment could be performed in practice.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.