Introduction
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.
Course Coordinator
| Name | Office |
|---|---|
| James M. Purtilo | AVW 4437 |
| Nelson Padua-Perez | AVW 1203 |
For office hours and other contact information, visit the staff link.
Textbooks
There are no required textbooks. The recommended textbooks are:
| Title | Authors | ISBN |
|---|---|---|
| Objects, Abstraction, Data Structures and Design Using Java Version 5.0 | Elliot Koffman/Paul Wolfgang | 0-471-69264-6 |
| Java Precisely, Second Edition | Peter Sestoft | 0-262-69325-9 |
Projects
There will be projects assigned almost every week. Some are considered "closed" assignments which you must complete by yourself and others are considered "open" assignments where collaboration is permitted. (More information about the open policy will be provided in class and can be found in the (Policy Regarding Open/Closed Assignments) There will also be one midterm, a final exam, homework exercises, and (announced) quizzes.
Topics
- 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
- Recursion
- Programming skills
- Java collection framework
- Threads, synchronization
- Exceptions
Class Announcements
Class announcements are located at Class Announcements. You should check announcements often (at least once every day).
Grading
All assignments are due at 6pm on the specified day in the assignment description. If for some reason you have not been able to finish your assignment by this deadline, then you have until 9am of the next day to submit your project with a 20% penalty. No assignments will be accepted after 9am. Assignments are to be submitted electronically according to instructions given with the assignments. Exceptional circumstances will be considered only if discussed with the instructor before the assignment is due.
Which Programming Assignment Gets Graded
Your grade for a programming assignment will be based on the greater value of two scores: (1) The score on the very last compilable submission prior to the deadline; (2) The score minus 20% on the very last compilable submission prior to the late deadline.
About Graded Material
Once we have graded any class material (e.g., exams, projects, etc.) we will post an announcement/send notification that the specific assignment has been graded, and the 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.
Final grades will be computed according the following weights:
| 30% | Projects(8) |
| 14% | Lab Exercises |
| 14% | Quizzes (Some Pop Quizzes) |
| 20% | Midterm |
| 22% | Final Exam |
About Quizzes
Quizzes will be in lab or lecture and some could be unannounced pop quizzes.
Use of Laptops/Phones/Electronic Devices
- Please, bring your laptop to your discussion (lab) session. If you don't have one we will pair you up with a classmate.
- The use of laptops, phones or any other electronic devices is not permitted in lecture. We ask that you turn off your phones or set them to vibrate mode. Texting is not allowed in class.
Academic Honesty
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. You are allowed to use the Web for reference purposes, but you may not copy code from any website or any other source. 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. Without exception every case of suspected academic dishonesty will be referred to the Office. If the student is found to be responsible of academic dishonesty, the typical sanction results in a special grade "XF", indicating that the course was failed due to academic dishonesty. More serious instances can result in expulsion from the university. If you have any doubt as to whether an act of yours might constitute academic dishonesty, please contact your TA or the course coordinator.
The University of Maryland, College Park has a nationally recognized Code of Academic Integrity, administered by the Student Honor Council. This code sets standards for academic integrity at Maryland for all undergraduate and graduate students. As a student you are responsible for upholding these standards for this course. 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 visit http://www.shc.umd.edu
To further exhibit your commitment to academic integrity, remember to sign the Honor Pledge on all examinations and assignments: "I pledge on my honor that I have not given or received any unauthorized assistance on this examination (assignment)."
Excused Absence and Academic Accommodations
Any student who needs to be excused for an absence from a single lecture, recitation, or lab due to a medically necessitated absence shall:
- Make a reasonable attempt to inform the instructor of his/her illness prior to the class.
- Upon returning to the class, present their instructor with a self-signed note attesting to the date of their illness. Each note must contain an acknowledgment by the student that the information provided is true and correct. Providing false information to University officials is prohibited under Part 9(h) of the Code of Student Conduct (V-1.00(B) University of Maryland Code of Student Conduct) and may result in disciplinary action.
- This self-documentation may not be used for the Major Scheduled Grading Events as defined below and it may only be used for only 1 class meeting during the semester.
Any student who needs to be excused for a prolonged absence (2 or more consecutive class meetings) or for a Major Scheduled Grading Event, must provide written documentation of the illness from the Health Center or from an outside health care provider. This documentation must verify dates of treatment and indicate the timeframe that the student was unable to meet academic responsibilities. No diagnostic information shall be given. The Major Scheduled Grading Events for this course include midterm(s) and final exam.
It is also the student's responsibility to inform the instructor of any intended absences from exams for religious observances in advance. Notice should be provided as soon as possible but no later than the Monday prior to the exam for both the midterm and the final.
Any student eligible for and requesting reasonable academic accommodations due to a disability is requested to provide, to the instructor in office hours, a letter of accommodation from the Office of Disability Support Services within the first two weeks of the semester.
Evaluation System (CourseEvalUM)
Your participation in the evaluation of courses through CourseEvalUM is a responsibility you hold as a student member of our academic community. Your feedback is confidential and important to the improvement of teaching and learning at the University as well as to the tenure and promotion process. Please go directly to the website (www.courseevalum.umd.edu) to complete your evaluations. By completing all of your evaluations each semester, you will have the privilege of accessing online, at Testudo, the evaluation reports for the thousands of courses for which 70% or more students submitted their evaluations.
You can find more information, including periodic updates, at the IRPA
course evaluation web site
https://www.irpa.umd.edu/Assessment/CourseEval/fac_faq.shtml