CPSC 327 | Data Structures and Algorithms | Spring 2025 |
On this page:
Course Description and Objectives |
At the heart of computer science is the development of efficient algorithms for solving problems. This course focuses on the design and analysis of data structures and algorithms, continuing the study of data structures begun in CPSC 225 with a focus on more advanced structures (hashtables, heaps, balanced binary trees, graphs, and building your own data structure for a particular application), common algorithmic approaches (iterative, recursive, divide-and-conquer, greedy, backtracking, branch-and-bound, dynamic programming), and covering topics such as correctness, efficiency, complexity, and NP-completeness. The course has three main goals (and several subgoals):
By the end of the course, the successful student should be able to:
|
---|---|
Prerequisites |
CPSC 225 is required. CPSC 229 is helpful, but not essential. |
Assignments and Evaluation |
Readings and Class Prep: Readings are the first introduction for most material — it often takes more than one encounter to fully absorb something, and class time is more effective if it can be used to fill in the gaps and answer questions about things you have already started to think about. Class prep assignments have a few questions or contain a short exercise to help you self-assess what concepts you understand from the reading and identify what needs further attention. Homework and Programming Assignments: Hands-on practice is essential for learning and mastery, and homework problems provide an opportunity to tackle problems for yourself. Most homework will involve written solutions, but there will also be a few programming assignments. Exams and Interviews: Exams and interviews assess what you, individually, have mastered. There will be three midterm exams in the first half of the semester covering core skills and "toolbox elements" — analysis of algorithms, ADTs and data structures, and graphs and graph algorithms — and a final exam covering the design and development of data structures and algorithms. There will also be interviews following each of the programming assignments and for one "design problem" homework. The dates of the exams and the approximate dates of the programming assignments and design problem are on the schedule page. More details about each exam and the format of interviews will be announced prior to the exam/first interview. Final Grades: There are two components to the final course grade: engagement (30%) and mastery (70%). Engagement covers your active participation in the learning activities of the course: attendance (10%), class prep assignments (10%), homeworks (50%), and programming assignments (30%). Mastery reflects your mastery of competency areas based on the course learning objectives as demonstrated by exams and interviews. Grading:
Revise-and-resubmit: Understanding feedback and fixing problems is an important component of learning, and most assignments will have an opportunity for revise-and-resubmit. However, revise-and-resubmit requires there to be something to revise and feedback to act on --- it is not intended as a de facto extension. To be eligible for revise-and-resubmit, there must be some effort put into the initial handin (a score 3 or higher). The resubmit deadline will be announced when the initial handin is handed back, and will generally allow a week or so for revision. Reviewing feedback and understanding and correcting mistakes is a valuable part of learning If you are concerned about your grade or are struggling with the material, come to office hours to get help! Staying on top of things and seeking help as soon as possible when you need it is the best route to success. |
Time Expectations |
You are expected to attend all scheduled class meetings (3 hours per week) and interviews (approx 1-2 hours total over the course of the semester), as well as some office hours and/or help sessions (minimum of 3-4 hours over the course of the semester). Interviews will be scheduled at mutually convenient times. If you cannot attend scheduled office hours or help sessions, you can make an appointment to meet at another time. You will also need to spend additional time outside of class completing assignments and studying. This additional out-of-class time is intended to be approximately 8 hours per week on average, though your experience may vary. However, if you routinely spend much less time, you may not be successfully mastering the material — or you should challenge yourself by tackling some of the extra credit! — and if you routinely spend substantially more time, especially if you feel like you are spinning your wheels and not making progress, you should visit office hours for help. |
Course Materials |
TextbookThe Algorithm Design Manual (3rd ed) This is both a textbook for learning how to design algorithms and data structures, and a useful reference with an extensive catalog of algorithmic problems that arise in practice. I hope that you will enjoy reading the book during the course and that you will want to hang on to the book afterwards to use in your future algorithmic endeavors. If you are buying the book on Amazon or elsewhere, note that the third edition has a very similar-looking cover to the second edition. Look for "Third Edition" on the cover and/or check the ISBN to make sure you are getting the right version. Additional material will be handed out or posted on the course webpage. SoftwareThere will be several programming assignments which involve programming in Java. The tools that you need (Java, JavaFX, Eclipse) are available on the lab computers in Rosenberg 009 (reboot them to Linux) and Lansing 310 and via the Linux virtual desktop. Using the Linux virtual desktop for remote access to Linux is recommended, but if you want to set up your own computer as an alternative to using the Linux VDI, you will need Java, JavaFX, Eclipse, and a file transfer program (FileZilla) to copy files between your computer and the Linux filesystem. Information on how to set up your own computer will be provided in advance of the first programming assignment. |