CMSC132 (Fall 2021) - Object-Oriented Programming II
Object-Oriented Programming II is a
second programming course for Computer Science majors with
a focus on object-oriented programming. The goal of the course is to
develop skills such as program design and testing as well as the
implementation of programs using a graphical IDE. All programming
will be done in Java.
Prerequisite → C- or better in CMSC131
and MATH 140
Credits → 4
In-Class Mask Policy
President Pines provided clear expectations to the University about the wearing of masks for
students, faculty, and staff. Face coverings over the nose and mouth are required while you are indoors
at all times. There are no exceptions when it comes to classrooms, laboratories, and campus offices.
Students not wearing a mask will be given a warning and asked to wear one, or will be asked to leave
the room immediately. Students who have additional issues with the mask expectation after a first
warning will be referred to the Office of Student Conduct for failure to comply with a directive of
Textbook (Not Required)
|Data Structures & Abstractions with Java, 5th Edition
Course Topics (Subject to Change)
- Object-oriented software development
- Software life cycle
- Requirements & specifications
- Designing objects & classes
- Testing & code coverage
- Programming paradigms
- 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
||Semester Exams (3), (10%, 10% and 10%)
Once we have graded any class material (e.g., exams, projects, etc.)
we will post an announcement and a deadline by which you must submit
any regrade request (if necessary). It is your responsibility
to submit regrade requests by the specified deadline; no regrade
requests will be processed afterwards.
- Deadlines -
All projects are due at 11:30 pm on the specified day
in the project description. You have until 11:30 pm of
the next day to submit your project with a 12%
penalty. Notice that after the late period, you will not receive
any points for your project, even though you still need to satisfy
the good faith attempt (see information below). For example,
if a project is due on Wednesday at 11:30 pm, you have until Thursday
at 11:30 pm to submit a late project with a 12% penalty. Any submission
after Thursday 11:30 pm will receive 0 pts.
- Submit Server -
You need to use the
submit server for project
submissions. We will not accept projects submitted otherwise (e.g.,
e-mail, etc.). Notice that we use the submit server results to
compute a significant portion of your project's grade. You need to
make sure that your project works in the submit server, otherwise you
will not get any credit.
- Which Project Gets Graded -
We will grades the project submission on the submit server with
the highest score after the late penalty (if any) has been applied. Your final recorded project score is not necessairly what you see in
the grade server as TAs may make additional deductions when reviewing your code.
- Good Faith Attempt -
You must satisfy a minimum set of requirements for each project
(Good Faith Attempt) otherwise you will not pass the course (automatic
grade of F). Each project defines its own good faith attempt
criteria and a deadline to provide an implementation that satisfies
it. If you start a project on time, and look for assistance
(if required) you should have no problems satisfying the Good Faith
Attempt. The Good Faith Attempt guarantees you have the skills
necessary for upper-level courses. Notice that you will not
receive extra points for completing the good faith attempt. The
grade you obtain for a project will be based on your ontime/late
- Closed Projects -
All programming assignments in this course are to be written
individually (unless explicitly indicated otherwise). Cooperation
between students is a violation of the Code of Academic Integrity.
Regarding Posting of Project Implementations
Do not post your assignments' implementation online (e.g.,
GitHub, PasteBin) where they can be seen by others. Making your
code accessible to others can lead to academic integrity violations.
Posting of your projects in a private repository where only selected
people (e.g., potential employers) can see them is OK. Just make
sure is not a public site.
Even if the course is over, do not make your code publicly available
- We constantly monitor online sources.
TA Office Hours
Office hours get extremely busy the day before a project deadline.
Therefore do not wait to start your projects. Regarding office
Once you have been helped by a TA please allow the TA to move on to help another student. We
have a large number of students in all of our classes and we need TAs to be available to address as many questions as possible.
A TA can spend at most 8 minutes with a student if other students need help.
When you meet with a TA, please be ready to ask specific question(s). Just telling the TA that your code does not work is not a specific question. Remember, that it is ultimately YOUR responsibilty to debug your code. The TA will try to point you in the correct direction, but we can not guarantee that your issue will be fully resolved after meeting with a TA.
If you have a basic question, for example if you need clarification on the project requirement, just post in Piazza. Please allow us to reserve office hour time for students that have specific questions about the code they have written.
You need to keep backups of your projects as you develop them.
No extensions will be granted because you accidentally erased
your project. Feel free to use the submit server as a backup
tool by submitting often. You can also use tools like git, etc.
Do not post code in any online system that is accessible to
others (e.g., GitHub).
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 e-mail you have in the school
See the section titled "Attendance and Missed Assignments"
available at Course Related Policies.
See the section titled "Accessibility" available at
Note that 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. In
short, 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.
The CS Department takes academic integrity seriously. Information on how
the CS Department views and handle academic integrity matters can be
found at Academic Integrity.
The following are examples of academic integrity violations:
Hardcoding of results in a project assignment. Hardcoding
refers to attempting to make a program appear as if it works
correctly (e.g., printing expected results for a test).
Using any code available on the internet/web or any other
source. For example, using code from Sourceforge, Stack Overflow, etc.
Hiring any online service to complete an assignment for you. For example, using Chegg to complete an assignment is not allowed.
Sharing your code or your student tests with any student.
Using online forums (other than Piazza) in order to ask for
help regarding our assignments.
Additional information can be found in the sections titled
"Academic Integrity" and "Student Conduct" available at
Course Related Policies.
As you work on a project, submit your project often even if you have
not finished. We monitor submit server submissions and can provide
assistance based on submit server results.
At the end of the semester visit (www.courseevalum.umd.edu) to
complete your course evaluations.
Contact the Counseling Center if you are experiencing
difficulties that affect your performance in your courses.
UMD Course related policies can be found at
All course materials are copyright UMCP, Department of Computer Science
© 2021. 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.