Advertisement

Ten Commandments of Formal Methods… Ten Years On

  • Jonathan P. Bowen
  • Mike Hinchey

Abstract

How have the formal methods commandments fared over the past decade? Are they still valid in the current industrial setting, and have attitudes toward formal methods improved? The authors revisit their ten maxims to answer these questions.

Keywords

Formal Method Software Product Line Literate Programming Graphical Notation Software Engineering Community 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Notes

Acknowledgements

We are grateful to our many colleagues and friends who provided us with valuable feedback and reactions to our original article. We also acknowledge the contributions of the formal methods community as a whole and thank them for providing us with material on which to base the original commandments. In particular, we thank David Atkinson, Jin Son Dong, Cliff Jones, Tiziana Margaria, Jim Rash, Chris Rouff, Roy Sterritt, and Bernhard Steffen, for their input.

Special thanks go to Tiziana Margaria and Mieke Massink, co-chairs of FMICS 2005, and George Eleftherakis, chair of SEEFM 2005, for inviting earlier conference presentations of this material, in the former case rather aptly to coincide with the tenth anniversary of FMICS.

References

  1. 1.
    Bowen, J.P., Hinchey, M.G.: Seven more myths of formal methods. IEEE Softw. 12(4), 34–41 (1995) CrossRefGoogle Scholar
  2. 2.
    Bowen, J.P., Hinchey, M.G.: Ten commandments of formal methods. IEEE Comput. 28(4), 56–63 (1995) CrossRefGoogle Scholar
  3. 3.
    Bowen, J.P., Hinchey, M.G.: Ten commandments revisited: a ten-year perspective on the industrial application of formal methods. In: 10th International Workshop on Formal Methods for Industrial Critical Systems (FMICS ’05), pp. 8–16. ACM, New York (2005) CrossRefGoogle Scholar
  4. 4.
    Hall, J.A.: Seven myths of formal methods. IEEE Softw. 7(5), 11–19 (1990) CrossRefGoogle Scholar
  5. 5.
    Hinchey, M.G., Rash, J.L., Rouff, C.A.: Requirements to design to code: towards a fully formal approach to automatic code generation. Technical report NASA Technical Monograph TM-2005-212774, NASA Goddard Space Flight Center (2005) Google Scholar
  6. 6.
    Hinchey, M.G.: Confessions of a formal methodist. In: Lindsay, P. (ed.) Seventh Australian Workshop Conference on Safety Critical Systems and Software 2002, vol. 15, Adelaide, Australia. Conferences in Research and Practice in Information Technology Series, vol. 139, pp. 17–20. Australian Computer Society, Darlinghurst (2002) Google Scholar
  7. 7.
    Hinchey, M.G., Bowen, J.P. (eds.): Applications of Formal Methods. Prentice Hall, Upper Saddle River (1995) MATHGoogle Scholar
  8. 8.
    Hinchey, M.G., Bowen, J.P. (eds.): Industrial-Strength Formal Methods in Practice. FACIT Series. Springer, Berlin (1999) Google Scholar
  9. 9.
    Lau, K.-K., Banach, R. (eds.): Formal Methods and Software Engineering, Proceedings 7th International Conference on Formal Engineering Methods, ICFEM 2005, Manchester, UK, November 1–4, 2005. Lecture Notes in Computer Science, vol. 3785. Springer, Berlin (2005) Google Scholar
  10. 10.
    MacKenzie, D.: Mechanizing Proof: Computing, Risk, and Trust. MIT Press, Cambridge (2001) MATHGoogle Scholar
  11. 11.
    Patterson, D.A., Brown, A., Broadwell, P., Candea, G., Chen, M., Cutler, J., Enriquez, P., Fox, A., Kiciman, E., Merzbacher, M., Oppenheimer, D., Sastry, N., Tetzlaff, W., Traupman, J., Treuhaft., N.: Recovery-oriented computing (ROC): motivation, definition, techniques, and case studies. Technical report Computer Science Technical Report UCB//CSD-02-1175, March 15, 2002, UC Berkeley (2002) Google Scholar
  12. 12.
    Power, D., Meyer, B., Grimes, J., Potel, M., Vetter, R., Laplante, P., Pree, W., Pomberger, G., Hill, M.D., Larus, J.R., Wood, D.A., El-Rewini, H., Weide, B.W.: Where is software headed? A virtual roundtable. Computer 28(8), 20–32 (1995) CrossRefGoogle Scholar
  13. 13.
    Research Triangle Institute: The Economic Impacts of Inadequate Infrastructure for Software Testing. Ed. Dr. Gregory Tassey. RTI Project No. 7007.011. National Institute of Standards and Technology, Washington, DC, May 2002 Google Scholar
  14. 14.
    Romijn, J., Smith, G., van de Pol, J. (eds.): Integrated Formal Methods, Proceedings 5th International Conference, IFM 2005, Eindhoven, The Netherlands, November 29–December 2, 2005. Lecture Notes in Computer Science, vol. 3771. Springer, Berlin (2005) Google Scholar
  15. 15.
    Ross, P.E.: The exterminators. IEEE Spectr. 42(9), 36–41 (2005) CrossRefGoogle Scholar
  16. 16.
    Sharpe, R.: Formal methods start to add up again. Computing (2004). 08 Jan 2004. Available online: http://www.computing.co.uk/ctg/feature/1836071/formal-methods-start-add

Copyright information

© Springer-Verlag London Limited 2012

Authors and Affiliations

  1. 1.Museophile LimitedLondonUK
  2. 2.Lero—the Irish Software Engineering Research CentreUniversity of LimerickLimerickIreland

Personalised recommendations