02110 Algorithms and Data Structures II 
General Info
 Mandatory Exercises
 Weekplan
 Programming Competition
 Exam sets
 FAQ
 Fall 15
 Fall 16
General Info
Teacher
Associate Professor Inge Li Gørtz, office 018, building 322, Email: inge@dtu.dk. Office hours: Tuesday 12.1513.
When Thursday 812.
The course runs in the DTU fall semester.
Exercise class Thursday 810.30 in building 358, room H071 (English), H063, and H067.
The exercise classes will work as follows:

8.009.00 Group work. Time to work on the exercises you couldn't solve at home. The TAs will be there to help you.
 9.0010.30 Walkthrough of solutions to the exercises. Together with the TA you will go through the solutions to the exercises in class. You are expected to have already solved the exercises and you should be prepared to present your solutions to the rest of the class.
Lectures Thursday 10.3012 in Building 308, auditorium 12.
Textbook
CLRS: "Introduction to Algorithms", Cormen, Leierson, Rivest and Stein. 3rd edition. ISBN 9780262533058
Piazza The course uses Piazza as onlineforum for discussion of material. Sign up here.
Prerequisites The course builds on 02105 Algorithms and Data Structures I. You are expected to know the curriculum for 02105, which includes
 Basic algorithm analysis, asymptotic notation.
 Data structures: stacks, queues, linked lists, trees, heaps, priority queues, hash tables, unionfind, binary search trees.
 Searching and sorting: binary search, heap sort, insertion sort, mergesort.
 Graph algorithms: single source shortest paths (Dijkstra and SSSP in DAGs), Minimum spanning trees, topological sorting, Breadth first search, Depth first search, representation of graphs.
CodeJudge Exercises marked with [CJ] are implementation exercises and can be tested in CodeJudge (CodeJudge). For each of these exercises, a detailed specification of the input/output and a java template can be found on CodeJudge.
Mandatory assignments
In order to be allowed to participate in the written exam it is a requirement that you:
 pass at least 3 mandatory assignments from the week plans (more info below).
 implement (and pass the tests of) two of the implementation exercises on CodeJudge.
Each week from week 1 to 9 you will be asked to do written exercises and hand them in during the group work. These exercises will be corrected by the teaching assistants. It is a requirement for participation in the exam that you get 3 of the 9 exercises approved. The exercises do not count in the final grade for the course, but you have to pass at least 3 of them in order to be allowed to participate in the exam.
The deadline for handing in the mandatory assignment on weekplan x is Thursday in week x+1 at 9:00.
The deadline for handing in the home work must be respected.
You are welcome to hand in more than 3  the TAs will correct all the home work you hand in.
The deadline for passing the implementation exercises is Thursday in week 11.
Collaboration policy All mandatory exercises are subject to the following collaboration policy. The exercises are individual. It is not allowed to collaborate on the exercises, except for discussing the text of the exercise with teachers and fellow students enrolled on the course in the same semester. Under no circumstances is it allowed to exchange, handover or in any other way communicate solutions or part of solutions to the exercises. It is not allowed to use solution from previous years, solutions from similar courses, or solutions found on the internet or elsewhere.
Weekplan
The weekplan is preliminary It will be updated during the course.
Week 
Topics 
Slides 
Weekplan 
Material 
Demos 

Data Structures I: RedBlack trees and 234 trees 
1x1 · 4x1 · full 
Week 1 
 Algorithms in Java by Sedgewick, page 572585 (on Campusnet)
 CLRS chapter 13
 Survival guide
 

Data Structures II: Amortized Analysis + splay trees. 
1x1 · 4x1 · full 
Week 2 
 Section 15 + 16.516.6 in notes by Jeff Erickson (can also be found on CampusNet)
 (CLRS chapter 17)

Splay
Trees
Splay Trees
Deletions


Dynamic programming I: Rod cutting and longest common subsequence 
1x1 · 4x1· full 
Week 3 
 CLRS 15.015.1, (15.3), 15.4
 

Dynamic programming II: Sequence alignment and All Pairs Shortest Paths 
1x1 · 4x1 · full 
Week 4 
 CLRS 25.0, 25.1
 Algorithm Design by Kleinberg and Tardos, section 6.6 (on CampusNet).
 Sequence Alignment 

Network Flow I: Maxcut minflow theorem, augmenting paths, FordFulkerson 
1x1 · 4x1 · full 
Week 5 
 Ford
Fulkerson and min cut 

Network Flow II: EdmondsKarp, maximum bipartite matching 
1x1 · 4x1 · full 
Week 6 
 

Randomized Algorithms: Introduction, quicksort, selection. 
1x1 · 4x1 
Week 7 
 CLRS chapter 7, 9.2
 notes by Paul Fischer on randomized algorithms section 1, 2 (except 2.4 and 2.5)
 Alternative reading: Algorithm Design by Kleinberg and Tardos, section 13.5 (on CampusNet).
 

Fenwick Trees and Programming competition 

Week 8 
 

Strings I: String matching 
1x1 · 4x1 
Week 9 
 Automata
matching and
construction
KMP matching and
construction 

Strings II: Suffix trees 
1x1 · 4x1 · full 
Week 10 
 Data Structures & Algorithms in Java by Goodrich and
Tamassia, section 12.3 (on CampusNet)
 trie search and
trie construction 

Computational Geometry: TBA 

Week 11 
 

Introduction to NPcompletenes 
1x1 · 4x1 
Week 12 
 Notes by Paul Fischer Appendix C
 CLRS 34.034.2 + 34.3 until page 1069 (page 10481069)
 

Questions, repetition, prize for programming competition 
1x1 · 4x1 
Week 13 
 
Old Exam Sets
Here is the exam set from the two previous years: ExamE15, ExamE14 and a solution to E14.
And an example exam: ExampleExam.
Solutions to selected exercises
Here are solutions to a couple of exam like exercises, such that you
can see how a well written solution could be: Example solutions.
Frequently Asked Questions
How should I write my mandatory
exercises?Here is a few tips:
 Write things directly: Cut to the chase and avoid anything that is not essential. Test your own writing by answering the following question: “Is this the shortest, clearest, and most direct exposition of my ideas/analysis/etc.?”
 Add structure: Don’t mix up description and analysis unless you know exactly what you are doing. For a data structure explain following things separately: The contents of the data structure, how to build it, how to query/update it, correctness, analysis of space, analysis of query/update time, and analysis of preprocessing time. For an algorithm explain separately what it does, correctness, analysis of time complexity, and analysis of space complexity.
 Be concise: Convoluted explanations, excessively long sentences, fancy wording, etc. have no in place scientific writing. Do not repeat the problem statement.
 Try to avoid pseudocode: Generally, aim for human readable
description of algorithms that can easily and unambiguously be
translated into code.
The only exception for this is dynamic programming algorithms, where
pseudo code is often the best choice.
 Examples for support: Use figures and examples to illustrate key points of your algorithms and data structures.
Can I write my assignments in Danish?
Ja. Du er meget velkommen til at aflevere på dansk. Det samme gælder
til eksamen.