CSE 30872 is an elective course in the Computer Science and Engineering program at the University of Notre Dame. This course encourages the development of practical programming and problem solving skills through extensive practice and guided learning. The bulk of the class revolves around solving brain-teaser and puzzle-type problems that often appear in programming contests, online challenges, and job interviews. Additionally, basic software engineering practices such as planning, debugging, testing, and source code management may be discussed.
Upon successful completion of this course, students will be able to:
Parse a variety of inputs and model problems.
Utilize appropriate data structures to represent and solve problems.
Implement common problem solving techniques and algorithms.
Employ modern software development methods and tools.
Debug and test code within an automated testing environment.
Unit | Date | Topics | Assignment |
---|---|---|---|
I/O | 08/22 | Introduction, I/O Slides Slides | Reading 00 |
08/24 | Complexity, Coding Style Slides Slides | Challenge 00 | |
Sequence Containers | 08/27 | Arrays, Lists Slides | Reading 01 |
08/29 | Stacks, Queues Slides | Challenge 01 | |
08/31 | Debugging Slides | Challenge 02 | |
Searching, Sorting | 09/03 | Searching Slides | Reading 02 |
09/05 | Engineering Industry Day | Challenge 03 | |
09/07 | Sorting Slides | Challenge 04 | |
Associative Containers | 09/10 | Maps, Sets Slides | Reading 03 |
09/12 | Hash Tables | Challenge 05 | |
09/14 | Testing / Profiling Slides | Challenge 06 | |
Complete Search | 09/17 | Subsets and Permutations Slides | Reading 04 |
09/19 | Backtracking | Challenge 07 | |
09/21 | Static Analysis Slides | Challenge 08 | |
Greedy Algorithms | 09/24 | Optimization Slides | Reading 05 |
09/26 | Compression | Challenge 09 | |
09/28 | Git Tricks Slides | Challenge 10 | |
Dynamic Programming | 10/01 | Memoization Slides | Reading 06 |
10/03 | Table Building | Challenge 11 | |
10/05 | Dredd Slides | Challenge 12 | |
In-class Contest I | 10/08 | Contest I | |
10/10 | Contest I | ||
10/12 | Contest I | ||
Fall Break | |||
Trees | 10/22 | Representation, Traversal Slides | Reading 07 |
10/24 | Divide and Conquer | Challenge 13 | |
10/26 | Documentation Slides | Challenge 14 | |
Graphs I | 10/29 | Representation, Traversal Slides | Reading 08 |
10/31 | Shortest Paths | Challenge 15 | |
11/02 | Building Slides | Challenge 16 | |
Graphs II | 11/05 | Spanning Trees Slides | Reading 09 |
11/07 | Topological Sorting | Challenge 17 | |
11/09 | Packaging Slides | Challenge 18 | |
Graphs III | 11/12 | Paths Slides | Reading 10 |
11/14 | Flows and Cuts | Challenge 19 | |
11/16 | Dredd | Challenge 20 | |
Number Theory | 11/19 | Primes and Modular Arithmetic Slides | Reading 11 |
11/21 | Thanksgiving | Challenge 21 | |
11/23 | Thanksgiving | ||
Miscellaneous | 11/26 | Brain Teasers Slides | Challenge 22 |
11/28 | Graduate School Slides | Challenge 23 | |
11/30 | Slacking and Hacking | Challenge 24 | |
Final | 12/03 | Contest II | |
12/05 | Contest II | ||
Final | 12/12 |
Component | Points |
---|---|
Readings Weekly reading assignments. | 10 × 2 |
Challenges Weekly programming challenges. | 24 × 6 |
Style Programming style for each challenge. | 24 × 1 |
External External programming contest. | 30 |
Contests In-class programming contests. | 2 × 36 |
Participation Regular class attendation and contribution to course community. | 10 |
Total | 300 |
Grade | Points | Grade | Points | Grade | Points |
---|---|---|---|---|---|
A | 285-300 | A- | 270-284 | ||
B+ | 260-269 | B | 250-259 | B- | 240-249 |
C+ | 230-239 | C | 220-229 | C- | 210-219 |
D | 195-209 | F | 0-194 |
All Readings and Challenges are to be submitted to your own private GitLab repository. Unless specified otherwise:
Students are expected to attend and contribute regularly in class. This means answering questions in class, participating in discussions, and helping other students.
Foreseeable absences should be discussed with the instructor ahead of time.
Any academic misconduct in this course is considered a serious offense, and the strongest possible academic penalties will be pursued for such behavior. Students may discuss high-level ideas with other students, but at the time of implementation (i.e. programming), each person must do his/her own work. Use of the Internet as a reference is allowed but directly copying code or other information is cheating. It is cheating to copy, to allow another person to copy, all or part of an exam or a assignment, or to fake program output. It is also a violation of the Undergraduate Academic Code of Honor to observe and then fail to report academic dishonesty. You are responsible for the security and integrity of your own work.
In the case of a serious illness or other excused absence, as defined by university policies, coursework submissions will be accepted late by the same number of days as the excused absence.
Otherwise, there is a penalty of 25% per day late (except where noted). You may submit some parts of an assignment on time and some parts late. Each submission must clearly state which parts it contains; no part can be submitted more than once.
Any student who has a documented disability and is registered with Disability Services should speak with the professor as soon as possible regarding accommodations. Students who are not registered should contact the Office of Disabilities.
For the assignments in this class, you may discuss with other students and consult printed and online resources. You may quote from books and online sources as long as you cite them properly. However, you may not look at another student's solution, and you may not look at solutions.
The following table summarizes how you may work with other students and use print/online sources:
Resources | Solutions | |
---|---|---|
Consulting | Allowed | Not Allowed |
Copying | Cite | Not Allowed |
See the CSE Guide to the Honor Code for definitions of the above terms.
If an instructor sees behavior that is, in his judgement, academically dishonest, he is required to file either an Honor Code Violation Report or a formal report to the College of Engineering Honesty Committee.