VSTTE 2012 Software Verification Competition


And the Winners Are...

posted Jan 28, 2012, 12:02 PM by Andrei Paskevich   [ updated Jan 28, 2012, 12:04 PM ]

Gold medal (600 points):
  • Team "acl2-dkms": Jared Davis, Matt Kaufmann, J Strother Moore, and Sol Swords with ACL2.
  • Team "KIV": Gidon Ernst, Gerhard Schellhorn, Kurt Stenzel, and Bogdan Tofan using KIV.
Silver medal (595 points):
  • Team "LeinoMueller": K. Rustan M. Leino and Peter Müller with Dafny.
  • Team "SRI": Sam Owre and Natarajan Shankar using PVS.
Bronze medal (590 points):
  • Team "eam": Ernie Cohen and Michał Moskal with VCC.
  • Team "JasonAndNadia": Jason Koenig and Nadia Polikarpova with Dafny.
Congratulations to the winners!

We have sent to all participants their scores and selected reviewers' comments by email.

Thank you for taking part and see you at the next Verified Software competition.

Competition is over

posted Nov 10, 2011, 7:01 AM by Andrei Paskevich

We thank you all for your participation and hope you enjoyed the competition.

If you have submitted a solution, you should have received an acknowledgment email from one of us. Otherwise, please resend it within an hour.

The winner will be notified by December 12. The results of the competition will be presented at VSTTE 2012 (Philadelphia, USA, January 28-29).

See you there!

Submission Instructions

posted Nov 8, 2011, 8:57 AM by Jean-Christophe Filliâtre

Submissions should be sent to vstte-2012-competition@lri.fr with subject "VSTTE 2012 Competition: your-team-name".  The submission email is limited to 5 Mb; if your submission exceeds this limit, please send us an URL to download it.  A team may send several submissions; only the latest will be evaluated.
 
A submission is a (possibly compressed) tarball that contains exactly one directory (named by the team, for instance). This directory should contain at least a text file named README, and one directory for each problem solved. Thus it must look like:

   team/ -+
          +- README
          +- problem1/
          +- problem2/
          +- problem3/
          +- problem4/
          +- problem5/
          +- other stuff...

The README file should contain the following information:
  • team members and contact information (email);
  • detailed description of the submitted solutions: properties that have been specified and/or proved, restrictions and/or generalizations, anything that may facilitate the review;
  • detailed instructions to replay the solutions, including the software to use, URLs to get it from, compilation commands, etc.
Several solutions can be submitted for the same problem (for instance, using different tools). They should be stored in separate subdirectories of problemI/. During evaluation, only the best-faring solution will be taken into account.

Competition Starts Now

posted Nov 8, 2011, 7:01 AM by Jean-Christophe Filliâtre

The competition starts now.

A PDF document describing the problems can be downloaded from
https://sites.google.com/site/vstte2012/compet/problems/

Have fun!
--
Jean-Christophe Filliâtre
Andrei Paskevich
Aaron Stump

Mailing List Created

posted Oct 25, 2011, 8:48 AM by Jean-Christophe Filliâtre   [ updated Oct 25, 2011, 9:01 AM ]

We created a mailing list for the Competition: vstte-2012-verification-competition@googlegroups.com

You can register either by visiting
or by sending an email to
(A Google account is not required.)

This mailing list is intended for announcements and discussions related to the competition.
Every announcement we make prior to or during the competition will be posted on this page as well.

Call For Participation

posted Sep 28, 2011, 12:40 PM by Andrei Paskevich   [ updated Oct 7, 2011, 6:21 AM ]

A software verification competition is organized on behalf of the VSTTE 2012 conference. The purposes of this competition are: to help promote approaches and tools, to provide new verification benchmarks, to stimulate further development of verification techniques, and to have fun.

The contest takes place during 48 hours, 8-10 November 2011, two months prior to the conference. Problems will be put on the website of the conference. Solutions must be sent by email to the competition organizers. Any programming language, specification language, and verification tool is allowed.

Problems

There will be several independent problems. Each problem is presented as a sequential algorithm, using English or pseudocode, and a list of properties to formally prove about it, also expressed in plain English and standard mathematical notation. Participants have liberty to implement the proposed algorithms in functional, imperative, object-oriented, or any other programming style.

Evaluation

Submissions are ranked according to the total sum of points they score. Each problem includes several sub-tasks, e.g. safety, termination, behavioral correctness, etc., and each sub-task is given a number of points. While evaluating the submissions, judges take into account the accuracy and thoroughness of solutions as well as their terseness and elegance. Clarity is preferred to brevity. A certain degree of subjectivity in judgement is inevitable and should be considered as part of the game.

Participants

Anybody interested can take part in the contest. Team work is allowed. Only teams up to 4 members are eligible for the first prize. Individual participants may belong to several teams. However, a given solution cannot appear in different submissions.

The technical requirements are as follows:
  • access to the web to download the problems (a PDF file);
  • access to the email to submit the solutions;
  • any software used in the solutions should be freely available for non-commercial use to the public. This does not exclude closed source programs such as Microsoft's Z3. Software must be usable on an x86 Linux or Windows machine. Participants are authorized to modify their tools during the competition.

Submission

A submission is a (possibly compressed) tarball that contains exactly one directory (named by the team, for instance). This directory should contain at least a text file named README, and one directory for each problem solved. Thus it must look like:

   team/ -+
          +- README
          +- problem1/
          +- problem2/
          +  ...
          +- problemN/
          +- other stuff...

The README file should contain the following information:
  • contact information (email);
  • detailed description of the submitted solutions: properties that have been specified and/or proved, restrictions and/or   generalizations, anything that may facilitate the review;
  • detailed instructions to replay the solutions, including the software to use, URLs to get it from, compilation commands, etc.

Several solutions can be submitted for the same problem (for instance, using different tools). They should be stored in separate subdirectories of problemI/. During evaluation, only the best faring solution will be taken into account.

Organizers

Schedule

  Tuesday 8 Nov 2011, 15:00 UTC — competition starts
  Thursday 10 Nov 2011, 15:00 UTC — competition stops

  Monday 12 Dec 2011 — the winner is notified
  28-29 Jan 2012 — results are announced at VSTTE 2012

Prize

The winner is awarded a talk slot at VSTTE 2012, to present any research of his/her choice of interest for the VSTTE community. In particular, a presentation of solutions to the competition problems and/or of the techniques and system used would be appreciated.

1-6 of 6