This course provides a hands-on introduction to formal methods for software engineering. The purpose of formal methods is to enable the construction of highly reliable software. Their foundation is the precise specification of run-time properties that a software system is expected to satisfy. Formal methods are concerned with specifications that are precise for being stated in languages endowed with a formal syntax, semantics, and theory. Formality helps the specification process in at least two ways:
As we will see, formal specification techniques allow for the construction of highly automated verification tools that help software developers analyze specifications and corresponding code, looking for errors in requirements, models, designs, and implementations.
In this course, we will study a collection of techniques for formal software development, spanning the whole development process: from high-level semantic modeling to coding and debugging. The study will not be done in the abstract, however, but through the use of actual tools supporting these techniques.
Students should be prepared to put in considerable time and effort into reading to become familiar with the course's topics, and into homework and exercises to gain experience with the techniques seen in class.
Tue and Thu, 12:30am - 1:45pm, 118 MLH
Office hours: Mon 2:00pm-3:30pm, Wed 11:30am-12:30pm, and by appointment.
Office hours: Tue, Thu 2:00pm-3:30pm, and by appointment.
CS:2810 or ECE:3330, or equivalent.
Most of the information about the class, including handouts and assignments, will be available from the class web site:
We will also use Piazza, a class discussion service, for announcements, questions and discussions, and ICON for homework submissions and grade posting. Lectures will be recorded and recording will be available to registered students on UICapture.
Students are expected to check both the class web site and the Piazza discussion board on a regular basis (at least every other day) for announcements regarding the course.
There is no required textbook for this course. All reading materials will be made available through the course web site. They will include several papers on formal software specification and verification, a number of papers on how to use the specification/verification tools adopted in the course, and various class notes and handouts.
The formalisms used in this class are ultimately based on propositional logic and on first-order logic (predicate calculus). Links to background reading material on that will also be available on the course website.
You may need to use your account on the CS lab machines which will have a working installation of software tools we will use in the course. Instructions on how to access those machines, on-site or remotely, and use the installed software will be provided on the course website.
Although you are welcome to use your own computer for course work, you are responsible for installing any necessary software. We regret that will not be able to provide assistance for any problems with your own installation.
A few exercises will be given during the course of the semester, covering the material from the readings and the lectures. These exercises are required but will not be collected or graded.
For each main topic there will be two graded homework assignments: an introductory assignment and a graded mini-project, both to be done in teams of 2 people. Every team member will be expected to be involved in all aspects of an assignment (no dividing up the work). The whole team is responsible for the work submitted. While the work is shared each students will received an individualized grade. Team members will be asked to submit an evaluation of how well they and their teammates performed as team members. Each evaluation is confidential and will be be incorporated into the calculation of the individual grade.
Each student is responsible for contacting other students and form a team. The discussion forum on Piazza can be unison to establish initial contacts, and possibly for later discussions. It is okay to form different teams for each assignment/project. Teams of 1 are accepted but not encouraged. In particular, no reduction of work will be granted to them.
There will be one midterm exam and one final exam. The midterm will be held during class time. The final exam will be held as per university schedule.
The weighting of items in grade determination will be the following:
The following cutoffs will be used to determine letter grades. In the ranges below, x stands for your total score at the end of the semester. Final scores near a cutoff will be individually considered for the next higher grade. Plus(+) and minus(-) grades will also be given; their cutoffs will be determined at the end of the semester.
|88 <= x < 100||A|
|75 <= x < 88||
|60 <= x < 75||C|
|50 <= x < 60||D|
|00 <= x < 50||F|
Grades are not curved in this course. It is theoretically possible for everyone in the class to get an A (or an F). Your final grade depends only on your own final score and not on that of others.
The University of Iowa expects students to set high academic standards for themselves and work hard towards achieving them. You can achieve true academic excellence only through dedicated work. An average workload of 6 hours a week besides class attendance should be considered the norm for this course. More effort might be needed depending on your background, predisposition and academic ambition.
Academic dishonesty will not be tolerated. In particular, under no circumstances should you pass off someone else's work as your own. This also applies to code or other material that you might find on the Internet.
Sharing solutions of graded homework (assignments and project) between teams or copying someone else's work,
including posted solutions from previous editions of the course, is not allowed.
Doing that will result in a zero on the assignment
and a report to the CS Department's chair and the College.
You are allowed and encouraged to discuss with students in other teams concepts and ideas that relate to the class and the homework assignments. However, it is important to ensure that these discussions do not lead to the actual exchange of written material.
Team members are collectively responsible for the work submitted by their team. So make sure you are fully aware of what is being submitted if you are not the submitter.
Exams: The midterm and final exams are individual tests. Each student must complete them without any help from others. Exam answers showing strong similarities and/or duplication will receive a fail grade and the students involved will be reported to the Department and the College.
If you are unclear about what constitutes academic dishonesty it is your responsibility to contact the instructors or consult the CLAS policy (online version). Be aware that repeated academic dishonesty offenses lead to suspension or expulsion from the University.
Communicating with the Instructors:
We welcome questions related to the course.
Students are strongly encouraged to post their class-related questions on Piazza (publicly or privately, as appropriate) rather than emailing questions to the teaching staff.
Questions sent by email will receive lower priority.
We will try to answer all questions, posted or emailed,
by the end of the following day.
We will make any course-related announcements on Piazza and will occasionally send direct email notifications to all students in the class. As a reminder, students are responsible for all official correspondence sent to your Hawkmail address (see General CLAS Policies on electronic Communication below).
Assigned Readings: Students are expected to study all the material assigned as required readings, even if that material is not explicitly discussed in class or in the homework.
Additional Readings and Discussions: Students are encouraged to go over any specifically suggested readings and consult any relevant materials beyond those provided on the course's web site. They are also encouraged to discuss the course topics with their classmates. It is a genuinely helpful learning activity having to formulate one's own thoughts about the material well enough to express them to others.
Attendance: Students are expected to attend all lectures or, for long distance students, timely watch all recorded lectures. Their knowledge and therefore their grade depends on this. Students are responsible for all announcements made in class and material covered there regardless of whether they attended/watched the lecture or not.
Extra Credit: No extra-credit assignments or tests will be given on an individual basis, although they maybe given to the whole class.
Make-up Exams: Make-up exams will be offered only if there is a serious, documented reason for not being able to take a scheduled exam, and if the request is made at least a week before the exam.
Regrading: Students thinking a graded assignment or test has been misgraded and deserves a regrading are invited to let the instructor know. The instructor welcomes and will give full consideration to all well motivated regrading requests.