Abstract
Formal methods can help to increase the correctness and trustworthiness of the software developed. However, they do not solve all the problems of software development. This paper analyses some limitations of formal methods.
Similar content being viewed by others
References
Brodbeck, F. C., Sonnentag, S., Heinbokel, T., Stolte, W. and Frese, M.: Tätigkeitsschwerpunkte und Qualifikationsanforderungen in der Software-Entwicklung: Eine empirische Untersuchung.Softwaretechnik-Trends, pages 31–40, May 1993.
Courtiat, J.-P., Dembinski, P., Holzmann, G. J., Logrippo, L., Rudin, H. and Zave, P.: Formal methods after 15 years: Status and trends. A paper based on contributions of the panelists at the FORmal TEchnique '95 Conference, Montreal, October 1995.Computer Networks and ISDN Systems, 28:1845–1855, 1996.
Coleman, D. and Hughes, J. W.: The clean termination of Pascal programs.Acta Informatica, 11:195–210, 1979.
Coy, W., Nake, F., Pflüger, J.-M., Rolf, A., Seetzen, J., Siefkes, D. and Stransfeld, R. Editors.Sichtweisen der Informatik. Vieweg, 1992.
Fairley, R. E.:Software Engineering Concepts. McGraw-Hill, 1985.
Fetzer, J. H.: Program verification: the very idea.Communications of the ACM, 31(9): 1048-l063, September 1988.
Fitzgerald, J. S., Larsen, P. G., Brookes, T. and Green, M.: Developing a security-critical system using formal and conventional methods. In[HiB95a], chapter 14, pages 333–356. 1995.
Hall, A.: Seven myths of formal methods.IEEE Software, pages 11–19, September 1990.
Hinchey, M. G. and Bowen, J. P.:Applications of Formal Methods. Prentice Hall, 1995.
Hinchey, M. G. and Bowen, J. P.: Applications of formal methods FAQ. In[HiB95a], chapter 1, pages 1–15. 1995.
Hörcher, H.-M. and Peleska, J.: Using formal specifications to support software testing.Software Quality Journal, 4:309–327, 1995.
Humphrey, W. S.: Characterizing the software process: A maturity framework.IEEE Software, 5(2):73–79, March 1988.
ISO 9000 Part 3. Quality management and quality assurance standards—Guidelines for the application of ISO 9001 to the development, supply and maintenance of software, 1991.
Jones, C. B., Jones, K. D., Lindsay, P. A. and Moore, R. C:mural — A Formal Development Support System. Springer-Verlag, 1991. With contributions from J. Bicarregui, M. Elvang-Gøransson, R. Fields, R. Kneuper, B. Ritchie, A.C. Wills.
Jones, C. B.:Systematic Software Development Using VDM. Prentice-Hall Int., 2nd edition, 1990.
Kneuper, R.: Symbolic execution: a semantic approach.Science of Computer Programming, 16:207–249, 1991.
Goguen, L. and J. A.: Formal methods: Promises and problems.IEEE Software, pages 73–85, January 1997.
Gorm, L. P., Plat, N. and Toetenel, H.: A formal semantics of data flow diagrams.Formal Aspects of Computing, 6(6):586–606, 1994.
Marshall, L. S.: Formally describing interactive systems. In Cliff B. Jones and Roger CF. Shaw, editors,Case Studies in Systematic Software Development, pages 293–336. Prentice Hall Int., 1990.
Millo, R. A. De, Lipton, R. J. and Perlis, A. J.: Social processes and proofs of theorems and programs.Communications of the ACM, 22(5), 1979.
Naur, P.: Formalization in program development.BIT, 22:437–453, 1982.
Partsch, H. and Möller, B.: Konstruktion korrekter Programme durch Transformation.Informatik-Spektrum, 10:309–323, 1987.
Swartout, W. R.:Gist English Generator. InProc. of AAAI-82, 1982.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Kneuper, R. Limits of formal methods. Formal Aspects of Computing 9, 379–394 (1997). https://doi.org/10.1007/BF01211297
Received:
Accepted:
Issue Date:
DOI: https://doi.org/10.1007/BF01211297