Important Websites

Lectures

8:30-11:20AM , Friday RCH 211

Instructor

Prof. Arie Gurfinkel, Office: DC 2536, first . last AT uwaterloo.ca, Office Hours: by appointment

Teaching Assistant

Jakub Kuderski, first . last AT uwaterloo.ca, Office Hours: by appointment

Textbook

No required textbook. Lecture slides, lecture notes, and reading material will be provided.

Some of the sources from which material will be drawn:

Course Description and Main Topics

This is an introductory graduate course. Its intent is to provide all students that are interested in software systems with a basic background that will help them succeed in subsequent endeavours (courses, research, and work in industry) related to software. The course is intended to be “hands-on” – there is a large project component that involves building a software system.

The course is divided broadly into three components: software systems (~40%), mathematical logic (~15%), and data structures (~45%).

Under software systems, we will cover topics such as systems programming and operating systems, scripting, system calls, libraries, compilers and interpreters.

Under mathematical logic, we will cover topics such as propositional logic, syntax, semantics, entailment, deduction and the use of logic in software.

Under data structures, we will cover topics such as stacks, heaps, trees, and graphs, and algorithms to manipulate them.

Prerequisite

Graduate standing in the ECE department at Waterloo.

Grading

Grades may be curved or adjusted at instructor’s discretion.

  • Assignments: 40%
  • Project: 10%
  • Final Exam: 50%

You must pass the assignments and the final exam (separately) to pass the course. All assignments will be returned in class, during office hours, or through LEARN.

Assignments

The assignments form an integral part of this course. They comprise several stages that span the term and involve the use of various software tools and techniques to solve a problem. They will exercise skills involving systems programming, use of libraries, and use of third-party software. Programming is to be done in C and scripting languages only. If you are unfamiliar with these or are weak at programming or scripting, you can do some extra work on your own in parallel with the course to strengthen those skills.

Assignments will be available at least two weeks before they are due.

Project

There will be a significant programming project, separate from the assignments. Details of the project be released during the course.

Course Policies

By registering for this class, students agree to the following class policies:

Independent work. All work turned in will be that of the individual student unless stated otherwise. Violations would result in zero credit to all students concerned. Policy 71 will be followed for any discovered cases of plagiarism.

Lateness. You have 2 days of lateness to use on assignment submissions throughout the term. Each day you hand in an assignment late consumes one of the days of lateness. If you consume all of your late days, assignments that are still late will get 0 marks. You can only hand in an assignment up to the time all assignments are returned. Missed assignments get 0 marks. For example, you may hand in A1 two days late and A2 on time, or you can hand in A1 one day late and A2 one day late.

University Policies

Academic Integrity. In order to maintain a culture of academic integrity, members of the University of Waterloo community are expected to promote honesty, trust, fairness, respect and responsibility. [Check http://www.uwaterloo.ca/academicintegrity for more information.]

Grievance. A student who believes that a decision affecting some aspect of his/her university life has been unfair or unreasonable may have grounds for initiating a grievance. Read Policy 70, Student Petitions and Grievances, Section 4, http://www.adm.uwaterloo.ca/infosec/Policies/policy70.htm. When in doubt please be certain to contact the departments administrative assistant who will provide further assistance.

Discipline. A student is expected to know what constitutes academic integrity [check http://www.uwaterloo.ca/academicintegrity] to avoid committing an academic offense, and to take responsibility for his/her actions. A student who is unsure whether an action constitutes an offense, or who needs help in learning how to avoid offenses (e.g., plagiarism, cheating) or about rules for group work/collaboration should seek guidance from the course instructor, academic advisor, or the undergraduate Associate Dean. For information on categories of offenses and types of penalties, students should refer to Policy 71, Student Discipline, http:://www.adm.uwaterloo.ca/infosec/Policies/policy71.htm. For typical penalties check Guidelines for the Assessment of Penalties, http://www.adm.uwaterloo.ca/infosec/guidelines/penaltyguidelines.htm.

Appeals. A decision made or penalty imposed under Policy 70 (Student Petitions and Grievances) (other than a petition) or Policy 71 (Student Discipline) may be appealed if there is a ground. A student who believes he/she has a ground for an appeal should refer to Policy 72 (Student Appeals) http://www.adm.uwaterloo.ca/infosec/Policies/policy72.htm.

Note for Students with Disabilities. The AccessAbility Services, located in Needles Hall, Room 1132, collaborates with all academic departments to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum. If you require academic accommodations to lessen the impact of your disability, please register with the AccessAbility Services at the beginning of each academic term.

Acknowledgements

Thanks to Mahesh V. Tripunitara for sharing his experience and materials from a previous iteration of this course.