| Course Objectives | Lecture and Discussion Sections |
| Course Website | Assignments |
| Instructors and Class Meetings | Examinations |
| Schedule of Lecture Topics and Exams | Grading |
| Textbook |
| Lecture 1 MW 4-5:50 WGYoung CS 50 David Smallberg das@cs.ucla.edu |
|||
| Discussion 1A F 12-1:50 Dodd 161 Evan Becker evbecker@ucla.edu |
Discussion 1C F 12-1:50 Haines A2 Nikki Woo nikki.k.woo@gmail.com |
Discussion 1E F 2-3:50 Dodd 167 Roshni Iyer roshnigiyer@ucla.edu |
Discussion 1G F 4-5:50 Boelter 5249 Hunter Dellaverson hdellaverson@gmail.com |
| Discussion 1B F 12-1:50 Haines 220 Kareem Ahmed kareem.yousrii@gmail.com |
Discussion 1D F 2-3:50 Rolfe 3126 Siyan Dong siyand@cs.ucla.edu |
Discussion 1F F 2-3:50 Royce 156 Varuni Sarwal sarwal8@gmail.com |
Discussion 1H F 12-1:50 Boelter 5436 Da Yin da.yin@cs.ucla.edu |
Office hours for the instructor, TAs, and LAs are on the class web page.
| Week | Date | Topics |
|---|---|---|
| 1 | Mar. 28 | Introduction/Computer History |
| Mar. 30 | Basics | |
| 2 | Apr. 4 | Basics |
| Apr. 6 | Basics | |
| 3 | Apr. 11 | Control Flow |
| Apr. 13 | Control Flow | |
| 4 | Apr. 18 | Functions |
| Apr. 20 | Functions and Program Development | |
| 5 | Apr. 25 | Parameters |
| Apr. 26 (Tue.) | Midterm 1 (6:00 pm - 7:50 pm) | |
| Apr. 27 | Arrays | |
| 6 | May 2 | Arrays |
| May 4 | Strings | |
| 7 | May 9 | Pointers |
| May 11 | Pointers | |
| 8 | May 16 | Structs and Classes |
| May 17 (Tue.) | Midterm 2 (6:00 pm - 7:50 pm) | |
| May 18 | Classes | |
| 9 | May 23 | Constructors |
| May 25 | Pointers | |
| 10 | May 30 | Memorial Day Holiday |
| Jun. 1 | Review | |
| end of 10 | Jun. 4 (Sat.) | Final exam (11:30 am - 2:30 pm) |
The required course textbook is an interactive online zyBook that offers a number of advantages over static text-dense textbooks. To purchase a subscription ($77):
Lectures will present the material you'll need to know for this class, expanding on material from the course textbook. 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 programs without writing programs. There will be several 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.
Some assignments will be activities in the course text designed to help ensure that you understand important concepts.
Occasionally you'll be asked to fill out a brief online form (e.g., because we need to gather some information for planning purposes) in a timely manner. These "responsibility assignments" will be so labelled and completing them will be worth a small part of your grade.
Every C++ program you turn in for this class outside of the course text must run successfully using two compilers, as specified in the Project Requirements document.
Programming projects are due at 11 PM on the dates 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 | Tuesday, April 5 |
| Project 2 warmup | Saturday, April 9 |
| Project 2 | Thursday, April 14 |
| Project 3 warmup | Tuesday, April 19 |
| Project 3 | Wednesday, April 27 |
| Project 4 part 1 | |
| Project 4 part 2 | Wednesday, May 4 |
| Project 5 | Monday, May 16 |
| Project 6 | |
| Project 7 | Thursday, June 2 |
The midterm 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:
| Projects (excluding zyBook assignments) | 42% |
| zyBook assignments | 7% |
| Responsibility assignments | 1% |
| Midterm 1 | 7% |
| Midterm 2 | 13% |
| Final exam | 30% |
The total points you earn from assignments (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 you have read and understood our expectations about academic integrity.