CMSC132 (Spring 2023, Nelson's Sections 01*)
Object-Oriented Programming II
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.
Learning outcomes can be found at CMSC132 Learning Outcomes.
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
Nelson Padua-Perez, Office:
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").
|Data Structures & Abstractions with Java, 5th Edition
- Lectures and lab/discussion sessions be recorded (if this represents a problem for you contact your instructor).
- No pop quizzes.
- Lecture and lab/discussion session attendance is NOT required, however, you are responsible for
any material covered in lecture and lab/discussion session.
- You do not need to notify your instructor if you will be missing lecture or lab/discussion session, unless
graded material (e.g., exam) takes place on that particular lecture.
- 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.
- Email should be used for urgent matters and not to
address project questions, lecture material questions, etc.
- All programming assignments will be individually developed, unless specified otherwise.
Course Topics (Subject to Change)
- 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
- Programming skills
- Inheritance in Java
- Java collection framework
- Threads, synchronization
|Programming Assignments (Projects), Exercises, Lab Work
|Semester Exams (3), (14%, 16% and 16%)
It is your responsibility to submit regrade requests by a
specified deadline; no regrade requests will be processed afterwards (even
if the are grading errors). If you don't address a grading concern by the
specified deadline, we will assume you have reviewed the graded work and are
satisfied with your current grade. 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 deadline. The submit server will use 11:56 pm as the deadline,
otherwise assignments submitted exactly at 11:55 pm will be considered late.
The actual deadline for assignments is 11:55 pm. One minute late is considered
a late submission.
- 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 or all of the assignment
- 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. We cannot select a particular
submission to grade. We will grade the highest scoring submission as described
above. Keep in mind you may get a total score lower than expected if the highest
scoring submission is missing requirements a lower scoring submission satisfies.
- Closed Assignments -
All programming assignments in this course are to be written individually (unless explicitly
indicated otherwise).You may discuss assignments only with TAs, instructor or via Piazza.
- 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.
- Projects and exercises are posted by 6 pm (or earlier) on the day specified on the schedule.
Regarding Posting of Assignments' Solutions/Implementations
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.
TA Room/Office Hours
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 using any approach
(make sure your work is not accessible to others). You are required to submit your
work to the submit server often, so you have a backup copy. No extensions will be
granted if you lose your work and you had no submit server backups.
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. An oldannouncements
Piazza folder will have old announcements.
Excused Absence and Academic Accommodations
See the section titled "Attendance and Missed Assignments"
available at Course Related Policies.
See the section titled "Accessibility" available at
For Accessibility & Disability Students
If you are an ADS (https://counseling.umd.edu/ads) student (others ignore this
ADS students: you are responsible for reserving a space at ADS to take
exams (we cannot provide that support). Keep in mind ADS has deadlines
regarding by when to schedule a day/time to take exams. If your main
accommodation is extra time in exams and quizzes, you don't need to meet your instructor
(just bring any form that needs a signature to lecture).
Please read this information carefully. We take academic integrity
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.
- 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
- 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).
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.
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.
- Please read the section titled "Academic Integrity" available at
Course Related Policies
and the information available at
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.
We only use ELMS for videos.
At the end of the semester visit (www.courseevalum.umd.edu) to
complete your course evaluations.
Contact your instructor, the
, or both, if you are experiencing difficulties that affect your performance in your courses.
UMD Course related policies are available at
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 and lab/discussion session.
All course materials are copyright UMCP, Department of Computer Science
© 2023. 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.