Admission requirements
Recommended prior knowledge
Students are assumed to have knowledge of computer science at a BSc level (logics, algorithmics and data structures) and basic programming skills (in any programming language). A BSc level course on verification or testing is recommended background knowledge (e.g., Programmeren & Correctheid, Theory of Concurrency).
Description
Digital systems have become so ubiquitous, that many of our daily activities depend on them. A glitch in the software or hardware of a digital system can cause us to miss an appointment or have to retype a text. But in the worst case, our lives can depend on the correctness of the system. Examples of such mission-critical systems are: traffic lights, automated breaking systems in cars, autonomous vehicles, autopilots, and guidence systems in rockets. Therefore, various methods have been developed for verifying the correctness of software and hardware. These methods go beyond mere testing by proving not only the presence but also the absence of bugs.
This course mainly focuses on a software / hardware verification technique called model checking. Model Checking is a Turing-award winning approach for proving program correctness fully automatically. A model checker is a tool that takes another program as input together with a specification of its intended behavior. The model checker then proves correctness by exhaustively exploring the program’s behavior, i.e., its state space, and ‘checking’ that it conforms to the intended behavior, as defined in the specification.
The power of model checking crucially depends on the ability to handle large state spaces. Even for a finite-state program (without recursion and memory allocation) the state space is exponential in both the program data (the variables in the program) and the amount of parallelism (the number of threads / processes in the program). Nevertheless, extremely large state spaces can be handled by the state-of-the-art technologies based on compression, partial-order reduction, symbolic data structures and parallelism. In the course, you will study both the theory and practice of these technologies.
The course follows the textbook Principles of Model Checking by Christel Baier and Joost-Pieter Katoen for the formal underpinning of model checking, i.e.:
Formalisms for speciying software and hardware systems
Temporal logics for specifying the behavior of reactive systems
Model-theoretic methods to verify that a system description adheres to its specification
Furthermore, the course puts an emphasis on algorithms and data structures for handling large state spaces. For this purpose, additional reading materials and lab exercises are provided. These techniques include:
Symbolic model checking with Binary Decision Diagrams (BDDs)
Symbolic model checking with SAT/SMT (Bounded Model Checking and Property Directed Reachability)
Enumerative model checking with state compression
State space reduction techniques that exploit parallel program semantics, such as, Partial Order Reduction
Parallel model checking algorithms
Course objectives
The first objective is to introduce the student to the formal underpinnings of model checking. The second objective is to learn to implement the different techniques (algorithms, data structures and symbolic approaches) developed for model checking large systems.
In this second objective, the student will implement their own model checker from scrath, using an incremental approach. Sub-objectives include:
Implementing program and its scheduling semantics in a next-state function
Implementing relevant (search) algorithms, data structures and reduction techniques
Encoding program semantics in BDDs and SAT/SMT
Timetable
The most recent timetable can be found at the Computer Science (MSc) student website.
You will find the timetables for all courses and degree programmes of Leiden University in the tool MyTimetable (login). Any teaching activities that you have sucessfully registered for in MyStudyMap will automatically be displayed in MyTimeTable. Any timetables that you add manually, will be saved and automatically displayed the next time you sign in.
MyTimetable allows you to integrate your timetable with your calendar apps such as Outlook, Google Calendar, Apple Calendar and other calendar apps on your smartphone. Any timetable changes will be automatically synced with your calendar. If you wish, you can also receive an email notification of the change. You can turn notifications on in ‘Settings’ (after login).
For more information, watch the video or go the the 'help-page' in MyTimetable. Please note: Joint Degree students Leiden/Delft have to merge their two different timetables into one. This video explains how to do this.
Mode of instruction
The theoretical part consists of a series of lectures about advanced model checking methods.
In the practical part of the course, the student will have the opportunity to implement and extend the techniques discussed in a model checking framework. This framework hides all uninteresting details of a model checker, so the student can focus on core algorithms and data structures.
The student will receive a series of home work exercises that can be completed alone or in groups of two.
Course load
Total hours of study: 168 hrs. (= 6 EC)
Lectures: 30:00 hrs.
Labs: 40:00 hrs.
Examination: 4:00 hrs.
Self-study: 94:00 hrs.
Assessment method
One exam (75%)
Practical exercises (25%)
The teacher will inform the students how the inspection of and follow-up discussion of the exams will take place.
Reading list
Baier, C., & Katoen, J. P. (2008). Principles of model checking. MIT press.
Additional materials will be distributed during the course.
Registration
Every student has to register for courses with the enrollment tool MyStudyMap. There are two registration periods per year: registration for the fall semester opens in July and registration for the spring semester opens in December. Please see this page for more information.
Please note that it is compulsory to both preregister and confirm your participation for every exam and retake. Not being registered for a course means that you are not allowed to participate in the final exam of the course. Confirming your exam participation is possible until ten days before the exam.
Extensive FAQ's on MyStudymap can be found here.
Contact
Lecturer: dr. Alfons Laarman.
Remarks
The course is open to first- and second-year master students of all programmes of Mathematics and Computer Science.