CSCI 180/181 Computer Science II and Lab

Class: MWF 10:30-11:20, Location: Alter 223
Lab: W 2:30-4:20, Location: Alter 223

Instructor: Liz Johnson
Office: Hinkle 133
Phone: 745-3667 (has voice mail also)
Email: johnsone@xavier.edu
Office Hours: MWF 11:30-12:25, Th 11-12 and by appt
Textbook: Objects First with Java - Barnes and Kolling - third edition
Home Page: http://cerebro.xu.edu/csci180/08s/index.html

Course Objectives (thanks to Gary L.)

The goal of CSCI II is to help students develop problem-solving skills and express those skills in reasonably efficient, well-structured computer programs automating the solutions to problems. At the conclusion of the course it is our objective that you will be able to:

• read and analyze text, including: explaining code; using documentation to determine what code does; analyzing problem descriptions to determine the tasks necessary for solution.
• design solutions to problems, implement them in Java, document the solution at a level that beginning programmers would understand your solution, and develop test cases to provide evidence your solution is correct.
• conduct independent explorations into the course material, including development of plans for exploring possible solutions and acting independently on that plan.
• identify possible extensions to problems you work on, exploratory questions about the topics in the course, and multiple methods for solutions.

Grading

Grades on all assigned work and exams will be based on correctness, clarity and style; presentation counts. Your grade will be based on 4 components:

• 25% Exams (Midterm=10%, Cumulative Final Exam=15%)
• 40% Projects
• 10% Homework
• 25% Labs

The Department of Mathematics and Computer Science has adopted a grading standard, which will be followed in this course.

Academic Integrity

The work you submit must be your own. As with many courses, some discussion of assignments is permitted, but be sure what you turn in is truly your work. Because insights in this course will occur frequently in discussions, you are permitted to discuss the assignments with others. However, you should hold these discussions away from the computer and any written artifacts from the discussion must be discarded. Between the discussion and your return to the computer, you should do something mindless (like take a walk, draw a picture of a cat, organize your bookbag, etc.) for at least a half hour so that your understanding of the discussion is all that informs your work.

Occasionally, you may have a stubborn bug that would benefit from a look by another set of eyes. In that case, you may show your code to someone else, but only you may touch the keyboard or mouse to modify your code. Never type anything you do not understand. You may be asked to explain your code -- if you cannot, you will receive a 0 on the assignment. You should never show your working code to someone else who is having problems with his/her code.

Exception: In cases where you have been explicitly instructed by me to work with someone else on a specific assignment, you are permitted to work as if you and that partner are the same person in terms of the discussion above.

Late Policy

Due dates/times for labs and projects will be announced when the assignment is made. Late work will not be accepted; however, partially complete, on-time assignments will be given some credit so you should always turn in something by the deadline.

Extensions may be granted on a case-by-case basis in extraordinary circumstances. You must contact me at least 24 hours before the deadline to discuss this option. The granting of an extension is never automatic and, unless indicated by the instructor, only applies to the requestor.