The course consists of two 75-minute lecture meetings per week along with two hours of combined lab and recitation.
All laboratories will be conducted on personal computers located in room 361 of Sumwalt building. Programming assigments may be completed on those computers, in other laboratories, or on your own computer. Regardless of where you develop your code, you must hand in a diskette with a complete ``project'' ready for execution on a PC using the Microsoft Visual C++ compiler (version 5.0). Open hourse for the labs are yet to be determined.
You will be expected to attend classes for this course. You will be responsible for all material covered in class and assigned readings. You will be expected to be prepared for unannounced quizzes at any time--class, recitation, or lab. You will be expected to hand in assignments when they are due. Programs are due at the beginning of lab on the due date. You must hand in a printout of the source code of the program and its output and a diskette containing your ``project.'' Please keep a copy of your project until the end of the course. Programs may not be returned to you in time for you to reuse diskettes; for this reason, you need to have several diskettes. You must be prepared to demonstrate your program in lab. Programs will be penalized for lateness unless you have a medical excuse. A 10% penalty will be assessed for each day's delay in submitting a program, up to a maximum of 50%. Homework is due at the beginning of the lecture, recitation, or lab period when it is due. Late homework will not be accepted. There will be two major tests and a cumulative final exam. The tests will have an in-class, written portion and a portion to be written in lab on a computer. The final exam will not have a lab portion.
Attendance at tests is mandatory. Should you unavoidably have to miss one of the major tests and be excused by your instructor, you will be required to take a make-up test upon your return to class. This make-up test will include both written and lab portions.
Grading Policy
In order to obtain a C in this course, you must have an average grade of at least 70 with a minimum test average (including the final exam) of 65. The standard grading scale is used (90 - 100 is an A, 87 - 89 is a B+, 80 - 86 is a B, and so on), possibly with minor adjustments.
Code of Student Academic Responsibility
You are expected to be aware of and to follow the academic code of responsibility that appears in Carolina Community: Student Policy Manual. Except for explicitly designated team assignments, all work that is turned in is expected to be your own. Program assignments may be discussed in a general fashion with other students. In terms of phases of program development, you are only allowed to discuss the requirements and specifications. You are forbidden to share any item concerning design, coding, and testing. In particular, you should never share the design of your program. You should never copy code which has been written by another student or allow another student to copy your code. You should not even discuss how to write specific code with another student. If you need help writing code, see your teaching assistants, lab assistants, or class instructor. If you get code from any of the above, lecture notes, textbooks, or other sources, you are expected to give proper credit, in the comments within your program, to the source of any code you did not write. The minimum penalty for submitting work that is not your own is a zero on the assignment; the usual penalty is the negative number of points the assignment was worth; the maximum penalty is a grade of F in the course. If you are found sharing code with another student, the above penalties will apply to both parties. In addition to these penalties, which are to the discretion of the instructor, your case will be reviewed by the Associate Dean of the College, according to a procedure described in Carolina Community: Student Policy Manual.