CMSC132 (Fall 2018) - 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
|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
||Quizzes, Exercises, Lab Work
||Semester Exams (3), (8%, 11% and 11%)
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 -
Your grade for an project will be based on the submission with
the highest score after the late penalty (if any) has been applied.
- 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 Room/Office Hours
Office hours get extremely busy the day before a project deadline.
Therefore do not wait to start your projects. Regarding office
hours and the TA Room:
Once you have been helped by a TA please leave the TA room. We
have a large number of students in all of our classes and the TA
room is really crowded.
If there is a line of students waiting, a TA should spent at most
5 minutes with a student. Please remind TAs about this rule.
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
Excused Absence and Academic Accommodations
See the section titled "Attendance, Absences, or Missed Assignments"
available at Course Related Policies.
Disability Support Accommodations
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.
It is very important for you to be aware of the consequences of cheating,
fabrication, facilitation, and plagiarism. For more information on
the Code of Academic Integrity or the Student Honor Council, please
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.
Hiring any online service to complete an assignment for you.
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 "Code of Student Conduct" available at
Course Related Policies.
By October 15, 2018, all UMD students must use multi-factor
authentication to log into all university resources that use the
Central Authentication System (CAS). In this course the grade server
relies on CAS. Make sure you enroll before October 15. Visit
https://it.umd.edu/mfa for additional information.
Please bring your laptop to your discussion (lab) session and
to lecture. If you don't have a laptop, we will pair you up with
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.
If you are experiencing difficulties in keeping up with the academic
demands of this course, you may contact the
Service located at 2202 Shoemaker Building.
UMD Course related policies can be found at
All course materials are copyright UMCP, Department of Computer Science
© 2018. 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.