M/F 2:30-3:20 |
CS 1130: Transition to OO Programming Spring 2016 |
Main
About: Overview Announcements Staff Consultants Calendar Materials: Texts DrJava Terminology Lectures: In-Class Web-Based VideoNote Assessment: Grading Assignments Labs Resources: CMS Piazza (link) Piazza (about) Java API Style Guide Academic Integrity |
GradingEarning your GradeRegardless of whether you are in the lecture-based or self-study section, this course is offered S/U only. In many ways, this makes grading quite simple. Earning a SatistfactoryIn order for you to earn that S, you must successfully complete all three assignments and 4 out of the 5 labs. Therefore, to get a satisfactory, you must do the following:
If you fail to successfully complete an assignment, you will be asked to redo it until it is correct. In the case of the third assignment, this may mean continuing to work on the assignment after the end of the course's 5 week period. Earning an UnsatistfactoryThe primary way students get an unsatisfactory in this course is by not keeping up with the deadlines. All of the assignments and labs have very clear deadlines. In addition, if you are asked to revise an assignment, then we will give you a deadline with that revision request. If you fail to meet any of these deadlines, you will receive an unsatisfactory for the course. Extensions are only provided ahead of time for the most extreme circumstances. Another, unlikely, way to earn a satisfactory is to exhaust your retries on the second and third assignments. As long as you take these seriously in the first place, we find that students need at most one retry on each of these. Academic IntegrityEven though this course is graded S/U, you should respect academic integrity. Cheating may seem an easy way out, but in the long run, it really hurts you more than anyone else. You end up not learning what you should learn, and it does something to your character, to your self-image. Cheating is not worth it. Please review these notes on integrity. |