Course syllabus

Jump to today

Course-PM

TDA567 / DIT084 TDA567 / DIT084 Testing, debugging and verification lp2 HT24 (7.5 hp)

Course is offered by the department of Computer Science and Engineering

Contact details

Teacher

Yehia Abd Alrahman, Associate Professor in Computer Science 

Teaching Assistants

Student Representatives

Students are welcome to provide feedback on the course to the student representatives or any of the teachers. 

See this page for contacts Student Representatives 

Course Evaluation:

Mid-course meeting: we will have a meeting with the student representatives on 21/11. Please talk to your student representatives and give feedback.

Course purpose

The main objective of the course is to develop a good understanding of the techniques that are used to (1) discover errors in computer programs, (2) analyse them and (3) eventually isolate them. 

We will provide automatic and/or mathematically correct ways to ensure that a program really does what we expect it to do. 

Expectations: This is an entry course to testing, debugging, and verification. We will show how the different methods work together to ensure software reliability. We will not go deep in details in each topic, but rather provide the necessary components to work with them.

Schedule

TimeEdit

Course design

The course will have two lectures per week (Monday and Thursday), one lab session (Monday), and one exercise session (Thursday). Lab sessions will focus on the hand-in assignments: this is where you can get help with upcoming hand-ins, as well get clarification about feedback.  Exercise sessions will be closely linked to the lectures of the week. Here, students may solve given problems, discuss solutions and interact with teachers in a more informal manner. The first part of the exercise session is dedicated to students solving problems themselves or in small groups, with the later half dedicated to discussion of (possibly alternative) solutions. Please see TimeEdit to find out the rooms of the upcoming lectures, exercise sessions, and lab sessions.

Read more about the course structure in the respective pages:

This is your guide to navigating the course and we encourage you to visit these pages weekly for up to date information about the course.

Communication tools

  • Slack channel: Here
  • This Canvas room is the primary source of information about the course. All announcements will be made on Canvas.
  • The discussion forum is also hosted on Canvas. There you can ask questions about the course to the teachers and to other students. Sharing solutions to labs is forbidden, on Canvas or anywhere else.
  • We use the Fire system. to handle lab submissions. All feedback for the hand-in assignments will be provided there.

The course uses several software tools. A collection of documentation and online references to these tools can be found on the Tools page.

 

Examination form

The course is examined by a final individual written exam, 5.0 hec, and laboratories (practical hand-in assignments), 2.5 hec. The laboratories must be done in groups of 2-3 students. Instructions for labs will be posted during the course.

In case a practical hand-in assignment is not passed in the first attempt, the student is granted a second try, to be submitted within one week. Labs can only be assessed during the study period in which the course is given, i.e. must be completed before the January exam.

The exam and the labs can be passed independently. However, to pass the course both the labs and exam must have been passed. In case of a pass, the final course grade is determined by the final exam.

The final grade is given on the standard scale for the respective universities: U (fail), 3, 4, 5 for Chalmers students and Fail, Pass (G), Pass with Distinction (VG) for GU students.

Exam Dates

Confirm dates below here.

It is your responsibility to sign up for the exam and the re-exams (always check course calendar to know when sign up opens)

Regular exam: 14 Jan 2025 at 8:30am

Re-exam: 16 Apr 2025 at 02:00pm 

Exam paper format

The written exam will include basic learning outcomes questions and more advanced questions. All students must pass the basic questions to pass the exam and get the grade 3. Students who also pass the advanced questions will be able to get higher grades (4, 5). 

Sample exams & solutions: 

Course literature

There are no mandatory books that students must buy, nor is there any single textbook covering all the content of this course. However, as a complement to the course slides, the following books which are available as e-books from Chalmers Library might be helpful:

Learning objectives and syllabus

After completion of the course the student is expected to be able to

Knowledge and understanding:

  • Describe the possibilities and limitations of both informal and formal techniques for the discovery, analysis, and resolving of program errors,
  • Describe the concept of precise specifications of software units,
  • Discuss the principles of software verification.
Competence and skills:
  • Express precise specifications of software units,
  • Systematically discover inputs on which a program fails,
  • Locate, analyse, and fix the error which caused the failure,
  • Formally reason about simple programs for guaranteeing correctness.

Judgement and approach:

  • Judge the various error removal and prevention practices that one can encounter in a working context,
  • Contribute to the development and improvement of error removal and prevention techniques in a given context, 
  • Follow up on, and take advantage of, conceptual and technical developments in the area of testing, debugging, and verification that go beyond the exact techniques covered in the course.

Syllabus for DIT084 (GU)
Syllabus for TDA567 (Chalmers)

Course summary:

Date Details Due