Application of total quality management techniques to safety analysis in software product development Online publication date: Tue, 08-Jul-2003
by Gary P. Moynihan, Paul S. Ray, Robert G. Batson, William G. Nichols
International Journal of Technology Management (IJTM), Vol. 21, No. 3/4, 2001
Abstract: The safety level of any system may be defined as the probability that no catastrophic accident is expected to occur during system operation, for a specified period of time. The purpose of software safety analysis is to reduce system risk, due to software malfunctions, to an acceptable level. Conventional software safety analysis techniques are reactive in orientation. They are intended to identify software faults as part of a post-programming evaluation procedure. A more cost-effective approach would be to avoid introducing the faults into the computer code. This paper discusses the ongoing establishment of a development methodology that would incorporate this proactive approach to software safety analysis, by applying the concepts of total quality management. This research provides a linkage of software engineering to such classical industrial engineering activities as safety analysis and quality control.
Existing subscribers:
Go to Inderscience Online Journals to access the Full Text of this article.
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Technology Management (IJTM):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email subs@inderscience.com
Our Blog 
Follow us on Twitter 
Visit us on Facebook