COP 2805C
Java Programming II

Weeks of Programming

Can Save You

Hours of Planning

Reported by: "Anne Applin" <anne.applin@GMAIL.COM>

(There may be PDF versions or book rentals available, to save money.  There may also be a possibly cheaper international edition, but despite vendors' claims, the content is not always exactly the same.)

HCC bookstore online

Instructional Methodology:  The class format will be lecture and discussion; class participation is strongly encouraged.  In addition, there will be numerous examples and some in-class group programming exercises (model solutions to these and all projects will be provided.)  Assignments will be mostly group programming projects.  While some time will be provided in class, most assignments will require several hours per week outside of class.

Students are expected to prepare for each class by completing all reading assignments, reviewing examples and model solutions provided, and practicing programming outside of class.  (This is important — you can't learn a skill such as Java programming only by attending class and reading a book.  You must practice, practice, practice, several hours each week!  If you won't have enough time available, consider auditing the course.)

1. Identify professional ethics, intellectual property rights, and software licensing issues, and understand the responsibilities these incur for software developers
2. Understand and use modern version control systems and software repositories, including Git and GitHub.com
3. Understand how to digitally sign applets and applications, and the related security concepts
4. Identify deployment and operational issues of software, and the use of Java WebStart
5. Create and use jar files
6. Understand and use advanced Java features including exceptions, reflection, annotations, weak references, enums, and autoboxing and unboxing
7. Work with files and I/O, and Java preferences, and understand the concepts of persistent data (CRUD)
8. Understand and select appropriate collection types and implementations generic collections, and perform common operations on collections
9. Understand how to construct internationalized applications, and how to use Unicode text safely (using standard normalization, sanitation, and validation techniques)
10. Understand and build applications using advanced object-oriented programming concepts (such as design patterns and basic UML)
11. Conduct and participate in code review activities, in a professional manner
12. Understanding testing (especially unit testing), assertions, tracing, and logging
13. Understand multi-threading concepts and build multi-threaded applets and applications
14. Understand how to use databases from a Java program
15. Identify the concepts and components of Java EE (enterprise) applications

Grading scale:  A=90-100,   B=80-89,   C=70-79,   D=65-69,   F=0-64
(Or you can elect to “audit” the class during the add/drop period.)

• No makeup exams will be offered without the prior approval of the instructor.  If a make-up exam is offered, you can take the exam in my office during my regular office hours, or from the Dale Mabry Testing Center.  (Check for their hours of operation, and make sure to give yourself sufficient time to complete an exam.  You will need to make an appointment to schedule a make-up exam.)
• Exams will be open book and open note, (mostly) multiple choice exams.  While the exams are non-cumulative, each does build upon knowledge acquired earlier.  Exams are based mostly upon material presented in class however some questions may be from assigned readings (the textbook and online resources).
• Exams will only cover material discussed in class or assigned as reading, before the exam.  Should the class fall behind the course schedule, some topics shown on the syllabus due for an earlier exam will be tested on the following exam instead.
• The schedule for the final week of the term may cause a conflict between our class schedule and another class's final exam.  It is up to you to determine if you will have a conflict, and to bring it to the attention of your instructor, so that appropriate arrangements can be made.
• Regular attendance is imperative for the successful completion of this class.  The textbook and online resources should be considered as required course supplements; in other words, the course is not based on the text.  Furthermore, not all the material present in the class lecture notes will be covered on exams.
If you must miss a class, let your instructor know in advance and the class will be recorded, so you can watch it later.
• All phones, pagers, and beepers must be turned off during class time, except with prior permission of the instructor.  No food or drink is permitted in HCC classrooms.
• Attendance will be taken within 5 minutes of the start of class; after 4 unexcused absences and/or lateness, the student will lose 2 points off the final grade for each additional occurrence.
• If you miss a class, you are still responsible for the material covered in that class.  All students should exchange contact information (name, email address, phone number) with at least one other student in the class.  If you must miss a class, you should then contact another student and request they take class notes for you.  (Note, Hawknet has Hawkmail365 email for HCC students.)
• Credit for class participation includes attendance, preparedness, and adding to class discussions by asking questions and participating in discussions.  Playing computer games, surfing the Internet, or working on assignments for this or other classes during class time will lose you credit.
• Additional time outside of class will be required.  For typical students an average of between 6 and 10 hours each week outside of class are required for preparation, practice, projects, and homework assignments.
• Students are expected to prepare for each class by completing all reading assignments, reviewing examples and model solutions provided, and practicing outside of class.  This is important — you can't learn a skill such as Java programming only by attending class and reading books.  You must practice several hours a few days each week!  If you won't have enough time available, consider auditing the course.
• Students are expected to check the class website regularly.  Any syllabus changes, class cancellations, or changes to project assignments and homework assignments are announced in class and in Canvas.
• A student shall not, without my express authorization, make or receive any recording, including but not limited to audio and video recordings, of any class, cocurricular meeting, organizational meeting, or meeting with me.  Further, you do not have my permission to post on the web or otherwise distribute my class lectures and other course materials.  (You can distribute freely any materials I make publicly available from the HCC (or the wpollock.com) website, without asking permission, provided you give me credit for the work and don't alter it.  Any other use will require expressly given permission.)
• Working together on individual assignments is considered as cheating!  Turning in someone else's work without giving them credit is also considered cheating (plagiarism).  Cheating will result in an automatic F (zero) for the project for all parties.  Also, you can only earn credit for your own work and not someone else's, even if you do cite your sources.  Note that most projects in this class are group projects, where each member of a small group works together on a project.  It is also okay to ask a fellow student for class notes (in the event you miss a class) or for help in understanding the text or material given to the class (e.g., examples on the class website).  You are encouraged to study together as well.
• Because you can learn a lot from your peers, both in the class and in the broader community, I encourage collaboration with both.  However, do not mistake this as a license to cheat.  It is one thing to learn from and with your peers; it is another to pass their work off as your own.  With respect to writing code for this class:
  • You are expected to document any collaboration that takes place.
  • Absolutely no electronic transfer (or other copying) of code between students is permitted.
  • Any code that you “find” on the Internet must be cited, with an active link to that code.
  • While you are encouraged to engage in conversations in online forums, under no circumstances are you permitted to solicit other individuals to complete your work for you.  (So, no posting programming assignments or homework questions and asking for answers.)
  • Ultimately, YOU are responsible for all aspects of your submissions.  Failure to be able to explain and defend your submission will be treated as a violation of academic integrity.
• You must abide by the HCC Acceptable Use Policy (AUP) for computers and services.  In particular, you must not run network scanners, or attempt to obtain administrator (“root”) privileges or otherwise disrupt HCC computers and services.
• You must follow the academic honesty policy and the student code of conduct for HCC.  A second cheating offense will result in an “F” for the course, and your name will be turned over to the dean for further handling.  I take these matters very seriously.  You have been warned!
• Every effort will be made to stick to the weekly schedule for our course.  However it may happen that we will fall behind the schedule at some point.  If so, no topics will be skipped.  Instead we will attempt to catch up over the following weeks.
• Please be aware that if we fall behind on the weekly schedule, the topics discussed may not match what shows on the syllabus.  The weekly schedule may (but probably won't be) updated in this case.
• In case we do fall behind, projects and exams will not be automatically postponed.  Should your instructor deem it necessary, projects and exams may be rescheduled; this will be announced in class.
• Communications Policy:  Communication between the instructor and student is a critical success factor in any course.  You are to use the Canvas message ("Inbox") function to send messages to the instructor.  A response to your email will be received within two working days.  Make sure all your communications in this course are polite; be as clear as you can since online communication makes it difficult to tell your tone or facial expression.

  HCC policy is that grades can only be discussed in person during office hours, or via email only if you use your assigned HCC HawkNet (Hawkmail365) email account.

  No appointment is necessary to see me during my scheduled, on-campus office hours.  You can just “walk-in”.  You can make appointments for other times as long as I'm available.  (Occasionally my office hours will be canceled on short (or no) notice, for example if the dean calls me for a meeting.  Before driving out to campus just for my office hours, you should contact me the day before to make sure I still plan to be there.)

  Students wanting help from their instructor during on-line office hours should first send an email.  A follow up can be arranged during office hours for a Microsoft Teams meeting, a Zoom meeting, or by other means.  During on-line office hours, expect quick email responses.

• Late Policies:  Late assignments (homework assignments, projects, or exams) generally will not be accepted.  An assignment is late if not turned in by the date and time shown in Canvas.

  Late assignments will be accepted late only if you obtain the instructor's permission prior to the due date of the assignment, or for a documented serious medical reason.  All late assignments are subject to a late penalty of at least one letter grade (10%) regardless of the reason for the delay.

  Projects and homework assignments later than one week will receive a more severe late penalty; very late assignments without adequate excuses will receive a grade of “F” (0).  However if you have a very good reason your instructor may waive any or all of the late penalty.  (Examples of good reasons include extended illness that prevents working, being out of town for work, or military service.  Remember, documentation will be required.)

• The dangers of the Covid-19 and flu (or another contagious disease) require some changes to normal policies.  HCC is implementing the recommendations for institutions of higher learning of the CDC.  (See www.cdc.gov/h1n1flu/guidance/ for guidance from the CDC.)  You won't need documentation if you miss class due to the flu.  (But if you think you have the flu, you should see a doctor as soon as you can.)  In the unlikely event of a school closure due to the flu, some plan to make up the missed work will be made.

  If you think you are sick, stay home.  Do not come to HCC until 48 hours after your fever has broken as you are still infectious; if you have Covid-19, you must stay home for at least 10 days after your fever has broken.  Also, people are infectious to others for a day or so before they have any symptoms.  Flu is spread by touching doorknobs, computer keyboards, railings on stairs, etc., that were touched by someone with the flu.  Avoid shaking hands; use the “fist shake” (touching of fists) if you must use a physical greeting.  The most effective way to avoid catching the flu is to wash your hands frequently, especially after touching something that was touched by others.  Avoid unnecessary touching of eyes, nose and mouth.  While not as good as properly washing hands, hand sanitizers have been installed throughout the campus; use them often.

While you should work individually on the first two projects, you must work in a group of two to four students on all other projects, unless approved by your instructor.  From project #3 on, projects will be submitted to a group's designated GitHub repository for that project.  (Each group will have one official repo for each of their projects; this will be explained before project #3 is assigned.)  Each group member must do their share of the work and make individual commits.  Your grade will depend mostly on your code as shown by your commits to the project repository for your group.

Students will make their code contributions in their own branches.  (Using repositories will be covered in class, and practiced in project #2.)  All students will need to push all their commits (in their own branches) to the group's repository on GitHub.  This is required because not all student's commits will be included in the group's final submission, and I will need to see the code produced by every student.  Only group-approved commits will be merged into the master branch.  The final version of the master branch that you want graded for a project will have an appropriate “tag”.  (All this will be explained in class.)

Projects are graded on the following scale:

A = 95% (Excellent: Good design with good comments, style, and extras)
B = 85% (Good: Good design, some comments, readable style, and it works)
C = 75% (Acceptable: Project objectives are met or are close to being met)
D = 65% (Unacceptable)
E = 10-64% (Variable credit: At least you tried)
F = 0% (Didn't hand in the project)

Minor extras worth +5 points, minor omissions or poor design worth -5.

Projects are graded according to their design (25%), how well they compile and run (20%), how well your project meets the requirements specifications (20%), the coding style (15%), the amount (and quality) of your comments (10%), and your creativity in extending the project usefully or an innovative design that uses the features taught in class well (10%).

Projects are not graded when turned in.  They are graded all at once, sometime after the project deadline has passed (usually the following weekend).  Every effort will be made to grade projects within a week of the due date, or as soon thereafter as possible.  (See also submitting assignments below.)

(Be aware that some employers reportedly check on-line code repos of perspective employees.  While you should not be embarrassed by code produced when first learning, remember you do have the option at the end of the term, once your grades have been verified by you, to delete any on-line repos.  I suggest making a clone of your repos on your personal computer, first.)

Monday  2/8/2021 (Superbowl 2021 at Raymond James stadium).
(Dale Mabry Campus Closed - Classes will be delivered virtually and recorded)