References
Adams, E. 1984. Optimizing preventative service of software products. IBM Research Journal 28(1): 2–14.
Boehm, B. W. 1981. Software Engineering Economics. Prentice-Hall.
Fenton, N., Neil, M., and Ostrolenk, G. 1995. Metrics and models for predicting software defects. Technical Report CSR/10/02 Centre for Software Reliability, City University, UK.
Fenton, N. E. 1991. Software Metrics—A Rigorous Approach. London: Chapman & Hall.
Henry, S., and Kafura, D. 1981. Software structure metrics based on information flow. IEEE Transactions on Software Engineering 7(5): 510–518.
Khoshgoftaar, T. M., and Kalaichelyan, K. S. 1995. Detection of fault-prone programs modules in a very large telecommunication system. The Sixth International Symposium on Software Reliability Touluse, France, 24–33.
Munson, J. C., and Khoshgoftaar, T. M. 1992. The detection of fault-prone programs. IEEE Transactions on Software Engineering 18(5): 423–433.
Ohlsson, N. 1996a. Software quality engineering by early identification of fault-prone modules, Licentiate Thesis No 575, Dept. of Computer and Information Science, Linköping University, Sweden.
Ohlsson, N., Helander, M., and Wohlin, C. 1996b. “Quality improvement by identification of fault-prone modules using software design metrics. Sixth International Conference of Software Quality Ottawa, Canada, 1–13.
Schulmeyer, G. G., and McManus, J. I., eds. 1987. Handbook of Software Quality Assurance. van Nostrand Reinhold Company.
Shen, V. Y., Yu, T.-L., Theabaut, S. M., and Paulsen, L. R. 1985. “Identifying error-prone software—an empirical study. IEEE Transactions on Software Engineering SE-11(4): 317–323.
Siegel, S., and Jr., N. J. C. 1988. Nonparametrics Statistics for the Behavioural Sciences. McGraw-Hill, second edition.
Turner, K. J., ed. 1993. Using Formal Description Techniques—An Introduction to ESTELLE, LOTOS and SDL. John Wiley & Sons.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Ohlsson, N., Eriksson, A.C. & Helander, M. Early Risk-Management by Identification of Fault-prone Modules. Empirical Software Engineering 2, 166–173 (1997). https://doi.org/10.1023/A:1009757419320
Issue Date:
DOI: https://doi.org/10.1023/A:1009757419320