Introduction to Computer Science

• Module: Introduction to Computer Science (CH-232)
• Semester: Fall 2023
• Instructor: Jürgen Schönwälder
• Office Hours: Monday, 11:15-12:30 (Research I, Room 87)
• TA (Group A): TBD
• TA (Group B): TBD
• TA (Group C): TBD
• TA (Group D): TBD
• TA (Group E): TBD
• TA (Group Z): TBD
• Class: TBD
• Class: TBD
• Class: TBD
• 1st Module Exam: TBD
• 2nd Module Exam: TBD

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).

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.

• Slides
• Lecture Notes
• Haskell Notes
• Source Code

• Eric Lehmann, F. Thomson Leighton, Albert R. Meyer: "Mathematics for Computer Science", 2018
• Richard Hammack: "Book of Proof", 3rd edition, 2020
• 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

• Glasgow Haskell Compiler (download ghc from here or use your package manager)
• Haskell: An advanced purely functional programming language (web site about Haskell)
• Learn You a Haskell for Great Good! (a book also available online)
• Real World Haskell (a book also available online)
• What I Wish I Knew When Learning Haskell (an open source book by Stephen Diehl)
• Haskell Tutorial (a relatively concise online tutorial)
• Haskell to Core: Understanding Haskell Features Through Their Desugaring
• UNIX Tutorial for Beginners (a tutorial that can be downloaded and done offline)
• Background reading on Hoare Logic

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. There are 10 regular assignments and 2-3 bonus assignments.

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 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 explicitly 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.