Data Structures and Algorithms

Policies

Academic Integrity

Academic honesty is required in all your work. Under no circumstances may you hand in work done with (or by) someone else under your own name. Your code should never be shared with anyone; you may not examine or use code belonging to someone else, nor may you let anyone else look at or make a copy of your code. This includes, but is not limited to, obtaining solutions from students who previously took the course or code that can be found online. You may not share solutions after the due date of the assignment.

Discussing ideas and approaches to problems with others on a general level is fine (in fact, we encourage you to discuss general strategies with each other), but you should never read anyone else’s code or let anyone else read your code. All code you submit must be your own with the following permissible exceptions: code distributed in class, code found in the course text book, and code worked on with an assigned partner. In these cases, you should always include detailed comments that indicates on which parts of the assignment you received help, and what your sources were.

Failure to abide by these rules constitutes academic dishonesty and will lead to a hearing of the College Judiciary Committee. According to the Faculty Handbook: “Because plagiarism is considered to be so serious a transgression, it is the opinion of the faculty that for the first offense, failure in the course and, as appropriate, suspension for a semester or deprivation of the degree in that year is suitable; for a second offense, the penalty should normally be expulsion.” Be aware that we will be routinely running plagiarism detection software on your submissions!

Please contact me if you have any questions about what is permissible in this course.

Grades

Grades in the course are weighted as follows:

Tests

Tests are given at the beginning of lab on the days posted in the Schedule. Please arrive at class promptly to ensure that you do not lose time on the test. If you are unable to attend class for a test, contact me as soon as possible to make appropriate arrangements.

Tests are conducted on paper but have a great deal to do with course material. A test may ask, for instance, what a given program will do when it is executed. Generally, you must complete the test without the use of a computer; practice what you’ve learned in class so you can be prepared!

Lab Assignments

Every student taking CS35 must also be enrolled in a corresponding lab section. Labs assignments are always due on Wednesday night (at 11:59 pm) unless an exception is noted in the schedule.

Throughout the course, there are two forms of lab assignment: individual labs and team labs. The first labs will be individual labs to ensure that everyone is familiar with the basics of C++ and the course material. Later, we will transition to labs completed in two person teams to allow you to work on larger, more interesting projects and to ensure that each student has experience working in groups to build software.

Late Policy

Lab assignments will typically be assigned in lab and will be due before midnight on Wednesday. You are strongly encouraged to start early and to attend the ninja sessions for extra practice.

You must submit your assignments electronically by pushing to your assigned git repository. You may push your assignment multiple times, and a history of previous submissions will be saved. You are encouraged to push your work regularly.

To help with cases of minor illnesses, athletic conflicts, or other short-term time limitations, all students start the course with two “late assignment days” to be used at your discretion, with no questions asked. To use your extra time, you must email your professor after you have completed the lab and pushed to your repository. You do not need to inform anyone ahead of time. When you use late time, you should still expect to work on the newly-released lab during the following lab section meeting. The professor and ninjas will always prioritize answering questions related to the current lab assignment.

Your late days will be counted at the granularity of full days and will be tracked on a per-student (NOT per-partnership) basis. That is, if you turn in an assignment five minutes after the deadline, it counts as using one day. For partnered labs, using a late day counts towards the late days for each partner. In the rare cases in which only one partner has unused late days, that partner’s late days may be used, barring a consistent pattern of abuse.

Exceptional Cases

If you feel that you need an extension on an assignment or that you are unable to attend class for two or more meetings due to a medical condition (e.g., extended illness, concussion, hospitalization) or other emergency, you must contact the dean’s office and your instructors. Faculty will coordinate with the deans to determine and provide the appropriate accommodations. Note that for illnesses, the College’s medical excuse policy, states that you must be seen and diagnosed by the Worth Health Center if you would like them to contact your class dean with corroborating medical information.

Final Exam

The format of the final exam is very much like the test, but longer. By the time you take the final, you’ll have prepared for these questions by taking the tests throughout semester. As long as you’re comfortable with those questions, you should have very little to worry about.

This semester, the final exam will be held in Science Center 101 on December 19 from 02:00 PM until 05:00 PM.

Participation

This portion of your grade is established based upon your engagement in the course. It is not graded stringently; participation is effectively a free boost to your grade as long as you:

• Attend all lecture and lab sessions
• Submit all lab assignments and tests
• Make an effort to learn the material

Students who are routinely absent from lecture or otherwise do not interact meaningfully with the course will not receive full credit here. This is an easy way to improve your grade; don’t miss out!

Academic Accommodations

If you believe you need accommodations for a disability or a chronic medical condition, please contact Student Disability Services (Parrish 113W, 123W) via e-mail at studentdisabilityservices at swarthmore.edu to arrange an appointment to discuss your needs. As appropriate, the office will issue students with documented disabilities or medical conditions a formal Accommodations Letter. Since accommodations require early planning and are not retroactive, please contact Student Disability Services as soon as possible. For details about the accommodations process, visit the Student Disability Services website. You are also welcome to contact your instructor privately to discuss your academic needs. However, all disability-related accommodations must be arranged, in advance, through Student Disability Services.

Exam Policy

Students must strictly adhere to the following policy, which applies to all exams taken in a Computer Science course at Swarthmore.

Exam takers must place all non-essential items at the front of the room (or other designated area). Unless otherwise permitted, students may not have any electronic devices or course materials in their possession during the entirety of the exam. This includes cell phones, tablets, laptops, smart watches, course notes, articles and books, among others. These items should be placed at the front of the room near the proctor. If you need to leave the room during the exam, you must obtain permission from an instructor first. Any non-permitted discussion or aide in regards to exam material will result in immediate forfeiture of the exam and a report to the College Judiciary Committee. Please discuss any concerns or accommodations with your instructor prior to starting the exam.