CSCI 220 – Computer Programming I

Course Syllabus – Fall 2003

 

Instructor:

Dr. Bill Manaris

Office:

Room: 210 J.C. Long Building
Phone: (95)3-8159

E-mail: manaris@cs.cofc.edu

Office Hours:

Mondays 11 a.m. – noon & 1 – 3 p.m., Wednesdays 1 – 4 p.m., and by appointment.  Feel free to come in with questions and problems you may have.  I may also be available for a few minutes after class.

Course
Description:

An introduction to programming using Java.  Topics include data types, variables, assignments, control structures (selection and iteration), arrays, object-oriented analysis and design of software, classes, and the use of class libraries.

Each student must have completed MATH 111 or an equivalent or higher course, and must be enrolled in or have completed CSCI 222 (Computer Programming I Laboratory).  Students are expected to be familiar with MS Windows.

 

Textbook:

Chapman, S. J. (1999), Java for Engineers and Scientists, Prentice Hall, ISBN 0-13-919523-8.

 

References:

Sestoft, P. (2002), Java Precisely, MIT Press, ISBN 0-262-69276-7.

Lewyn, M. “Flying in Place: The FAA’s Air-Control Fiasco,” Business Week, April 26, 1993, pp. 87-90.

Gleick, J. “Little Bug, Big Bang,” The New York Times Magazine, December 1, 1996. Also at www.around.com/ariane.html .

Additional materials will be made available via handouts and the class webpage  at www.cs.cofc.edu/~manaris/fall03/cs220.html .

 

Goals:

·         To learn the fundamentals of programming, and object-oriented analysis and design.

·         To understand the fundamentals of the program development process (problem definition, requirements specification, design, implementation, testing, and maintenance).

·         To learn the fundamentals of the Java language, including class definitions, variable and object declarations, method definitions, and the major types of statements, such as assignment, selection and iteration.

·         To develop working knowledge of object-oriented programming techniques and their implementation in Java, including classes, objects, and methods.

 

Grading:

Scale: A: 90-100; B: 80-89; C: 70-79; F: <70. The grades of B+, C+, and D may be given at the professor's discretion.

Final Grade Computation: Assignments (5-7) 20%, Tests (2) 50%, Comprehensive Final Exam 25%, and Class Participation 5%.

 

Collaboration
Policy:

·         You must do your assignments alone.  You are not allowed to discuss assignments and possible solutions with any person other than the instructor, lab instructor, and department-assigned tutors. You are not allowed to look at someone else’s solution (including code in books and the Internet) or show your solution to someone else other than the instructor.  Any violation of the above rules is an honor offense.  See The Honor System of the College of Charleston and the Student Code of Conduct (www.cofc.edu/student-life/handbook/), especially sections on Cheating, Plagiarism (pp. 10-11), and Computer Use (p. 13).

·         On assignments you will be asked to identify the person(s) you received help from, if any.

·         In-class exercises, when identified as collaborative, are excluded from the above.

Course Policies:

·         Attendance at tests is mandatory.  You are expected to attend all classes.  Regardless of actual attendance, you are responsible for announcements made in class, assignment due dates, etc.

·         You are expected to do all reading assignments promptly.

·         Students are expected to participate in the educational experience through questions and invited comments/discussion.  However, you should respect your classmates right to learn (e.g., raise your hand, keep comments and discussions contained to the subject at hand, etc.); see Student Handbook section on Classroom Code of Conduct (pp. 49-50).

·         Programming assignments are to be submitted to the instructor on a floppy disk by the due date and time.  If the instructor is unavailable, they may be turned in at the CSCI department office (Long 216). 

·         Clearly label your floppy disk with your name, course number, section number, and semester.  Place your programs at the top directory using the specified filename.

·         To be eligible for partial credit, your submitted programs should compile (have no syntax errors).  Also your floppy disk should be readable on MS Windows.  Do verify both before submitting your assignment for grading.

·         24-hour blackout period: You may ask questions about an assignment up until 24-hours before it is due.

·         Upon return of graded work, you have one week to ask questions regarding your grade.

·         To receive a passing grade for the course, you must average a passing grade (70% or higher) on each of the following: assignments, tests, and final exam.

·         You have four “late” days for the whole semester to use when submitting your assignments.  Once you use up these days, no late assignments will be accepted. However, partial solutions submitted on time will be graded.

·         If at the end of the semester you still have all 4 “late” days unused and have completed all assignments, 2.5 bonus points will be added to your final course grade.