The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.08 - August (1991 vol.17)
pp: 830-838
ABSTRACT
<p>Software errors have been studied from various perspectives; however, most investigations have been limited to an individual section or a partial path of the cause-effect relationships of these errors. The bresent study analyzes approximately 700 errors in 4 commercial measuring-control software products, and then identifies the cause-effect relationships of errors occurring during software development. The analysis method used was: (i) defining appropriate observation points along the path leading from cause to effect of a software error, followed by gathering the corresponding data by analyzing each error using Fault Tree Analysis, and (ii) categorizing each observation point?s data, and then summarizing the relationships between two adjoining points using a cross-indexing table. This paper presents four major cause-effect relationships and discusses the effects of the Structured Analysis and Structured Design methods on these relationships.</p>
INDEX TERMS
Software development, cause-effect relationships, case-based error analysis, program faults, human errors, process flaws, structured analysis and structured design, Fault Tree Analysis.
CITATION
Takeshi Nakajo, Hitoshi Kume, "A Case History Analysis of Software Error Cause-Effect Relationships", IEEE Transactions on Software Engineering, vol.17, no. 8, pp. 830-838, August 1991, doi:10.1109/32.83917
39 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool