ICS 111 – Course Policies – Spring 2020


  • Programming courses require good time-management skills. Please be sure to visit Laulima 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 until about 9 at night. Emails received later than that will replied to in the morning.
    • Email is the fastest and most reliable way to reach me.  Office phone messages are checked infrequently.

Letter Grade Distribution:


A: >=90%    B: 80 – 89.99%    C:70 – 79.99%    D: 55 – 69.99%    F: <= 54.99%

You must get a B in this course to continue to ICS 211!

Class Structure

This class relies heavily on Laulima.

  • All quizzes and exams will be done on Laulima.
  • All programming assignments will be posted, turned in, and returned via Laulima.
  • Face-to-face class time will be for lectures, demonstrations, and discussion.

Grading 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 once I do it! — Don’t skip and think you’re okay!!
      • 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.

Programming Assignments:

  • These are 50% of your grade!
  •  There will be 12 programming assignments.
    • Nine assignments are worth 100 points.
    • Three assignments (9, 10, and 12) are worth 150 points.
    • Each assignment is approximately 4% of your grade.
  • Assignments must always be turned in via Laulima. Assignments not submitted in Laulima will not be accepted.
  • Please read each assignment carefully and note the deadlines.
    • Generally, there will be one programming assignment per week.
    • The due dates are variable depending on the material, but generally they will be one week after the assignment comes out.
    • Please be aware of your due dates! The time allotted for each assignment may vary.  Sometimes towards the end of the semester 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 the assignment instructions thoroughly. Make sure that you understand what is required before you begin working on it.
    • The most common reason for poor grades on programming assignments is not performing the assigned task.
  • All submitted code must compile and run in the instructor’s jGRASP, or no credit will be given!
    • For those that may have done some programming before: I do not suggest you use Eclipse. It “holds your hand” too much and will allow you to produce programs that do not compile with the official Oracle Java compiler or in JGrasp.
  • All software for this class is free and will work with all laptops and desktops, Windows, Mac, or Linux.
    • It is strongly recommended that you install all software on your own computer if you have one and that you bring your computer to class if possible.
    • All software is installed on the computers in the STEM Center in Koki’o 202 and on the laptops and desktops in Koki’o 207 and 207A.
    • The required software in NOT installed in the Library nor the Computer Labs in Kopiko (the Business Dept).
    • I may have a loaner laptop if you need one in an emergency. (It is not very nice, but will work for your assignments)
    •  You cannot program effectively on any device that runs Android or iPhone operating systems! (such as Android tablets or iPads)

Turning in Assignments:

  • All assignments will be due at 11:55pm on the due date.
  • Before the due date and time, assignments can be uploaded to Laulima multiple times without deduction in points.
  • After the due date and time:
    • 1 – 24 hours late, up to 50% deducted depending on how late.
      • Score = points earned – (points * (hours late/24) * 0.50).
  • After 24 hours no submissions will be accepted.
  • The last thing submitted will be what is graded. If you turn in something before the deadline and then resubmit after, you will have points deducted for lateness!

Excused late assignments:

  • In the case of serious illness, emergency, or death in the family, contact the instructor as soon as possible. You need to show proof, such as a doctor’s note, obituary, etc. Excused late assignments may be allowed a time extension or may be excluded from your grade depending on circumstances.

Extra Credit:

  • There will be some extra-credit opportunities in certain programming assignments and from doing practice exercises on CodingBat.com (I will show you how in a few weeks).


  • Up until the first exam there will be a short quiz on Laulima after most class lectures.
  • After the first exam, there are only practice exams and two quizzes at the end of the semester.
  • Quizzes will open at the end of class and close at the start time of the next class.
  • There will be 11 quizzes, each worth approximately 1% of your grade.
  • There is also 3 practice exam review quizzes worth 0 points. These are just for you to practice on.


  • There will be two mid-term exams and a cumulative final
  • Exams will be done in class on Laulima.
  • Exams will be made up of multiple choice, true/false, and fill-in questions; and reading of code.
  • 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 outside of class at a time you choose.

Academic Honesty Policy

  • Students are required to complete and submit their own work. Sharing files, duplicating code, using another students work, copying, plagiarism, or other such acts will not be tolerated and are subject to penalties including a grade of ”F” for the course.
    • First warning: all students involved will split the credit (two get 1/2, three get 1/3, etc.)
    • Second warning: 0 credit.
    • Third warning: F for the course.
  • You may work together to figure out how to do assignments, but everyone must write their own code!

Do not copy/paste another student’s code! I WILL be able to tell.

  • All assignment submissions for ICS 111 will be sent to Stanford University’s MOSS system to check for similarities.
  • If you have your program working, do not loan your code to a classmate who asks help!  At least once a semester, I see an instance where the classmate just turns in what was given to them.

Do not loan out your code! You will get PENALIZED TOO!

  • If you are stuck, you are allowed to look up examples on the Internet, but you MUST cite anything you use directly.
  •  Points (up to all for the assignment) will be deducted for non-cited code from the Internet at the instructor’s discretion.
  • If you have concerns, please discuss them with your instructor.  For more information, please refer to the “Student Conduct Code” in the Kapi‘olani Community College General Catalog.

Special Warning for Experienced Programmers:

  • Computer science is not just knowing how to write programs in Java. 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 API constructs that perform the same tasks.
  •  Do not use the Java version unless specifically instructed to! Using Java API constructs that are not assigned is considered to be an incorrect solution and will result in point deductions.
  • It is important for computer scientists to understand how Java does those things, not just to be able to use them.