Skip to main content

Fault Links: Exploring the Relationship Between Module and Fault Types

  • Conference paper
Dependable Computing - EDCC 5 (EDCC 2005)

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 3463))

Included in the following conference series:

Abstract

Fault links represent relationships between the types of mistakes made and the type of module being developed or modified. The existence of such fault links can be used to guide code reviews, walkthroughs, allocation of verification and validation resources, testing of new code development, as well as code maintenance. We present an approach for categorizing code faults and code modules, and a means for examining relationships between the two. We successfully applied our approach to two case studies.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Allen, M., Yeh, W.: Introduction to Measurement Theory. Brooks/Cole Publishing (1979)

    Google Scholar 

  2. Apache modules and problem reports, Apache HTTP server version 1.3.24, http://httpd.apache.org/docs/mod/index-bytype.html

  3. Basili, V.R., Perricone, B.T.: Software Errors and Complexity: An Empirical In-vestigation. Communications of the ACM 27(1), 42–51 (1984)

    Article  Google Scholar 

  4. Beizer, B.: Software Testing Techniques, 2nd edn. Van Nostrand Reinhold, Inc., New York (1990) ISBN 0-442-20672-0

    Google Scholar 

  5. Bieman, J., Andrews, A., Yang, H.: Analysis of change-proneness in software using patterns: a case study. In: Seventh European Conference on Software Maintenance and Reengineering, Benevento, Italy (March 2003) (submitted)

    Google Scholar 

  6. Bieman, J., Jain, D., Yang, H.: Design patterns, design structure, and program changes: an industrial case study. In: Proceedings of the International Conference on Software Main-tenance, Florence, Italy, November 6–10 (2001)

    Google Scholar 

  7. Centre of Software Maintenance, University of Durham, England, http://www.dur.ac.uk/computer.science/research/csm/rip/introduction.html

  8. Cooper, A.: About face: the essentials of user interface design. In: IDG Books Worldwide, Foster City, CA (1995)

    Google Scholar 

  9. Duncan, I.M.M., Robson, D.J.: An exploratory study of common coding faults in C programs. A technical report, Centre for Software Maintenance, University of Durham, England (May 1991)

    Google Scholar 

  10. Endres, A.: An Analysis of Errors and Their Causes in System Programs. In: Proceedings of the 1975 International Conference on Reliable Software, in SIGPLAN Notices, vol. 10(6), pp. 327–336 (1975)

    Google Scholar 

  11. Fenton, N.E., Ohlsson, N.: Quantitative Analysis of Faults and Failures in a Complex Software System. IEEE Transactions on Software Engineering 26(8), 797–814 (2000)

    Article  Google Scholar 

  12. Freimut, B.: Developing and Using Defect Classification Schemes, Fraunhofer IESE IESE-Report No. 072.01/E, Version 1.0 (September 2001)

    Google Scholar 

  13. Gall, H., Hajek, K., Jazayeri, M.: Detection of logical coupling based on product re-lease history. In: Procs. International Conference on Software Maintenance, Bethesda, MD, pp. 190–198. IEEE Computer Society Press, Los Alamitos (1998)

    Google Scholar 

  14. Gram, C.: A software engineering view of user interface design. Engineering for Human-Computer Interaction. In: Proceedings of the IFIP TC2/WG2.7 working conference on engi-neering for human-computer interaction, Yellowstone Park, USA, August 1995, pp. 293–304. Chapman & Hall, London (1996)

    Google Scholar 

  15. Hayes, J.H.: Building a Requirement Fault Taxonomy: Experiences from a NASA Verification and Validation Research Project. In: IEEE International Symposium on Software Reliability Engineering (ISSRE), Denver, CO (November 2003)

    Google Scholar 

  16. Hayes, J.H., Dekhtyar, A., Osbourne, J.: Improving Requirements Tracing via Infor-mation Retrieval. In: Proceedings of the International Conference on Requirements Engineering, Monterey, California (September 2003)

    Google Scholar 

  17. Hayes, J.H., Mohamed, N., Gao, T.: The Observe-Mine-Adopt Model: An Agile Way to Enhance Software Maintainability. Journal of Software Maintenance and Evolution: Research and Practice 15(5), 297–323 (2003)

    Article  Google Scholar 

  18. IBM Research, Center for Software Engineering, Details of ODC v5.11, http://www.research.ibm.com/softeng/ODC/DETODC.HTM

  19. IEEE Standard Classification for Software Anomalies, December 12, IEEE Std 1044.1-1995 (1995)

    Google Scholar 

  20. Lanubile, F., Shull, F, Basili, V.R..: Experimenting with Error Abstraction in Requirements Documents. In: Proceedings of the 5th Inernational. Symposium on Software Metrics, Bethesda, Maryland (1998)

    Google Scholar 

  21. Macaulay, L.: Human -computer interaction for software designers. International Thom-son Computer Press, London (1995)

    Google Scholar 

  22. Marick, B.: A survey of software fault surveys. A technical report UIUCDCS-R-90-1651, University of Illinois, pp. 2-23 (1990)

    Google Scholar 

  23. Mayhew, D.J.: Principles and guidelines in software user interface design. Prentice Hall, Englewood Cliffs (1992)

    Google Scholar 

  24. Mayrhauser, A., Ohlsson, M.C., Wohlin, C.: Deriving fault architecture from defect history. J. Softw. Maint. Res. Pract. 12, 287–304 (2000)

    Article  Google Scholar 

  25. Miller, L.A., Groundwater, E.H., Hayes, J., Mirsky, S.M.: Guidelines for the verification and validation of expert system software and conventional software. In: SAIC 1995, vol. 2, p. 100 (1995)

    Google Scholar 

  26. Mozilla organization website, http://mozilla.org/

  27. Munch, J., Rombach, H.D., Rus, I.: Creating an advanced software engineering laboratory by combining empirical studies with process simulation. In: Proceedings of the International Workshop on Software Process Simulation and Modeling (ProSim 2003), Portland, Oregon, USA, May 3-4 (2003)

    Google Scholar 

  28. Nikora, A., Munson, J.: Developing Fault Predictors for Evolving Software Systems. In: Proceedings of the Ninth International Software Metrics Symposium (METRICS 2003), Sydney, Australia (September 2003)

    Google Scholar 

  29. Offutt, J.: Investigations of the Software Testing Coupling Effect. ACM Transactions on Software Engineering Methodology 1(1), 3–18 (1992)

    Article  Google Scholar 

  30. Offutt, J., Hayes, J.H.: A Semantic Model of Program Faults. In: International Symposium on Software Testing and Analysis (ISSTA 1996), San Diego, CA (January 1996)

    Google Scholar 

  31. Ohlsson, M., Andrews, A., Wohlin, C.: Modelling fault-proneness statistically over a sequence of releases: a case study. Journal of Software Maintenance and Evolution: Research and Practice 13, 167–199 (2001)

    Article  MATH  Google Scholar 

  32. Ostrand, T., Weyuker, W.: The Distribution of Faults in a Large Industrial Software System. In: Proceedings of International Symposium on Software Testing and Analysis (ISSTA) 2002 and ACM SIGSOFT, vol. 27(4), pp. 55–64 (2002)

    Google Scholar 

  33. Perry, D.E., Stieg, C.S.: Software Faults in Evolving a Large, Real-Time System: a Case Study, AT&T Bell Laboratories. In: Proceedings of the 4th European Software Engineering Conference, Garmisch, Germany (September 1993)

    Google Scholar 

  34. Rombach, H.D., Basili, V., Selby, R.: Experimental Software Engineering Issues: Critical Assessment and Future Directions. LNCS. Springer, Heidelberg (1993)

    MATH  Google Scholar 

  35. Shneiderman, B.: Designing the user interface: strategies for effective human-computer interaction. Addison-Wesley, Reading (1992)

    Google Scholar 

  36. Sullivan, M., Chillarege, R.: Software defects and their impact on system availability- A study of field failures in operating systems. In: Digest 21st International Symposium on Fault-Tolerant Computing, Montreal, Canada (June 1991)

    Google Scholar 

  37. Warren-Smith, R.F.: Starlink project, Rutherford Appleton Laboratory, http://star-www.rl.ac.uk/star/docs/sgp42.htx/sgp42.html#stardoctoppage

  38. Wohlin, C., Andrews, A.: Analysing Primary and Lower Order Project Success Drivers. In: Proceedings of the Software Engineering and Knowledge Engineering (SEKE 2002), Isclina, Italy. CS Press (2002)

    Google Scholar 

  39. Yu, W.D., Barshefsky, A., Huang, S.T.: An empirical study of software faults preventable at a personal level in a very large software development environment. Bell Labs Technical Journal 2, 221–232 (1997)

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2005 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Hayes, J.H., Inies Raphael, C.M., Surisetty, V.K., Andrews, A. (2005). Fault Links: Exploring the Relationship Between Module and Fault Types. In: Dal Cin, M., Kaâniche, M., Pataricza, A. (eds) Dependable Computing - EDCC 5. EDCC 2005. Lecture Notes in Computer Science, vol 3463. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11408901_31

Download citation

  • DOI: https://doi.org/10.1007/11408901_31

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-25723-3

  • Online ISBN: 978-3-540-32019-7

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics