CS 212 Software Development
Fall 2020 • CS 212-01, CS 212-02 • 4 Credits
This course gives students experience with advanced programming topics, including inheritance and polymorphism, multithreaded programming, networking, database programming, and web development. Students will also learn techniques for designing, debugging, refactoring, and reviewing code.
This syllabus is similar to a contract between students and the instructor, and as such it is quite long (with many sections required by the university). A few key points from this syllabus are highlighted here:
We will primarily use Piazza for all asynchronous communication for this class, not email. See: Communication Policy
You should be stuck for an hour on a problem before seeking help, but you should definitely seek help if you have been stuck for an hour. See: Getting Help
Do not cheat. This includes working too closely with your classmates or the CS tutors. See: Cheating Policy
You must pass at least one exam to earn a C or higher letter grade in this class. See: Pass Requirements
You must make enough progress on projects to earn a C or higher letter grade in this class. See: Pass Requirements
Attendance is required one per week and late submissions are not accepted; but there are automatic exceptions granted for certain situations. See: Policy Exceptions
Treat this class like a part-time job and plan to spend 10 to 20 hours coding per week outside of class. See: Credit Hour Policy
You are still required to read through the entire syllabus below.
This section covers basic information about the course, instructor, and teacher assistants.
This syllabus covers the following lecture sections:
12:45pm – 2:30pm
Zoom: 998 7326 3891
4:35pm – 6:20pm
Zoom: 949 1721 3734
Generally, Tuesday lectures will be replaced by asynchronous content and Thursday lectures will be held synchronously via Zoom. See the course schedule for details.
See the Attendance Policy for whether you can attend a section you are not enrolled.
This syllabus covers the following lab sections:
3:30pm – 4:35pm
Zoom: 991 1044 4721
4:45pm – 5:50pm
Zoom: 931 6737 5825
After the first several weeks of the semester, lab times will convert to TA office hours and one-on-one code reviews with the instructor.
See the Attendance Policy for whether you can attend a section you are not enrolled.
Instructor and Assistants
The instructor and instructor office hours for this course will be:
The teacher assistant and teacher assistant office hours for this course will be:
See the Communication Policy for how to contact the instructor and TAs.
The prerequisite for this class is CS 245 Data Structures and Algorithms with a letter grade of C or higher. You may not take the prerequisite at the same time as this class.
There is a lab corequisite of CS 212L that you must take at the same time as this class.
This course utilizes resources and software that are freely available for enrolled students. There are no required books.
Below are important dates relevant to this class:
|08/18||Fall 2020 classes begin.|
|08/24||Last day to add classes online.|
|09/04||Census date; last day to drop without a “W” appearing on transcript.|
|🚩||09/29||Exam 1; retake opportunity on Thursday.|
|🚩||10/29||Project Cutoff; deadline to meet the project pass requirement.|
|10/30||Last day to withdraw from a class and receive a “W” on transcript.|
|🚩||11/17||Exam 2; retake opportunity on Thursday.|
|11/23||Beginning of a week-long Thanksgiving recess.|
|11/30||Classes resume following Thanksgiving recess.|
|🚩||12/03||Project Cutoff 2; deadline to pass project 2 design and project 3 functionality.|
|12/03||Fall 2020 classes end.|
|12/04||Finals begin; start of final code reviews.|
See the official academic calendar for other important dates.
There will be an individually-scheduled final code review instead of a final exam during finals week.
Learning and Assessment
This section covers the learning outcomes for this course and how they will be assessed.
At the end of this course, you should be able to:
- Independently design programs
- Produce professional-quality source code
- Implement large programs with 1,000 to 2,000 source lines of code (SLOC)
- Design and execute tests to find and repair software bugs
- Redesign and refactor code to improve quality
Assessment of these outcomes will be done by a combination of pass requirements, exams, homework, projects, and more. See Grading Breakdown below for details.
To ensure you are meeting the learning outcomes for this course, you must meet the following minimum requirements to receive a C or higher grade in this course:
Exam Pass Requirement: Students must receive an average C letter grade or higher on at least one exam and its retake.
Project Pass Requirement: Students must pass project 1 functionality, project 1 design, and project 2 functionality BEFORE the withdraw deadline. The cutoff for this requirement is October 29, 2020 and the withdraw deadline is October 30, 2020 for the Fall 2020 semester.
Failure to meet 1 or more of the following requirements will cap your letter grade for this course to C– maximum, regardless of whether you have a higher letter grade in Canvas.
If you are concerned about not meeting one or more of these requirements by the withdraw deadline, you are encouraged to consult with the instructor. Your best option may be to withdraw from the class. Note, however, that a W (withdraw) counts as an attempt and CS majors and minors have restrictions on how many times they may attempt CS courses.
Meeting the pass requirements does not guarantee a passing grade. See the Grade Breakdown section below for how the final grade will be calculated.
If you are meeting the pass requirements, then your final letter grade for this class will be calculated as follows:
The assignments within each category are not necessarily equally weighted. For example, some participation assignments are worth more points than others.
Each of these categories are described more below.
You must attend and participate in at least one synchronous interaction per week. The options are:
Lecture: You should ideally attend and participate in the synchronous lecture via Zoom every Thursday. This includes participating in Zoom polls and breakout rooms.
Alternatives: You may alternatively attend lab or office hours with the instructor or teacher assistants. This must be a meaningful interaction, such as asking a question or having a discussion.
Attending a code review appointment with the instructor does not count towards the weekly attendance requirement.
Misrepresenting your attendance or participation is a violation of academic integrity. See the Cheating Policy for possible consequences.
This includes pass/fail assignments for completing surveys and discussions on Piazza, participating in exercises during lecture or lab, and participating in CS-sponsored events.
Short quizzes are assigned throughout the week, sometimes at the start of class. You will be given an opportunity to retake those quizzes until the deadline. Quizzes will be conducted on Canvas.
There will be two exams. The exams are not comprehensive. Each exam will have a retake opportunity. The exam score will be the average of the original and retake attempts. See Important Dates for the exact exam and exam retake dates. You must receive an average C letter grade or higher on at least one exam (including the retake). See the Pass Requirements for more.
Instead of a final exam, students will have a final project graded during finals week.
Homework programming assignments are assigned on a semi-weekly basis, and usually due the following week. Students may work on these assignments during their lab session, allowing them to get immediate help from the teacher assistants.
Partial grades are not given for homework assignments; students must pass 100% of the provided tests to earn credit. If all of those tests pass before the deadline, the student will earn a 100% on that homework assignment.
Programming projects place an emphasis on code quality—it is not enough to achieve correct results. Each project must pass several functionality tests and then undergo multiple rigorous code reviews checking for specific criteria, such as proper encapsulation and generalization, efficiency, and maintainability.
We use a mastery learning approach with projects: students must perfect the current project before moving on to the next project. The final project grade will depend on when and how many projects are completed.
Each project grade is split into two components: functionality (evaluated with automated software tests) and design (evaluated with one-on-one code reviews). The project functionality must be passed before the code review may be passed, students must pass code review for each project sequentially, and may only have at most one review appointment per week.
The functionality grade depends on when the project passes the tests. Projects that pass the functionality tests by the deadline will receive a 100%. Otherwise, there will be a –10% late penalty for each week the project is late past the deadline up to a maximum –30% deduction.
The design grade depends on when the project undergoes its first code review. Projects that have at least one code review by the deadline will receive a 100%. Otherwise, there will be a –10% late penalty for each week the first code review is late past the deadline up to a maximum –30% deduction. Abuse of the code review process may also result in deductions. For example, failing to fix all of the issues from a previous code review may result in a –5% to –10% deduction.
You must pass project 1 functionality, project 1 design, and project 2 functionality BEFORE the withdraw deadline. See the Pass Requirements for details.
The following is the grading scale mapping percentage to letter grade and GPA for this course:
|97% ≤||A+||< 100%||4.0|
|94% ≤||A||< 97%||4.0|
|90% ≤||A–||< 94%||3.7|
|87% ≤||B+||< 90%||3.3|
|84% ≤||B||< 87%||3.0|
|80% ≤||B–||< 84%||2.7|
|77% ≤||C+||< 70%||2.3|
|74% ≤||C||< 77%||2.0|
|70% ≤||C–||< 74%||1.7|
|67% ≤||D+||< 70%||1.3|
|64% ≤||D||< 67%||1.0|
|60% ≤||D–||< 64%||0.7|
|0% ≤||F||< 60%||0.0|
Non-passing grades for undergraduate CS majors and minors are highlighted in red text. See the Undergraduate Student Regulations for more about letter grades and GPA for undergraduate students.
At the end of the semester, various awards will be given to students. While these awards are informal and do not impact your final grade, they do provide a way for students to differentiate themselves on resumes. Example awards include: top student askers and answerers on Piazza, and more.
This section includes miscellaneous policies specific to this course, including communication, attendance, credit hours, cheating, and more. These policies are in addition to the standard USF policies included later.
Email will NOT be used for communication in this course.
Instead, please see how best to communicate depending on whether you wish to communicate synchronously (live, simultaneously, in real time) or asynchronously (on your own time, without immediate responses or feedback).
The synchronous communication that would have occurred in-class will be conducted during the live lectures as follows:
Comment Box: At the start of class and during breaks, the instructor will enable a poll that allows you to enter questions and comments anonymously.
Raise Hand: Use the “Raise Hand” feature in Zoom to get the instructor’s attention. The instructor will pause and give you an opportunity to ask a question verbally or via the chat.
Meeting Chat: Use the in-meeting “Chat” feature in Zoom to ask questions or make comments. These should be posted in the “Everyone” channel (not privately). If you do not want your name to appear in the main chat, you can privately chat the TA to post the question on your behalf instead.
Office hours will also be held via Zoom. Requests will be taken on a first-come first-serve basis (i.e. no appointments). You may join individually or in groups. The instructor will create private breakout rooms to respond to questions as needed.
Most asynchronous course-related communication will be handled using Piazza—a FERPA-compliant Q&A platform that supports public, anonymous, and private posts. When making posts on Piazza, please keep the following in mind:
Search other posts first. It is possible your question has already been asked and answered in another post. There is a search feature and you can use the folders to narrow posts to a single category.
Make a public post when appropriate. You can post anonymously if you prefer. Your classmates will not be able to see your identity for anonymous posts, but instructors will still be able to see your name. If you make a private post that should be public, you will be asked to create a new public anonymous post before receiving an answer.
Do not post code on Piazza. If you have a question regarding your specific code, please commit and push your code to your GitHub repository and post a link. That ensures only those with access to your repository (instructor and teacher assistants) will see your code.
Make posts specific to solutions or grades private to the instructor and teacher assistants. This replaces directly emailing the instructor regarding the course. If you email the instructor directly, you will be asked to make a private post on Piazza before receiving an answer.
Follow the 1 hour rule. You should be stuck on a problem between 30 minutes to 1 hour before asking for help, but should immediately ask for help if stuck over 1 hour. Worst case, you figure out the answer before we are able to help. Best case, we can help you get unstuck!
Post exact details when possible. You will get a solution faster if you include as many details as possible when asking for help. This might include exact error messages, stack traces, which tests are failing and passing, console or log output, and more. If you forget, we will have to ask you for this detail which can extend how long it takes to get help.
This course also has an anonymous suggestion box where you can raise non-urgent concerns or suggestions.
Under no circumstances should you reach out to the teacher assistants via any unapproved communication channel. Instructors and teacher assistants must provide all students equal opportunity for course-related help. Using unapproved communication channels creates an unfair advantage over other students and will be treated as a violation of the Student Conduct Code.
Students are required to adhere to the University’s Student Code of Conduct. In short, students are expected to treat each other with respect at all times.
In addition, remote learning often involves a netiquette policy. Simply stated, “netiquette” is network etiquette—that is, the etiquette of cyberspace. And “etiquette” means “the forms required by good breeding or prescribed by authority to be required in social or official life.” In other words, Netiquette is a set of rules for behaving properly online .
Activities that are synchronous are those that occur live (in real-time) with everyone participating at the same time. This includes livestreamed lectures and labs on Zoom. When communicating and participating in synchronous portions of the course:
- Arrive on time and attend for the entire session.
- Listen and dialog with each other respectfully.
- Participate in live polls and surveys in a timely manner.
- Need a break? Wait until the scheduled breaks if possible. There will either be two 10 minute breaks or one 15 minute break each lecture.
It will always be OPTIONAL whether you wish to enable your audio and/or video. When enabling your audio and/or video, keep in mind the following:
- The main livestream is sometimes recorded for students unable to attend live. If you enable your audio and/or video, it is possible it will be part of the password- protected recording.
- Consider enabling your audio and video during small group breakout rooms or when asking a question live.
- Keep your microphone muted unless speaking.
- If you choose to enable your video, please make sure to present yourself appropriately (dressed as you would be in the classroom) and double-check your background environment (for example, clean up laundry, trash).
- Be careful what you do while your video is enabled. Everyone can see you in “Gallery View” if you enable video, even if you are not currently speaking.
Activities that are asynchronous are those that occur outside of class time, usually individually on your own. This includes watching a pre-recorded lecture or participating in an online discussion board. When communicating and participating in asynchronous portions of the course:
- Be respectful of other participants and keep your comments constructive.
- Avoid using all caps (may be read as SHOUTING).
- Keep subject lines clear.
- Spelling and grammar do count; proofread your writing.
- Be coherent and succinct.
- Check the most recent comment/email before replying to an earlier one.
- Do not falsify information or impersonate others online.
Limit use of acronyms (eg YOLO), icons and emojis.If you want to use an acronym, icon, or emoji (or even a GIF) in this class to express yourself, please feel free to do so :) Just keep it appropriate!
See the Attendance requirement for this course. You are expected to be on-time to all live lectures and labs to minimize disruption.
Attend the section of lecture and lab for which you are registered. Keeping the class sizes balanced is important for interactive exercises. One-time exceptions on non-exam days are allowed with pre-approval.
Attendance is mandatory for all one-on-one code review appointments. You must be on-time to these appointments. If you arrive more than 5 minutes late, the appointment will be canceled. You risk a grade penalty for repeated canceled or missed appointments.
Except for projects, late submissions are not accepted.
Don’t worry—you may request an exception to this late policy in certain cases. See the Policy Exceptions section for details.
All students are expected to know and adhere to the University’s Honor Code. In short, students must never represent another person’s work as their own. Examples of honor code violations include (but are not limited to):
Copying and pasting code (especially without attribution) from the web
Having anyone other than yourself complete your work (including teacher assistants, tutors, and former students)
Working too closely with others such that your code no longer represents an individual contribution
Sharing your solutions with others (either directly or indirectly)
Keep in mind that unauthorized collaboration or discussion that results in the same or very similar work indicates that you have not placed enough independent thought into your submission and is a violation of the honor code, regardless of whether you directly copied!
Flagrant or repeat violations of the honor code will result in an F in the course, a report to the Academic Integrity Committee (AIC), and a report to the Dean. At the discretion of the instructor, a less severe penalty may be imposed for minor or first offenses. This is at the sole discretion of the instructor and any violation may result in an F in the course.
Keep in mind that there is a history of your code development on Github. Commit and push changes often to record your incremental code development.
Credit Hour Policy
All courses must comply with the Credit Hour Policy, which states:
“One unit of credit in lecture, seminar, and discussion work should approximate one hour of direct faculty instruction and a minimum of two hours of out-of-class student work per week through one 15-week semester.”
As this is a 4 credit course, students must spend a minimum of 8 hours of out-of-class work per week to earn a non-failing (D– or higher) letter grade. To earn a passing C or higher letter grade (as required for the CS major and minor), students should expect to spend closer to 10 to 15 hours per week on projects and assignments.
Think of this class like a part-time job. If you do not put in the time, you will not make it to the final project. Many students do not pass due to poor time management!
Life sometimes (often?) interferes with learning. Several exceptions to course policies will be granted automatically upon request. These exceptions are requested by making a private post on Piazza within the required timeframe. See the following sections for additional details.
You may request to have a 48 hour extension on any participation, quiz, or homework assignment. This request will be automatically granted as long as (1) the assignment is in the appropriate category, (2) the request is made within 48 hours of the assignment deadline, and (3) you have not made any previous extension requests. This extension does not cover assignments in other categories, such as exams or projects.
You may request to have your attendance waived for any lecture that does not have a scheduled exam or retake. The waiver will be automatically granted if (1) it is made within 48 hours of the missed lecture, (2) there is not an exam or retake scheduled that day, and (3) you have not made any previous attendance waiver requests.
Extra Credit Request
You may request one extra credit/makeup opportunity for assignments in the participation, homework, or project categories. You may earn up to 50% of the amount of points missed on that assignment. For example, suppose you earned 70 out of 100 points on an assignment, you can request an extra credit opportunity to make up 15 points. There is no time limit on when this request may be made.
Only one request per semester will be automatically approved; choose wisely to maximize the impact on the final grade. Extra credit requests may not be made for quizzes or exams.
Did you cross the line and violate the Academic Honesty policy? You can invoke the regret clause  to avoid the full consequences outlined in the Cheating Policy section. Instead, you will be able to resubmit the offending assignment with up a 20% to 40% point deduction depending on the severity of the violation.
You must voluntarily invoke the regret clause within 48 hours of submitting the offending assignment and attend a one-on-one appointment with the instructor to discuss the specifics of your cheating case to qualify.
You cannot retroactively invoke the regret clause. If the instructor confronts you regarding cheating after the 48 hour grace period, expect full consequences for that action. You can only invoke the regret clause once. Repeat cheating cases will immediately result in an F for the course and report to the Academic Integrity Committee.
Additional exceptions may be requested for any reason, but are more likely to be approved for verifiable exceptional circumstances. To make an additional policy exception request, please make a private post on Piazza to only the course instructor.
This section includes standard statements on University policies and resources.
Students with Disabilities
The University of San Francisco is committed to providing equal access to students with disabilities. If you are a student with a disability, or if you think you may have a disability, please contact USF Student Disability Services (SDS) at email@example.com or call (415) 422-2613 to speak with a disability specialist. All communication with SDS is private and confidential. If you are eligible for accommodations, please request that your accommodation letter be sent to me as soon as possible, as accommodations are not retroactive. Once I have been notified by SDS of your accommodations we can discuss your accommodations and ensure your access to this class or clinical setting.
All students are expected to behave in accordance with the Student Conduct Code and other University policies.
USF upholds the standards of honesty and integrity from all members of the academic community. All students are expected to know and adhere to the University’s Honor Code.
All course communications, like all other USF communications, will be sent to your USF official email address. You are therefore strongly encouraged to monitor that email account.
See the Communication Policy for this course above.
Counseling and Psychological Services (CAPS)
CAPS provides confidential, free counseling to student members of our community.