Abstract
Most formal assessment and evaluation techniques and standards assume that software can be analysed like any physical item. In safety-critical systems, software is an important component providing functionality. Often it is also the most difficult component to assess. Balanced use of process assessment and product evaluation methods is needed, because lack of transparency in software must be compensated with a more formal development process. Safety case is an effective approach to demonstrate safety, and then both process and product are necessary evidence types. Safety is also a likely candidate to be approached as a process quality characteristic. Here we present a tentative set of process quality attributes that support achievement of safety requirements of a software product.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Leveson, N.G.: Engineering A Safer World: Systems Thinking Applied to Safety. MIT (2011)
Varkoi, T.: Safety as a Process Quality Characteristic. In: Proceedings of SPICE 2013 Conference (accepted for publication, 2013)
ISO/IEC 25010:2011, Systems and software engineering–Systems and software Quality Requirements and Evaluation (SQuaRE)–System and software quality models (2011)
IEC 61508-3 Ed. 2.0, Functional safety of electrical/electronic/programmable electronic safety-related systems – Part 3: Software requirements (2009)
ISO/IEC 15504-5:2006, Information technology – Process assessment – Part 5: An exemplar Process Assessment Model (2006)
ISO/IEC 33001 DIS, Information technology – Process assessment – Concepts and terminology. ISO/IEC (2013)
FiSMA 2011-1: S4N Method Description - Nuclear SPICE PRM and PAM. FiSMA (2012)
IEC 61508-7 Ed. 2.0, Functional safety of electrical/electronic/programmable electronic safety-related systems – Part 7: Overview of techniques and measures (2009)
ISO 26262, Road vehicles – Functional safety, ISO (2011)
Inge, J.R.: The Safety Case: Its development and use in the United Kingdom. In: Equipment Safety Assurance Symposium, Bristol, UK (2007)
Johnson, C.W., Robins, D.A.: Myths and barriers to the introduction of safety cases in space-based systems. In: 29th International Systems Safety Society, Las Vegas, USA (2011)
Rasche, T.: Development of a safety case methodology for the Minerals Industry – a discussion paper. Minerals Industry Safety and Health Center (2001)
Stensrud, E., Skramstad, T., Li, J., Xie, J.: Towards Goal-Based Software Safety Certification Based on Prescriptive Standards. In: First International Workshop on Software Certification, WoSoCER (2011)
Weaver, R.A., McDermid, J.A., Kelly, T.P.: Software Safety Arguments: Towards a Systematic Categorisation of Evidence. In: Proceedings of the 20th International System Safety Conference (ISSC), System Safety Society, Denver (2002)
Flood, M., Habli, I.: Multi-Viewpoint Safety Cases. In: Proceedings of the 6th IET International System Safety Conference, Birmingham, United Kingdom (2011)
Kelly, T.: Arguing Safety - A Systematic Approach to Managing Safety Cases. PhD thesis, Department of Computer Science, The University of York (1998)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Nevalainen, R., Ruiz, A., Varkoi, T. (2013). Making Software Safety Assessable and Transparent. In: McCaffery, F., O’Connor, R.V., Messnarz, R. (eds) Systems, Software and Services Process Improvement. EuroSPI 2013. Communications in Computer and Information Science, vol 364. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-39179-8_1
Download citation
DOI: https://doi.org/10.1007/978-3-642-39179-8_1
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-39178-1
Online ISBN: 978-3-642-39179-8
eBook Packages: Computer ScienceComputer Science (R0)