Abstract
Even if the application developers produce software in accordance with the customer requirements, they cannot guarantee that the software will behave in a safe way during the lifetime of the software. We define a system as safe if the risks related to its use are judged to be acceptable [1]. Safety must not be confused with security which broadly is defined as keeping the system unavailable for people who should not be able to access it. In this paper we introduce the Failure Mode and Effect Analysis (FMEA) technique into the software development process to improve the safety of business-critical software. In a business environment this means that the system does not behave in such a way that it causes the customer or his users to lose money or important information. We will use the term “business-safe” for this characteristic.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
Lowrance, W.W.: Of acceptable risk: Science and the determination of safety. William Kaufman, Inc., Los Altos (1976)
Leveson, N.G.: Safeware – System safety and computers. Addison-Wesley Publish-ing Company, Inc., Reading (1995) ISBN: 0-201-11972-2
Guidelines for Considering a Software Intensive System within FMECA Studies, ESTEC (January 1992)
Poppendieck, M., Poppendieck, T.: Lean Software Development – An agile toolkit. Addison-Wesley, Reading (2003) ISBN: 0-321-15078-3
Sindre, G., Opdahl, A.L.: Eliciting Security Requirements with Misuse Cases. Requirements Engineering Journal 10(1), 34–44 (2005)
Johannessen, P., Grante, C., Alminger, A., Eklund, U., Torin, J.: Hazard Analysis in Object Oriented Design of Dependable Systems. IEEE, Los Alamitos (2001)
Craig, J.H.: A software reliability methodology using software sneak analysis, SW FMEA and the integrated system analysis approach. In: Reliability and Maintainability Symposium, 2003. Annual, 27-30 January (2003)
Samatis, D.H.: Failure Mode and Affect Analysis. FMEA from theory to Execution. ASQ Quality Press, Milwaukee (1995) ISBN: 087389300X
Hecht, H., Xuegao, A., Hecht, M.: Computer-Aided Software FMEA. SoHaR Incorporated, Culver City CA Los Angeles (2003)
Travassos, G.H., Shull, F., Carver, J.R., Basili, V.R.: Reading Tech-niques for OO Design Inspections. In: Proceedings of the Twenty-fourth Annual Software Engineering Workshop (1999)
Fowler, M., Scott, K.: UML distilled, 2nd edn. Addison-Wesley, Reading, ISBN: 0-201-65783-X
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2005 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Lauritsen, T., Stålhane, T. (2005). Safety Methods in Software Process Improvement. In: Richardson, I., Abrahamsson, P., Messnarz, R. (eds) Software Process Improvement. EuroSPI 2005. Lecture Notes in Computer Science, vol 3792. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11586012_10
Download citation
DOI: https://doi.org/10.1007/11586012_10
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-30286-5
Online ISBN: 978-3-540-32271-9
eBook Packages: Computer ScienceComputer Science (R0)