- 4 April 2016: Prize winners announced
- 2 April 2016: competition day. 14 teams participating, using 9 different tools: Dafny (4 x), Why3 (2 x), KIV, KeY, CIVL, VerCors, Viper, mCRL2, and VeriFast. There are 4 student-only teams, and also 4 non-developers teams.
- 9 March 2016: program available, Dafny tutorial and challenge open to all ETAPS participants
- 22 February 2016: travel grants available
- 13 November: 2015 a call for problems is published. Submission deadline is December 4th, 2015.
- 22 October 2015: website online
- to bring together those interested in formal verification, and to provide an engaging, hands-on, and fun opportunity for discussion
- to evaluate the usability of logic-based program verification tools in a controlled experiment that could be easily repeated by others.
|Saturday April 2
|9 :00 – 9:45||Dafny tutorial - Rustan Leino, MSR research (open to everybody)|
|9:45 – 10:30||Dafny challenge (open to everybody)|
|10:30 – 11:00||coffee break|
|Start of the competition|
|11:00 – 12:30||challenge 1 (90 minutes)|
|12:30 – 14:00
|14:00 – 15:30||challenge 2 (90 minutes)|
|15:30 – 16:00||coffee break|
|16:00 – 17:30||challenge 3 (90 minutes)|
|17:30 – 19:00||participants that are leaving already discuss their answers with the judges|
|19:30||dinner for all competition participants|
|Sunday April 3|
||informal discussions among participants and judging|
|Monday April 4|
|during reception||award ceremony|
The competition will start with a tutorial on Dafny by Rustan Leino, MSR Research. Dafny has been especially popular in previous verification competitions. The tutorial will explain the basic ideas of program verification in Dafny, which can then immediately be tried out on a small challenge problem.
The Dafny tutorial is open to all ETAPS participants.
The competition has funds for a limited number of travel grants. A grant covers the incurred travel and accommodation costs up to a certain amount. The amount is EUR 250 for those coming from Europe and EUR 500 for those coming from outside Europe.
To apply for a travel grant, send an email to email@example.com. The application should include:
- your name
- your affiliation
- the academic degree you are seeking resp. your career stage
- the verification system(s) you plan to use at the competition
- the planned composition of your team
- a short letter of motivation explaining your involvement with formal verification so far
- if you are a student or PhD student, please have your supervisor send a brief letter of support by email to the same address.
Evaluation criteria are qualifications (for the applicant's career level), need (please explain briefly in your application), and diversity (technical, geographical, etc.).
- best team
- best student team
- best challenge submitted
- distinguished user-assistance tool feature
- student teams (this includes PhD students)
- non-developer teams using a tool someone else developed
- several teams using the same tool
- a problem should contain an informal statement of the algorithm to be implemented (optionally with complete or partial pseudocode) and the requirement(s) to be verified
- a problem should be suitable for a 60-90 minute time slot
- submission of reference solutions is strongly encouraged
- problems with an inherent language- or tool-specific bias should be clearly identified as such
- problems that contain several subproblems or other means of difficulty scaling are especially welcome
- the organizers reserve the right (but no obligation) to use the problems in the competition, either as submitted or with modifications
- submissions from (potential) competition participants are allowed