Office hour (328 CIWW)
Structures and Algorithms in Java, 6th edition,
to Java Programming, any edition
Java: How To Think Like a Computer Scientist,
Java, Java: Object Oriented Problem Solving,
Passing CSCI.UA.0101 with a grade of C or better.
You are expected to know and remember the material from CSCI.UA.0101 course. If you took the course a few semesters ago and/or do not remember parts of the material, start reviewing it during the summer/winter break.
If you took an equivalent of this course at a different school, you need to make sure that you are familiar with Java. We assume you know enough Java to write fairly large programs right at the beginning of the semester.
Your grade will be based on:
Grades will be determined using the following scale:
F less than 65
The grade of Incomplete is reserved for students who, for legitimate and documented reason, miss the final exam. The grade of Incomplete will not be given to student who started falling behind in class. Those students should withdraw from the class or switch to Pass/Fail option.
Recitations will not be held for the summer course. In lieu of recitations, the extra class time will be used to work on exercises related to the lecture material
During these periods you will also get some hands-on practice by participating in (usually group) activities. It may be a good idea to bring a laptop to class (although it is not a requirement since you will only need one laptop per group).
There will be two different types of assignments in this course:
Programming projects (30% of your final grade) will be given on a regular basis. In general, they will be due one-two weeks after they are assigned. They will require you to write and, often, read significant amount of code.
No programming projects can be accepted after the last day of classes.
Late and missed programming projects:
For each project you will have a 5 hour buffer window after the due date. You can submit or resubmit the project during this time without any point penalty. The late project submissions lose 30% of their value for each day they are late. If you submit the project 5-24 hours late, the maximum score is 70 (instead of 100). If you submit the project 24-48 hours late, the maximum score is 40 (instead of 100).
Broken programming projects:
If you hand in a program that does not compile or crashes when it is run, you will get a grade of zero on it. As you are working on your code, make sure that it compiles and does what you expect it to do. Test frequently, not only after you write hundreds of lines of code.
Do not hand-in homeworks (DNHI) will be given to encourage you to practice the
material that we discuss in class. The problem sets will be posted as separate homeworks or inicated in the
lecture notes. They will serve also as review questions for exams.
I use MOSS (a system for detecting software plagiarism) to make sure that the submitted assignments are not duplicates of one another. Your code has to be your own.
I follow the department's academic integrity rules.
In short, it is fine to talk to
other students about your ideas and your programs, but it is not fine to work
together on assignments or copy someone else's assignment. You cannot copy
other people's work without giving them a proper credit (and part of your
Any sharing or copying of assignments will be considered cheating. By the rules of the College of Arts and Science, I am required to report any incidents of cheating to the department.
If you have any doubt if something that you are doing qualifies as academic dishonesty, talk to me!
So what is cheating?
What is NOT cheating?
There will be a midterm and a final exam. All exams are cumulative.
Missing an exam: There will be no make-up exams. Failure to take an exam counts as a zero grade on that exam. The only exception to this rule is for students who have a legitimate serious medical or personal emergency (documented). These students need to talk to me as soon as possible (trying to excuse an exam absence three weeks after it happened will not work).
Additional topics (time permitting):
· Check the school email address on a regular basis. You can simply forward its content to another email account that you use regularly.
· Use your school's email account to send emails to professors, instructors, TA's, graders, administrators, etc. OR make sure that your email address contains your true name, not "firstname.lastname@example.org", "BabyGurl@yahoo.com" or some other cool alias.
· Start your email with proper salutations! Use the correct titles (Professor, Dr., etc.) and spell first and last names correctly. If you are on the first name basis with your instructors, use their names, not "Hey". For example: "Dear Professor Drummer" or "Dear Robert", not "Hey Bob".
· Sign your name under the body of your email, otherwise you expect people to read emails from anonymous.
· Do not write everything in upper-case letters. Do not write everything in lower-case letters.
· Make sure you included everything you wanted before hitting send. Don't send three emails one after another because you forgot something in the first one.
· Proofread the text in your email before sending it. Most of the email clients check for typos, but they cannot tell if your email makes much sense. Read it, before you send it.
This work is licensed under a Creative Commons Attribution 4.0 International License.