| Course Objectives | Lecture and Discussion Sections |
| Course Website | Programming Projects and Homeworks |
| Instructor and Class Meetings | Examinations |
| Schedule of Lecture Topics and Exams | Grading |
| Textbook |
In this course, you will learn how to employ data abstraction to build programs larger than those you constructed in CS 31. You will learn how to use a variety of data structures in the course of solving problems, and importantly, how to analyze what data structures and algorithms are most appropriate for a given problem. In addition, you will deepen your understanding of modern programming by learning the principles of object-oriented and generic programming.
The URL for the course website is https://cs.ucla.edu/classes/spring22/cs32. You must check the site for announcements at least every other weekday. You must also check your email as regularly. The course Bruin Learn site is used mostly to house Zoom links to lectures, office hours, and learning assistant workshops; recorded lectures and workshops; and material posted by TAs.
| Lecture 1 MW 4-5:50 WGYoung CS50 David Smallberg das@cs.ucla.edu |
||||
| Discussion 1A F 10-11:50 Rolfe 3126 Wenqi Zou wenqizou625@g.ucla.edu |
Discussion 1C F 12-1:50 Kaplan A51 Jason Panelli panelli@ucla.edu |
Discussion 1E F 12-1:50 Pub Aff 2232 Sirui Xie srxie@ucla.edu |
Discussion 1G F 12-1:50 Dodd 167 Shardul Parab shardulparab@g.ucla.edu |
Discussion 1I F 12-1:50 Royce 156 Srinath Ajmeera srinath@g.ucla.edu |
| Discussion 1B F 10-11:50 Royce 156 Yiyou Chen gerry99@ucla.edu |
Discussion 1D F 12-1:50 Kaplan A65 Sonia Jaiswal soniajaiswal@g.ucla.edu |
Discussion 1F F 12-1:50 Rolfe 3126 Parth Shah parthushah8@g.ucla.edu |
Discussion 1H F 10-11:50 Rolfe 1200 Shikha Mody smody@ucla.edu |
|
Office hours for the instructor, TAs, and LAs are on the class web page.
| Week | Date | Topics | Book |
|---|---|---|---|
| 1 | Mar. 28 | Introduction, C++ Review | Chapter 1 |
| Mar. 30 | Data Abstraction, C++ Classes | Chapter 1 | |
| Pointers, Dynamic Arrays, Resource Management | Chapter 3 | ||
| 2 | Apr. 4 | Resource Management | Chapter 3 |
| Apr. 6 | Linked Lists | Chapters 4 and 8 | |
| 3 | Apr. 11 | Stacks and Queues | Chapters 6, 7, 13, and 14 |
| Apr. 13 | Inheritance | Chapter 3 | |
| 4 | Apr. 18 | Inheritance and Polymorphism | Chapter 3 |
| Apr. 20 | Recursion | Chapters 2 and 5 | |
| Apr. 20 | Midterm 1 (6:00 pm to 7:30 pm) | ||
| 5 | Apr. 25 | Recursion, Templates | Chapters 2 and 5 |
| Apr. 27 | Templates, STL | ||
| 6 | May 2 | STL, Algorithmic Efficiency | Chapters 10 and 11 |
| May 4 | Sorting | Chapter 11 | |
| 7 | May 9 | Sorting, Trees | Chapters 11 and 15 |
| May 11 | Trees | Chapter 16 | |
| 8 | May 16 | Midterm 2 (6:00 pm to 7:30 pm) | |
| May 18 | Tables, Tree-based Tables, Hash Tables | Chapter 18 | |
| 9 | May 23 | Hash Tables | Chapter 18 |
| May 25 | Trees and Arrays, Priority Queues, Heaps | Chapter 17 | |
| 10 | May 30 | Memorial Day Holiday | |
| Jun. 1 | Graphs | Chapter 20 | |
| end of 10 | Jun. 5 (Sun.) | Final exam (11:30 am to 2:30 pm) |
If you prefer a traditional textbook for coverage of the course material in a form other than the live or recorded lectures or Carey Nachenberg's online slides, we recommend Data Abstraction and Problem Solving with C++: Walls and Mirrors, Seventh Edition, by Frank M. Carrano, Pearson, 2017. The Sixth Edition, the Fifth Edition or even the Fourth Edition would do as well.
Lectures will present the material you'll need to know for this class. In discussion sections, your TA along with a learning assistant (LA) will pose problems to solve collaboratively in class to help build your problem solving skills and ensure you understand key concepts. They may answer questions that arise about these concepts, lecture topics, and programming projects.
You cannot learn how to write large programs without writing large programs. There will be four programming projects. Each project specification will detail any requirements that differ from the general project requirements. Your program correctness score is based on your program's correctness as determined by our testing. The amount of time you spent working on the program is irrelevant; indeed, if you follow our software development advice, you'll probably spend less time and get a higher score than if you don't.
Since the projects cannot give you experience with all the material in the course, there will be five homework assignments in addition to the projects. These may require you to answer some questions and analyze or write small programs. Some of the work you put into the homework will do double duty: it will help you with a programming project or will serve as a good study guide for an exam. If you are seriously interested in mastering the course material, you will do every homework problem, even though not every problem of every homework assignment will be graded. (You won't know which problems won't be graded.)
Every C++ program you turn in for this class must run successfully using two compilers, as specified in the Project Requirements document.
Programming projects and homeworks are due at 11 PM on the dates listed below. Late submissions will be penalized by 0.0034722% per second (which comes to 12.5% per hour), making a submission worthless if submitted after 7 AM the next morning. It is your responsibility to start early and to make backups to removable devices or to online storage
| Project 1 | Wednesday, April 6 | |
| Homework 1 | Tuesday, April 12 | |
| Project 2 | Tuesday, April 19 | |
| Homework 2 | Tuesday, April 26 | |
| Homework 3 | Tuesday, May 3 | |
| Project 3 | ||
| Homework 4 | Tuesday, May 24 | |
| Project 4 | ||
| Homework 5 | Thursday, June 2 |
The midterms will cover material from the lectures. The final examination will cover material from the entire course. Missing the final for any reason will result in a final exam score of zero.
Your grade in the course will be determined from your total score, although a final exam score below 40 may subject you to a failing grade regardless of your total score. The total score is determined from the graded materials as follows:
| Project 1 | 1% |
| Project 2 | 10% |
| Project 3 | 10% |
| Project 4 | 10% |
| Homeworks | 19% |
| Midterm 1 | 7% |
| Midterm 2 | 13% |
| Final exam | 30% |
The total points you earn from projects and homeworks (scaled to 0 through 100) will be capped at 30 points above the mean of your exam scores (scaled to 0 through 100). For example, if you average 90 on the assignments, your midterm scores are 50 and 60, and your final is 40, then your assignment average is treated as only 80 (because that's 30 more than the mean of 50, 60, and 40). In other words, your assignment scores won't count fully if you can't show from your exam scores that you learned what you should have from the assignments.
A request for reconsideration of the grading for an item must be made within one week of our sending you your score for that item.
Be sure that you have read and understood our expectations about academic integrity.