Introduction to Computer Science


  • Module: Introduction to Computer Science (CH-232)
  • Semester: Fall 2019
  • Instructor: Jürgen Schönwälder
  • TA: Balani, Eglis
  • TA: Blaceri, Romelda
  • TA: Chen, Tianyao
  • TA: Kabadzhov, Ivan
  • TA: Shandro, Jovan
  • Class: Tuesday, 11:15-12:30 (CNLH)
  • Class: Friday, 08:15-09:30 (CNLH)
  • Class: Friday, 09:45-11:00 (CNLH)
  • 1st Module Exam: Saturday 2019-12-14 09:00-11:00 (SCC Hall 3+4)
  • 2nd Module Exam: Saturday 2020-01-25 08:00-10:00 (ICC East Wing)
  • Office Hours: Monday, 11:15-12:30 (Research I, Room 87)

Content and Educational Aims

The module introduces fundamental concepts and techniques of computer science in a bottom-up manner. Based on clear mathematical foundations (which are developed as needed), the course discusses abstract and concrete notions of computing machines, information, and algorithms, focusing on the question of representation versus meaning in Computer Science.

The module introduces basic concepts of discrete mathematics with a focus on inductively defined structures, to develop a theoretical notion of computation. Students will learn the basics of the functional programming language Haskell because it treats computation as the evaluation of pure and typically inductively defined functions. The module covers a basic subset of Haskell that includes types, recursion, tuples, lists, strings, higher-order functions, and finally monads. Back on the theoretical side, the module covers the syntax and semantics of Boolean expressions and it explains how Boolean algebra relates to logic gates and digital circuits. On the technical side, the course introduces the representation of basic data types such as numbers, characters, and strings as well as the von Neuman computer architecture. On the algorithmic side, the course introduces the notion of correctness and elementary concepts of complexity theory (big O notation).

Intended Learning Outcomes

By the end of this module, students will be able to

  • explain basic concepts such as the correctness and complexity of algorithms (including the big O notation);
  • illustrate basic concepts of discrete math (sets, relations, functions);
  • recall basic proof techniques and use them to prove properties of algorithms;
  • explain the representation of numbers (integers, floats), characters and strings, and date and time;
  • summarize basic principles of Boolean algebra and Boolean logic;
  • describe how Boolean logic relates to logic gates and digital circuits;
  • outline the basic structure of a von Neumann computer;
  • explain the execution of machine instructions on a von Neumann computer;
  • describe the difference between assembler languages and higher-level programming languages;
  • define the differences between interpretation and compilation;
  • illustrate how an operating system kernel supports the execution of programs;
  • determine the correctness of simple programs;
  • write simple programs in a pure functional programming language.


  • Eric Lehmann, F. Thomson Leighton, Albert R. Meyer: "Mathematics for Computer Science", 2018
  • David A. Patterson, John L Hennessy: "Computer Organization and Design: The Hardware/Software Interface", 4th edition, Morgan Kaufmann, 2011
  • Miran Lipovaca: "Learn You a Haskell for Great Good!: A Beginner's Guide", 1st edition, No Starch Press, 2011



Tu 11:15 Fri 08:15 Topics
2019-09-03 2019-09-06 Introduction and maze generation algorithms
2019-09-10 2019-09-13 String search algorithms, complexity and correctness
2019-09-17 2019-09-20 Mathematical notations and proof techniques
2019-09-24 2019-09-27 Sets, relations, and functions
2019-10-01 2019-10-04 Representation of integer and floating point numbers
2019-10-08 2019-10-11 Representation of characters, strings, date and time
2019-10-15 2019-10-18 Boolean operations and expressions / practice midterm exam
2019-10-22 2019-10-25 Boolean algebra and normal forms
2019-10-29 2019-11-01 Boolean expression minimization and Boolean logic
2019-11-05 2019-11-08 Logic gates, combinational and sequential digital circuits
2019-11-12 2019-11-15 von Neuman computer architecture, assembly programming
2019-11-19 2019-11-22 Interpreter, compiler, operating systems
2019-11-26 2019-11-29 Software specification and verification
2019-12-03 2019-12-06 Automated generation of proof goals and termination proofs

