ICS 211 Course Policies Spring 2020


  • Programming courses require good time-management skills. Please be sure to check Github and to read your UH email at least once a day.
  •  Keep your deadlines in mind. Turning assignments on time is key to succeed in this class!!!
  • If you have any questions outside of class, email the instructor right away ljmiller@hawaii.edu.
    • I will respond very quickly in most cases (except after 9 at night, those I answer in the morning).
    • Email is the fastest way to reach me.  Phone messages are checked only during my office hours.

Grade Breakdown:


Grades will be kept in the class Laulima site’s Gradebook tab.

  • You will be able to see your individual assignment scores and current overall grade.
    • I input grades as soon as I calculate them. If they’re not in the Gradebook, I haven’t finished grading yet.
  • Things to keep in mind:
    • Any skipped/never attempted quizzes, exams, or assignments will not be applied to your grade automatically by Laulima. Those zero scores will not be deducted from the Gradebook until I go in and mark them manually as zeros. This will change your grade drastically if you have missed any!
    • Extra credit is applied in a weird way in Laulima, usually I must go in and adjust it manually at the end of the semester.

Assignment feedback will be given in GitHub pull request comments.

Extra Credit:

There will be some extra credit available in certain programming assignments.

Letter Grade Distribution:


  • A: >=90.00%
  • B: 80.00 – 89.99%
  • C: 70.00 – 79.99%
  • D: 55.00 – 69.99%
  • F: <= 54.99%

You must get a B in this course for it to count towards an ICS degree and to continue in ICS programming courses.

Class Structure

We will use both Laulima and GitHub.

  • All quizzes will be done on Laulima outside of class.
  • Mid-terms and the Final will be done on Laulima.
  • All assignments will be posted and turned in via GitHub.

Programming Assignments:

  • These are 50% of your grade!
  • There are nine assignments, the amount of points vary, but each is approximately 5.5% of your grade
  • Three assignments will be group projects.
  • Assignments must always be turned in via GitHub. Assignments not submitted in GitHub will not be accepted. (Don’t worry we will practice!)
  • Please read each assignment carefully and note the deadlines. The time allotted for each assignment varies! Please beware of this!! Sometimes you may be required to work on two assignments at once (assignments may have overlapping deadlines). It is very important that you learn to deal with situations like this because that is what you are expected to do in the workplace.
  • As soon as an assignment opens, please read it thoroughly, make sure that you
    understand what is required before you begin working on it.
  • The assignments for ICS 211 are larger and more time consuming than those for
    ICS 111, make sure you budget your time wisely!
  • We will be doing code reviews in pairs and groups.
    • On the day an assignment is due for code review, you MUST have your code pushed to GitHub and a pull request made before class. It should be mostly finished!
    • I will assign each student/group a partner or group. You and your partner/group will review each other’s code and give feedback using GitHub pull requests.
    • You will have at least 1 day to write up a review and 1 day to implement improvements (11:55pm the day after review date for review; 11:55 pm the day after that for final code submission).
    • For two assignments: A1 and A5, we will have a class period dedicated to code reviews.
  • All submitted code must compile and run using the standard Java JDK 8 compiler or no credit will be given!

Late Assignments:

  • If you haven’t pushed anything to GitHub or have very little, non-working code by class time on the review date. I will not assign you a review partner. You will lose points for not doing a review and will not get review feedback.
  • Before the due date and time, assignments can be pushed to GitHub multiple times
    without deduction in points. In fact, you are encouraged to do so. The last version
    pushed to your GitHub repository develop branch will be what is graded.
  • After the final due date and time (2 days after review date), for the next 24 hours:
    • Score = points earned – (points * (hours late/24) * 0.50).
    • After 24 hours, late assignments have no value (100% deducted).
    • After 24 hours have passed, a solution to the assignment may be posted and no other submissions will be accepted.

Excused late assignments:

In the case of serious illness, emergency, or death in the family, contact the instructor as soon as possible to arrange making up missed deadlines. You need to show proof, such as a doctor’s note, obituary, etc. This is the only kind of excuse that will be allowed a time extension.


  • There will be a short quiz on Laulima after class about once a week, sometimes more or less often. It is your responsibility to complete quizzes on time! See schedule.
  • Quizzes will be available until the start time of the next class.
  • You may use posted slides, a textbook, and all other resources, but you only get one attempt at each quiz.
  • There will be 13 quizzes, each one is worth approximately 1.2% of your grade.


  • There will be one mid-term exam worth 15% of your grade and a cumulative final worth 20% of your grade.
  • Exams will be some multiple choice, true/false, fill-in, and reading/writing of code.
  • All exams will be done in class on Laulima.
  • If you submit proof of completion of the CES course evaluation at the end of the semester you will be allowed to do the Final Exam on Laulima at a time you choose.

Academic Honesty Policy Summary:

  • Students are required to complete and submit their own work. For the most part, sharing files, duplicating code, using another students work, copying, plagiarism, or other such acts are not allowed and are subject to penalties including a grade of ”F” for the course.
  • Sometimes we will share code, or you will use some provided code. In this case, citing the code’s author in your comments is required or it is considered plagiarism.
  • All assignment submissions will be sent to Stanford University’s MOSS system to check for similarities.
  • If you have concerns, please discuss them with your instructor. For more information, please refer to “Student Conduct Code,” Kapi‘olani Community College General Catalog.

Special Warning for Experienced Programmers:

Computer science is not just knowing how to write programs. In this class, we are
learning about how computer programming works and the concepts behind programming language constructs. In several assignments for this class, you will be asked to manually construct functionality for which there are existing Java structures and methods that automatically do the same tasks. Do not use Java API implementations unless specifically instructed to! It is important for computer scientists to understand how Java does these things, not just to be able to use them.