Program Verification (Lecture)
Course Type 
Lecture 

Instructors  Matthias Heizmann, Dominik Klumpp, Andreas Podelski 
Lecture 
Lecture recordings will be uploaded twice a week. We will have interactive sessions for questions and discussions about lecture contents and exercises. 
Exercise 
Closely integrated to the lecture 
Language  English 
Exam 
There will be an exam. 
Course Catalog 
Program Verification (Lecture) Program Verification (Exercise) 
Motivation
Did you ever write compute program that did not work correctly? Perhaps surprisingly for outsiders the response of every programmer will be "yes" because especially during the development of software, faulty programs are rather the rule than the exception.
How do we deal with the problem that we often have errors in our code? There are two typical approaches:
 We can write tests. We check for a given input if the program produces the expected output
 We can analyze our code very carefully.
Did you ever have a bug in you code even if you analyzed it very carefully and did some tests? Even to this question, the answer "yes" is no surprise, since tests cannot capture all behaviors of the program and an analysis of code is tedious and errorprone. From our everyday experience with electronic devices, we know that not only computer science students but also professional programmers regularly fail to write correct code. The fact that there is a long list of faulty software systems that were expensive or safetycritical hints that the problem is not just the sloppiness of programmers but that there is a need for new approaches that improve the reliability of software.
In this lecture we will learn an approach that is called software verification. First, we will formally state properties like e.g., if the program reaches line 42 then the variable x is positive, or if the input is different from 23 then there will be no overflow. We will then learn how to write mathematical proofs that show that a given program satisfies a given property.
Unfortunately, it can be tedious and difficult to find such a mathematical proof and humans also tend to make mistakes while giving mathematical proofs. Hence, we would like to let computers do this task.
In this lecture we will see algorithms that enable computers to find bugs in computer programs, or to find proofs that show the absence of bugs.
Contents
Although we will use tools this is a rather theoretical lecture in which we will learn the basic concepts of program verification.
We will often reduce problems to the satisfiability problem of logical formulas. (So if you do not like mathematical logic, you probably do not want to take this lecture.) E.g, a satisfying assignment for the following formula will show us how the assert statement in the depicted program can be violated.
x_0 >= 0 /\ y_0 >=0 /\ x_0<=4294967296 /\ y_0<=4294967296 /\ x_0 + y_0 <= 42 /\ y_0 >= 100 /\ x_1 = (2*x_0y_0)%4294967296 /\ x+y < 100

void foo(unsigned int x, unsigned int y) { while (x+y <=42) { if (y >= 100) { x = 2 * x  y; //@ assert (x+y >= 100); } y++ } } 

In order to get familiar with logical reasoning, the course will start with an introduction to propositional logic and firstorder logic. We will then formally introduce the Hoare calculus which will allow us to state the correctness of a program and to give a mathematical proof that the program is correct.
Throughout this lecture, we will use tool like the Z3 SMT solver or the Ultimate Automizer software verifier in order to see the effect of our algorithms on practical examples. E.g., if we want to find out if the following C program is correct, we can ask Ultimate Automizer.

int main() { unsigned char pos = getInitialPosition(); int arr[256]; while(1) { arr[pos] = getNextValue(); arr[pos + 1] = getNextValue(); pos += 2; } return 0; } 

ELearning
The course will be organized online in the Ilias system.The main course material are slides, exercises, and videos. Additionally we will have interactive sessions via BigBlueButton, which is itegrated in Ilias. The interactive sessions are NOT recorded.
The slide set consists of three kinds of slides. First, there are slides that I would show in a presentation. Some of these slides are accompanied by additional slides (the slides with violet text) that contain the information that I would say while giving the presentation. Furthermore there are slides that look like titlepages, have blue background and tell you the range of slides that is discussed in the next virtual classroom.
The slides are very similar to a lecture script and the idea is that you read the slides before the next interactive sessions. Your efforts to understand the slides will be supported by exercises that you hand in before the next interactive sessions. In the interactive sessions we will go very quickly through the slides and discuss only your questions. Furthermore, we will discuss your solutions for the exercises. For some topics, e.g., presentation of tools, carrying out difficult algorithms, motivating a new concept, we will record videos.
We are very happy to improve the course material. If you have questions and you think something should be explained in more detail then please let us know.
Slides
The lecture slides are the main course material. Starting from Section 2 the slides are annotated with additional information and can be seen as a kind of lecture script.
The slides will be updated frequently. We will not only append new content but depending on the questions in interactive sessions we will also insert slides with additional information
The slides are very similar to the slides of last year's course.
Videos
Video03 The NPL Proof SystemExercises
 An exercise sheet will be uploaded every Wednesday evening and should be submitted (in Ilias) by the following Monday.
 Furthermore, we will have short exercise sheets on Monday in preparation for the next lecture, to be submitted by Wednesday.
Submission deadline 
Exercise sheet 

Wednesday 29th April 16:00 
Exercise sheet 00 (see Ilias) 
Monday 18th May 10:00 

Wednesday 20th May 16:00 

Monday 25th May 10:00 

Wednesday 27th May 16:00 

Wednesday 3rd June 10:00  
Monday 8th June 10:00  
Wednesday 10th June 16:00  
Monday 15th June 10:00  
Wednesday 17th June 16:00  
Monday 22nd June 10:00  
Wednesday 24th June 16:00  
Monday 29th June 10:00  
Wednesday 1st July 16:00  
Monday 6th July 10:00  
Wednesday 8th July 16:00  
Monday 13th July 
Exam
There will be an exam during the examination period. Prerequisite for admission to the exam is an active participation in the exercises. A sufficient criterion for an active participation in the exercises is that you achieved 50% of the points that can be obtained for exercise sheets and presented an exercise in an interactive session.
Literature
 Almeida, J.B., Frade, M.J., Pinto, J.S., Melo de Sousa, S., Rigorous Software Development  An Introduction to Program Verification, Springer 2011, ISBN 9780857290175
 Matthias Heizmann, Jochen Hoenicke, Andreas Podelski: Software Model Checking for People Who Love Automata. CAV 2013

Traces, interpolants, and automata : Ultimate Automizer’s approach to software verification
Talk given at the EPIT Spring School 2018