Second Meeting (2018/05/23)


  1. Welcome back! This time Alexandra and Joao could not make it, otherwise everyone was in, despite the challenging hours. We had this meeting exactly three months after the first one. Thanks Kenji and Dino in particular for agreeing to join this slot, although not among their initial favourites.

  2. The github repository of FM courses. We have thought on how to store our repository of courses. Dino and Bernd mentioned ResearchGate ( and Researchr (, but in the end we agreed to give GitHub a try. GitHub is primarily a tool for storing and sharing code, but other repositories can be formed, for instance all the papers published on a topic, check the Github repository for reaction systems: The papers are now stored as “Issues”, and Rustan made a good point in that maybe we should investigate whether the Wiki menu is more appropriate. Bernd thought the “Issues” might offer better measurability. We agreed to investigate this.

  3. Courses we found. Graeme sent FM courses he uncovered in Australia and New Zealand. It’s quite nice to see our first courses collected! In particular, New Zealand seems strong! Graeme made these lists by individually emailing people he knew from a forum called “Formal Methods Australia” and from other sources. The response was great, and people commented on how teaching in Formal Methods decreased and how they are quite interested in our actions, wanting to follow and contribute if possible.

  4. FMBoK. No new developments so far and we agreed we have to start from somewhere. Bernd proposed the ACM classification of terms ( also check this link We should also check the FMBoK efforts of Jonathan Bowen, Kenji Taguchi and others, sent as links and references in a previous email. I re-attach the file to this email for easier handling. We could also check the Software Engineering BoK for reference.

  5. Other advances on repositories. Not yet. In addition to what we agreed to store in repos last time though (case studies, simpler and more complex and exam questions), Graeme pointed out that resources on how to teach formal methods are quite valuable as well. A first paper to check on this topic was “(In)formal methods: the lost art” by Carroll Morgan, 2016, link here:

  author = {Carroll Morgan},
  title = {(In-)Formal Methods: The Lost Art - {A} Users' Manual},
  booktitle = {Engineering Trustworthy Software Systems - First International School,
               {SETSS} 2014, Chongqing, China, September 8-13, 2014. Tutorial Lectures},
  pages = {1--79},
  year = {2014},
  crossref = {DBLP:conf/setss/2014},
  url = {},
  doi = {10.1007/978-3-319-29628-9_1},
  timestamp = {Wed, 17 May 2017 14:24:31 +0200},
  biburl = {},
  bibsource = {dblp computer science bibliography,}

There is/was? also a course:

  1. Some common doc storage for us. We agreed on GoogleDocs, at least for the time being.

  2. Other issues. The issue of taking advantage of the Formal Methods community arose and we discussed how we can obtain info on FM courses from people we will anyway meet at FM conference in Oxford, at Formalise in Götenborg, Sweden, at ABZ in Southampton, etc. We agreed that maybe we ask the chairs to inform participants of our committee and to create some handouts for people to fill in wrt FM courses they know about. Rustan made a good point that it is interesting to see how FM teaching evolves over time, for instance to also ask questions like “what tool do you use to teach model checking”.

  3. Next steps. This is how we continue.

  • Luigia creates a repository in github and adds the courses sent by Graeme there. We then think whether we are happy with this storing mechanism or not.
  • We all check the ACM classification and the previous work on FMBoK and come up with proposals on how to revive this initiative.
  • Luigia copies all our materials to GoogleDocs and so we’ll have a sharing mechanism
  • We make a format for what to ask people about (in emails or in handouts at conferences) wrt FM courses
  • We meet again in September, Luigia sends Doodle poll at the end of August…
Formal Methods Teaching Committee

The aim of the FME Teaching Committee is to support a worldwide improvement in learning formal methods, mainly by teaching but also via self-learning.