Safety oriented software engineering process for autonomous robots

Gribov, Vladislav; Voos, Holger

doi:10.1109/etfa.2013.6647969

Cited by 9 publications

(10 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The topic of a safetyoriented architecture for autonomous robots has received growing attention over the past years. Some issues, however, still have to be addressed (as already mentioned in [13]): (1) to provide a link between risk accentuation and SW architecture to demonstrate a chain of evidence (helpful for the standardization and certification), (2) to consider the relevant safety standard ISO 13482:2014, (3) to consider the software architecture as a part of the software engineering process and (4) to include deployment issues in the context of the software reuse and HW and SW heterogeneity. The approach here tries to incorporate these aspects in a more general approach for safe robot software.…”

Section: Discussionmentioning

confidence: 97%

“…The proposed approach 3.1. Safety representation in the context of safe robot SW The first important issue addressed by our approach is to provide a chain of evidence, showing the safety case and the consistent relation between hazards and corresponding SW parts [13]. The simplified core model of the ISO 13482:2014 linked to the software is shown in Fig.…”

Section: Discussionmentioning

confidence: 99%

“…In this context, the engineering process derived in [13] can be seen as a model-to-model (M2M) transformation from the risk and hazard model to a requirements model and then to the SW model according to the software architecture.…”

Section: Integration In the Software Engineering Processmentioning

confidence: 99%

“…These are clearly new requirements on the SW component and on its deployment. If a component that fulfills these requirements is not available, the corresponding domain engineering process for the development of a novel related component shall be started as suggested in [13].…”

Section: Figure 8 Software Modelmentioning

confidence: 99%

See 3 more Smart Citations

A multilayer software architecture for safe autonomous robots

Gribov

Voos

2014

Proceedings of the 2014 IEEE Emerging Technology and Factory Automation (ETFA)

Self Cite

View full text Add to dashboard Cite

In this paper a safety-oriented model based software architecture for robotic solutions is proposed. The main focus herein is to consider aspects such as real-time, heterogeneity, deployment, modeling and analysis of emerging effects as well as functional safety and to combine all aspects into an overall development approach. The architecture shall capture the complexity caused by the autonomy and mobility of the robot and support the developer with a suitable chain of evidence especially suited for the safety relevant functions. A use case comprising a lightweight robotic manipulator which will be integrated in a mobile service robot underlines the feasibility of this approach.

show abstract

Section: Discussionmentioning

confidence: 97%

Section: Discussionmentioning

confidence: 99%

Section: Integration In the Software Engineering Processmentioning

confidence: 99%

Section: Figure 8 Software Modelmentioning

confidence: 99%

See 2 more Smart Citations

A multilayer software architecture for safe autonomous robots

Gribov

Voos

2014

Proceedings of the 2014 IEEE Emerging Technology and Factory Automation (ETFA)

Self Cite

View full text Add to dashboard Cite

show abstract

“…[19]). The models have addressed specific aspects of the standards, such as their processes [20][21][22], artefact traceability [23,24], system specification [17,18,25], system architecture [26,27], quality-related aspects [28], faults [29], and testing [30]. The models in [8,25] address both process and system specification.…”

mentioning

confidence: 99%

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

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

On the Use of Safety Certification Practices in Autonomous Field Robot Software Development: A Systematic Mapping Study

Ingibergsson

Schultz

Kuhrmann

2015

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Robotics has recently seen an increasing development, and the areas addressed within robotics has extended into domains we consider safety-critical, fostering the development of standards that facilitate the development of safe robots. Safety standards describe concepts to maintain desired reactions or performance in malfunctioning systems, and influence industry regarding software development and project management. However, academia seemingly did not reach the same degree of utilisation of standards. This paper presents the findings from a systematic mapping study in which we study the state-of-the-art in developing software for safety-critical software for autonomous field robots. The purpose of the study is to identify practices used for the development of autonomous field robots and how these practices relate to available safety standards. Our findings from reviewing 49 papers show that standards, if at all, are barely used. The majority of the papers propose various solutions to achieve safety, and about half of the papers refer to non-standardised approaches that mainly address the methodical rather than the development level. The present study thus shows an emerging field still on the quest for suitable approaches to develop safety-critical software, awaiting appropriate standards for this support.

show abstract

Safety oriented software engineering process for autonomous robots

Cited by 9 publications

References 12 publications

A multilayer software architecture for safe autonomous robots

A multilayer software architecture for safe autonomous robots

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

On the Use of Safety Certification Practices in Autonomous Field Robot Software Development: A Systematic Mapping Study

Contact Info

Product

Resources

About