Skip to main content

Program Modeling for Fault Definition Based Static Analysis

  • Conference paper
  • First Online:
  • 711 Accesses

Part of the book series: Lecture Notes in Computer Science ((LNAI,volume 2070))

Abstract

Generating effective test data to show that a faulty structure could produce a failure poses many complexity problems. Code reviews are known as an effective method for detecting potential critical program structures. But detecting this structures in a code review takes a lot of effort and is error prone.

This paper presents a method to detect potential faulty structures by program modeling. Therefore we build a database containing informa- tions about classified faults. For analyzing the program we generate a first order predicate logic model implemented in horn clauses. We show how to detect the fault structures defined in the database and how to reduce the effort for the code review by slicing the relevant parts of the program.

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

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   109.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

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. O. Jack F. Belli. A test coverage notation for logic programming. Proceedings of the Sixth International Symposium on Software Reliability Engineering, pages 133–142, 1995.

    Google Scholar 

  2. John H. R. May Hong Zhu, Patrick A. V. Hall. Software unit test coverage and adequacy. ACM Computer Surveys, 29:366–427, December 1997.

    Article  Google Scholar 

  3. M. Weiser J. R. Lyle. Automateic program bug location by program slicing. IEEE Symposium on Computers and Applications, pages 877–883, 1987.

    Google Scholar 

  4. L. M. Ottenstein K. J. Ottenstein. The program dependence graph in a software developement environment. ACM Sigsoft/Sigplan Software Engineering Symposium on Practical Software Development Environments, 19(5):177–184, 1984.

    Article  Google Scholar 

  5. Mariam Kamkar. An overview and comparative classification of program slicing techniques. J. Systems Software, 31:197–214, 1995.

    Article  Google Scholar 

  6. D. Binkley S. Horwitz, T. Reps. Interprocedural slicing using dependence graphs. ACM Trans. Progr. Lang. Syst., 12:26–61, 1990.

    Article  Google Scholar 

  7. E. J. Weyuker S. Rapps. Selecting Software test data using data flow information. IEEE Transactions on Software Engineering, pages 367–375, 1985.

    Google Scholar 

  8. Frank Tip. A Survey of program slicing techniques. Journal of Programming Languages, 3:121–189, 1995.

    Google Scholar 

  9. M. Weiser. Program slicing. IEEE Transactions on Software Engineering, 10:352–357, 1984.

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2001 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Illgen, T. (2001). Program Modeling for Fault Definition Based Static Analysis. In: Monostori, L., Váncza, J., Ali, M. (eds) Engineering of Intelligent Systems. IEA/AIE 2001. Lecture Notes in Computer Science(), vol 2070. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-45517-5_100

Download citation

  • DOI: https://doi.org/10.1007/3-540-45517-5_100

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-42219-8

  • Online ISBN: 978-3-540-45517-2

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics