CMSC132 (Spring 2022, Pedram/Nelson's Sections 01*, 04*)
Object-Oriented Programming II

Syllabus

Object-Oriented Programming II covers the design, building, testing, and debugging of medium-size software systems. Students will learn object-oriented methodology, algorithms, and data structures, to create effective and efficient problem solutions. All programming will be done in Java.

Prerequisite → Minimum grade of C- in CMSC131; or must have earned a score of 5 on the A Java AP exam; or must have earned a satisfactory score on the departmental placement exam. In addition, a minimum grade of C- in MATH140 (Calculus I).

Credits → 4

Pedram Sadeghian, Office: IRB 2214
Nelson Padua-Perez, Office: IRB 2210

No required textbook. Information about a recommended textbook by Carrano and Henry, that you do not need to buy to be successful in the course, can be found below. Some online textbooks you could use can be found at Introduction to Programming Using Java, Eighth Edition and Think Java 2e (look for "Download Think Java in PDF").

• Lectures and labs will be recorded (if this represents a problem for you contact your instructor).
• Quizzes and exams will be in lecture not in lab/discussion session.
• Quizzes will be announced (no pop quizzes).
• Lecture or lab attendance is not required, but you are responsible for material presented in lecture and lab.
• You do not need to notify your instructor if you will be missing lecture or lab, unless a graded material (e.g., quiz) will take place.
• You must attend the lecture and discussion session you are registered in.
• We may have a limited number of online office hours in addition to on-campus office hours.
• Students are expected to abide by the university health guidelines (e.g., masks in lecture/lab, etc.)
• Email should be used for urgent matters and not to address project questions, lecture material questions, etc.
• The above format will be updated in case the class moves to an online format.

• Object-oriented software development
  • Software life cycle
  • Requirements & specifications
  • Designing classes
  • Testing & code coverage
  • Design patterns
• Algorithms & data structures
  • Asymptotic efficiency
  • Lists, stacks, queues
  • Trees, heaps
  • Sets, maps, graphs
  • Recursion
• Programming skills
  • Inheritance in Java
  • Java collection framework
  • Threads, synchronization
  • Exceptions

It is your responsibility to submit regrade requests by a specified deadline; no regrade requests will be processed afterwards. Deadlines to address any grading concerns will be available at Grading Concerns.

• Deadlines - All assignments are due at 11:55 pm and you have until 11:55 pm of the next day to submit your work with a 12% penalty. You will not receive any credit for a submission after the late date, except the Good Faith Attempt credit (additional information below).
• Submit Server - You need to use the submit server to submit you work. We will not accept work submitted otherwise (e.g., email, etc.). You need to make sure that your assignment solution works in the submit server, otherwise you may lose most of the credit.
• Which Assignments Gets Graded - For programming assignments the one with public/release/secret tests that scores the highest in the submit server after a late penalty (if any) has been applied. We only use public/release/secret tests scores to select the submission to grade. Other assignment requirements (e.g., style, methods you must implement, allowed classes, etc.) are not considered. We will evaluate those requirements on the selected submission.
• Good Faith Attempt (GFA) - You must satisfy a minimum set of requirements (Good Faith Attempt (GFA)) for most class work (usually programming assignments), otherwise you will fail the course (automatic grade of F). The Good Faith Attempt guarantees you have the skills necessary for upper-level courses. A good faith attempt for an assignment is worth 0.5 of your class grade. GFAs are not due at the end of the semester (a common misunderstanding). GFAs requirements and deadline are available at at CMSC132 GFAs. Additional information about good faith attempts is available at GFA Information.
• Closed Assignments - All programming assignments in this course are to be written individually (unless explicitly indicated otherwise).
• No Pop Quizzes/Pop Lab Work - There are no pop quizzes nor pop lab exercises. We will announce in advance (at least one day) if there is any work you need to submit for a grade.

• Posting of any assignment solution (even after the course is over) in a publicly available online location (e.g., github, Chegg) is prohibited under the Code of Academic Integrity (facilitation of academic dishonesty). Any student responsible for publicly posting assignments' solutions will be reported to the Office of Student Conduct and risks the sanction of an "XF" in the course.
• Posting of your assignments in a private repository where only selected people (e.g., potential employers) have access is OK.

Office hours get extremely busy the day before an assignment deadline and getting help is not guaranteed. Please start your assignments early so you can address any problems during office hours.

You are responsible for creating backups of your work. Use the submit server as a backup tool by submitting often.

We will be using (Piazza) for class communication. You will not be able to register to Piazza yourself. Your instructor will register you using the email address you have in the school system. Posting of any kind of code in Piazza is not allowed.

You are responsible for checking announcements (at least twice a day) we post in the announcements Piazza folder.

See the section titled "Attendance and Missed Assignments" available at Course Related Policies.

See the section titled "Accessibility" available at Course Related Policies.

Please read this information carefully. We take academic integrity matters seriously.

1. Academic dishonesty includes not only cheating, fabrication, and plagiarism, but also includes helping other students commit acts of academic dishonesty by allowing them to obtain copies of your work. All submitted work must be your own. Cases of academic dishonesty will be pursued to the fullest extent possible as stipulated by the Office of Student Conduct.
2. Situations that often lead to academic integrity violations:
   • A student's friend/roommate shares an assignment's code. Once you provide your code to another student, you are a facilitator, even if you indicate to the student "not to copy-paste" any of it. Actually we had a case in which a student CS degree was revoked for this reason.
   • Students use online resources (github, Chegg, etc.) to find assignments' solutions. The solutions are found by several students and all will be involved in an academic case.
   • Students assume we don't have tools that check for similarities among all students' submissions.
   • Students get desperate and don't want a 0 in the assignment.
   • Students are not aware of the expectations regarding academic integrity.
   • Students assume we don't take academic integrity matters seriously.
   • You should only receive assistance from instructors/TAs. We have seen cases in which the use of tutors have led to academic integrity violations (e.g., tutors looked for assignment's solutions online).
3. The Office of Student Conduct is responsible for handling academic integrity matters. After a report is submitted by an instructor, the case is evaluated by the office and it could result in an XF grade, degree revocation, or dismissal from the university.
4. One of the most negative consequences of academic integrity violations is the emotional burden an academic integrity case has on a student. We have seen students extremely distraught as a result of an academic integrity violation. In many cases students chances for recommendations, TA positions, and other opportunities are negatively affected.
5. Please read the section titled "Academic Integrity" available at Course Related Policies and the information available at Academic Integrity

If you or your parents have any class concerns, feel free to contact the instructor. If an issue arises with the instructor, report it using the form available at https://www.cs.umd.edu/classconcern.

• At the end of the semester visit (www.courseevalum.umd.edu) to complete your course evaluations.
• Contact your instructor, the Counseling Center, or both, if you are experiencing difficulties that affect your performance in your courses.
• UMD Course related policies are available at http://www.ugst.umd.edu/courserelatedpolicies.html.
• We plan to record lectures and lab/discussion sessions, but technical problems may prevent us from creating a recording. You are still responsible for any material covered in lecture/lab.

All course materials are copyright UMCP, Department of Computer Science © 2022. All rights reserved. Students are permitted to use course materials for their own personal use only. Course materials may not be distributed publicly or provided to others (excepting other students in the course), in any way or format.

Web Accessibility