Implementation of Heuristic Algorithms for Board Games

Implementation of Heuristic Algorithms for Board Games

Practical Software Course, Summer Semester 2016


  • 13.01 – Page up

Plenary meetings

Date Time Location
26.04.2016 10:15 – 11:45 9U10 (E3)
10.05.2016 10:15 – 11:45 9U10 (E3)
24.05.2016 10:15 – 11:45 9U10 (E3)
07.06.2016 10:15 – 11:45 9U10 (E3)
21.06.2016 10:15 – 11:45 9U10 (E3)
05.07.2016 10:15 – 11:45 9U10 (E3)
19.07.2016 10:15 – 11:45 9U10 (E3)

Group meetings

Location: The group meetings are held in our seminar room at I2, building AS55 E1. It is located on the 3rd floor (2.OG), 2nd door on the left of our hallway.

Group Day Time
1 Thursday 14:15
2 Thursday 14:00
3 Wednesday 11:15
4 Wednesday 11:30
5 Thursday 14:30
6 Thursday 15:00
7 Wednesday 11:45
8 Thursday 14:45

Discussion Group

Use the mailinglist swp-i2-2016-pm AT for general and technical questions and discussions among students. Students are urged to answer other student’s questions.

Topics and Goals

The aim of the course is the implementation of a strong computer player for an extended version of Reversi. At the end of the course, a competition will be held between the developed computer players and a ranking is set up. The top of the ranking is the winner of the competition, and additional points to the final grade will be awarded to the winner.
During the course, techniques and concepts for creating stronger computer players are introduced incrementally which are expected to be studied and understood by the student. The course covers the following topics:

  • Client network socket programming
  • Mini-max and paranoid search
  • Alpha-beta pruning
  • Iterative deepening
  • Move sorting
  • Aspiration windows
  • Game state rating heuristics
  • Empirical algorithmic efficiency analysis
  • Performance and memory profiling
  • Technical writing and reporting

The current lab organiser is Harold Bruintjes



  • The language for this course will be English.
  • The implementation is expected to be in Java or C++.
  • Reports have to handled in a clearly defined location in your Git repository.
  • Attendance of every meeting is mandatory.
  • Students are expected to form and work in groups of 3 students.
  • Grades are based on the quality of the written reports, the quality of the source code, the strength of the AI, team play and work attitude.