Advertising Formal Methods and Organizing Their Teaching: Yes, but ...

  • Dino Mandrioli
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3294)


This position paper aims to address most of the “challenges” suggested by the conference’s CFP plus a few others. The style is deliberately informal and colloquial, occasionally even provocative: for every examined point some obvious agreement is given for granted but a few, more controversial, “counterpoints” are raised and hints are suggested for deeper discussion. At the end a constructive synthesis is attempted.


Software Engineering Formal Method Requirement Elicitation Engineering Curriculum Brute Force Algorithm 
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.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Easterbrook, S., Lutz, R., Covington, R., Kelly, J., Ampo, Y., Hamilton, D.: Experiences using lightweight formal methods for requirements modeling. IEEE Transactions on Software Engineering 24(1), 4–14 (1998)CrossRefGoogle Scholar
  2. 2.
    Saiedian, H., Bowen, J.P., Butler, R.W., Dill, D.L., Glass, R.L., Gries, D., Hall, A., Hinchey, M.G., Holloway, C.M., Jackson, D., Jones, C.B., Lutz, M.J., Parnas, D.L., Rushby, J., Wing, J., Zave, P.: An Invitation to Formal Methods. IEEE Computer 29(4), 16–30 (1996)Google Scholar
  3. 3.
    Hall, A.: Seven Myths of Formal Methods. IEEE Software 7(5), 11–19 (1990)CrossRefGoogle Scholar
  4. 4.
    Bowen, J., Hinchey, M.: Seven More Myths of Formal Methods. IEEE Software 12(4) (July 1995)Google Scholar
  5. 5.
    Bowen, J., Hinchey, M.: Ten Commandments of Formal Methods. IEEE Computer 28(4), 56–63 (1995)Google Scholar
  6. 6.
    Dijkstra, E.W.: On the cruelty of really teaching computing science. Communications of the ACM 32(12), 1398–1404 (1989)Google Scholar
  7. 7.
    Ciapessoni, E., Coen-Porisini, A., Crivelli, E., Mandrioli, D., Mirandola, P., Morzenti, A.: From formal models to formally-based methods: an industrial experience. ACM Transactions on Software Engineering and Methodologies 8(1), 79–113 (1999)CrossRefGoogle Scholar
  8. 8.
    Cigoli, S., Leblanc, P., Malaponti, S., Mandrioli, D., Mazzucchelli, M., Morzenti, A., Spoletini, P.: An Experiment in Applying UML2.0 to the Development of an Industrial Critical Application. In: Proceedings of the UML 2003 workshop on Critical Systems Development with UML, San Francisco, CA, October 21 (2003)Google Scholar
  9. 9.
    Parnas, D.L.: Software engineering programmes are not Computer science Programmes. CRL Report 361, McMaster University, Ontario (1998)Google Scholar
  10. 10.
    Parnas, D.L., Heninger, K.,, Kallander, K., Shore, J.: Software Requirements for the A-7E Aircraft., Naval Research Laboratory, Report no. 3876 (November 1978)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Dino Mandrioli
    • 1
  1. 1.Dipartimento di Elettronica e InformazionePolitecnico di MilanoMilanoItaly

Personalised recommendations