Functional Programming (Haskell)

Fri 09:45 Topics
2019-09-06 Haskell (ghc, expressions)
2019-09-13 Haskell (lists, characters, strings, tuples)
2019-09-20 Haskell (characters, strings, tuples, types)
2019-09-27 Haskell (functions, pattern matching, recursion)
2019-10-04 Haskell (guards, bindings, case expressions)
2019-10-11 Haskell (Lambda functions, composition, currying)
2019-10-18 Practice Midterm Exam
2019-10-25 Haskell (higher order functions)
2019-11-01 Haskell (datatypes)
2019-11-08 Haskell (typeclasses)
2019-11-15 Haskell (functors, applicative, monads)
2019-11-22 Haskell (IO monad)
2019-11-29 Haskell (IO monad)
2019-12-06 Summary and Outlook


Date/Due Name Topics
2019-09-20 Sheet #1 Boyer-Moore algorithm, Haskell expressions and operators
2019-09-27 Sheet #2 Proof by contrapositive and induction, Haskell isLeapYear, rotate, circle functions
2019-10-04 Sheet #3 Proof by induction, relation properties, Haskell isPrime and isCircPrime functions
2019-10-11 Sheet #4 Prefix order relations, function composition, Haskell isSpecialPrime function
2019-10-18 Sheet #5 B-complement, IEEE 754 floating pointer numbers, Haskell toBase, fromBase, showBase, readBase functions
2019-10-25 Sheet #6 Character encoding, data and time calculations, Haskell emoji encoding and decoding
2019-11-01 Sheet #7 Universal Boolean functions, Boolean expressions and equivalence laws, Haskell variables and truthtable
2019-11-08 Sheet #8 Quine-McCluskey algorithm
2019-11-15 Sheet #9 Full-adder digital circuit, Haskell fold function duality theorems
2019-11-22 Sheet #10 Assembly programming, ripple counter, Haskell type classes
2019-11-29 Sheet #11 Process creation, BNF grammars, Haskell edit distance
2019-12-06 Sheet #12 Program correctness proof
2020-01-15 Sheet #13 Extra sheet for those who did not manage to obtain 50/120


The final grade is determined by the final exam (100%). In order to sit for the final exam, it is necessary to have 50% of the assignments correctly solved.

Electronic submission is the preferred way to hand in homework solutions. Please submit documents (plain ASCII/UTF-8 text or PDF, no Word) and your source code (packed into a tar or zip archive after removing all binaries and temporary files) via the online submission system. If you have problems, please contact one of the TAs.

Late submissions will not be accepted. Assignments may need to be defended in an oral interview. In case you are ill, you have to follow the procedures defined in the university policies to obtain an official excuse. If you obtain an excuse, the new deadline will be calculated as follows:

  1. Determine the number of days you were excused until the deadline day, not counting excused weekend days.
  2. Determine the day of the end of your excuse and add the number of day you obtained in first step. This gives you the initial new deadline.
  3. If the period between the end of your excuse and the new deadline calculated in the second step includes weekend days, add them as well to the new deadline. (Iterate this step if necessary.)

For any questions stated on assignment sheets or exam sheets, we by default expect a reasoning for the answer given, unless explicitely stated otherwise.

Students must submit solutions individually. If you copy material verbatim from the Internet (or other sources), you have to provide a proper reference. If we find your solution text on the Internet without a proper reference, you risk to lose your points. Any cheating cases will be reported to the registrar. In addition, you will lose the points (of course).

Any programs, which have to be written, will be evaluated based on the following criteria:

  • correctness including proper handling of error conditions
  • proper use of programming language constructs
  • clarity of the program organization and design
  • readability of the source code and any output produced

Source code must be accompanied by a README file providing an overview of the source files and giving instructions how to build the programs. A suitable Makefile is required if the build process involves more than a single source file.

If you are unhappy with the grading, please report immediately (within one week) to the TAs. If you can't resolve things, contact the instructor. Problem reports which come late, that is after the one week period, are not considered anymore.