Authoring IEC 61508 Based Software Development Process Models

Porres, Iván; Heidenberg, Jeanette; Weijola, Max; Nordman, Kristian; Truşcan, Dragoş

doi:10.1007/978-3-642-39259-7_22

Cited by 2 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Porres et al [31] reported on how the IEC 61508 generic, process-oriented standard when employed during the development of safety-critical systems demands rigorous documentation of the development process. However, a survey they conducted showed that the documentation of the process is often informal, to the point that it may be preferable to employ IEC 61508 as a process itself.…”

Section: Safety-critical Software Engineeringmentioning

confidence: 99%

Recent developments in product-focused software process improvement

Graziotin

Jedlitschka

2013

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

This report summarizes the presentations and discussions that happened at PROFES 2013, the 14th International Conference on ProductFocused Software Process Improvement, which was held June 12-14, 2013 in Paphos, Cyprus. The main theme of PROFES is software process improvement (SPI) motivated by product, process, and service quality needs. PROFES 2013 addressed both quality engineering and management topics, divided into the areas of Decision Support in

show abstract

Section: Safety-critical Software Engineeringmentioning

confidence: 99%

Recent developments in product-focused software process improvement

Graziotin

Jedlitschka

2013

SIGSOFT Softw. Eng. Notes

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

Authoring IEC 61508 Based Software Development Process Models

Cited by 2 publications

References 6 publications

Recent developments in product-focused software process improvement

Recent developments in product-focused software process improvement

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

Contact Info

Product

Resources

About