The course meets MWF at 9:30 (Sect A) and 10:30 (Sect B); the text is Objects first with JAVA by Barnes and Kolling. We will cover approximately Chapters 1 to 6, and 8 to 11. There will be assigned three hour labs held in the PC Lab in Dunn 102. Labs start the week of September 15. There will be two programming assignments. One in-class Mid-term Test will be held on October 24. The Lab Test will be held during labs on Nov. 17 and 19
Slides from Sept. 8, 2003 class.
For official detail see the Department Handbook.
Laboratory attendance is mandatory. As noted above, you must complete 8 of the 9 labs to pass the course (unless excused). Please contact Antony Golding email@example.com concerning lab absences. The Lab Test will be held during labs on Nov. 17 and 19. All laboratory solutions must conform to the CS1711 JAVA Programming Standards. Items which violate standards will be marked down at least one grade.
The assignments will be due on October 17 and November 21. All assignment solutions must conform to the CS1711 JAVA Programming Standards. Programs which violate standards will be marked down at least one grade.
For the requirements for the Assignments see ETA.
By its nature much of the work in Computer Science is done in collaborations. Indeed, in later courses in the subject you will often be assigned to work on projects in small groups. Thus, it is important that students in CS1711 have a clear idea of what is appropriate collaboration and what is cheating.
With the exception of assigned collaboration in some labs, all CS 1711 course work must be done individually. You are encouraged to discuss any CS1711 topic, including programming and lab assignments, with other students in the course but exchange of any JAVA code by any written or electronic means between CS1711 students is not acceptable. It is dishonest either to read someone else's solution or to provide a classmate with a copy of your work.
Penalties for cheating are severe and may result in a failing grade for the course. See Calendar Regulation 6.13.
Do not expect that small changes in a program (such as altering comments, changing variable names, or interchanging statements) will avoid detection. If you cannot do the work yourself, it is extremely unlikely that you will succeed in disguising someone else's work.
Cheating in any form will not be tolerated. Even the most trivial assignment is better not done than if you cheat to complete it.
Last updated: October 14, 2003.