CS2013-final-report

Given the nature of tutorials, it can be difficult to quantify the number of hours spent on a topic. Below, I base the
hours dedicated to each unit by assuming roughly 3 hours of contact time with the students during each week of
the 12-week semester.
How are students assessed
Students are assessed via the preparedness and contributions to the weekly discussions, by their written solutions
to problem set questions, and by the quality and correctness of their compiler implementations. Students also give
presentations on their final projects to the entire class.
Course textbooks and materials
The primary textbook is Compilers: Principles, Techniques, and Tools by Aho, Lam, Sethi, and Ullman. Papers
from the primary literature are also included when possible. Supplementary material for background reading and
for the project is provided on a website.
Why do you teach the course this way
The tutorial format offers a unique opportunity to tailor material specifically to student interest, and to allow them
to explore and learn material on their own. The interactions between tutorial partners in the weekly meetings
develops communication skills and thought processes that cannot be as easily fostered in lecture-style courses.
The group projects also enable students to develop solid software engineering practices and to appreciate the
theoretical foundations of each phase of compilation.
The students all enjoy the tutorial-style and collaborative environment it fosters, and they typically rate this class
among the most challenging offered at Williams.
Body of Knowledge coverage
KA Knowledge Unit Topics Covered Hours
PL Basic Type Systems All (mostly review of existing knowledge) 2
PL
PL
Program
Representation
Language Translation
and Execution
All 2
All 3
PL Syntax Analysis All 5
PL
Compiler Semantic
Analysis
All 5
PL Code Generation All 5
PL Runtime Systems All 5
PL Static Analysis Relevant program representations, such as basic blocks, controlflow
graphs, def-use chains, static single assignment, etc.
Undecidability and consequences for program analysis
Flow-insensitive analyses: type-checking
Flow-sensitive analyses: forward and backward dataflow analyses
Tools and frameworks for defining analyses
Role of static analysis in program optimization
Role of static analysis in (partial) verification and bug-finding
SE Software Design System design principles
Refactoring designs and the use of design patterns.
6
2
- 354 -