Date: Tue, 14 Jan 1997 20:09:57 GMT Server: Apache/1.1.1 Content-type: text/html Content-length: 6159 Last-modified: Thu, 29 Aug 1996 21:53:25 GMT
Syllabus CS122 - 401 Fall 1996 Instructor: Richard King office: 763-C Anderson Hall e-mail (best way by far to reach me): newt@sac.uky.edu phone: (606) 257-4084 fax: (606) 323-1971 office hours: Mondays 3:00 pm - 5:00 pm Tuesdays and Thursdays 5:00 pm - 6:00 pm and by appointment Schedule: Topics Chapter Reading in Text ----------------------------------------- --------------- Introduction to Unix and Review of C++ -- Algorithms and Complexity 11 Linked Lists and Pointers 14 Stacks and Queues 15 First Exam Recursion 16 Trees and Graphs 17 Second Exam Sorting 18 Searching 19 Final Exam Grading Policy: Programs 30% Homework, Quizzes, and Class Participation 25% First Exam 15% Second Exam 15% Final Exam 15% Your class participation grade will be determined by your attendance in class and your active participation in class discussions. I teach my classes in a highly interactive manner, so come prepared each day with something constructive to say about our current topic! All exams and quizzes will be closed book. Quizzes will be given during class and usually will be unannounced. There will be no makeup of missed quizzes unless you have a valid University excused absence. There will be two regular exams and a final exam. All three exams should be considered as cumulative, and will be administered in our regular classroom. Assignments will be made throughout the semester and may include readings, homeworks to be done on a word-processor, and programming assignments. Homework and programming assignments are considered separate. Homework assignments are strictly due on the date specified. Since we may go over the answer to homeworks in class, no late homework assignments will be accepted. All homework submission must be word-processed -- hand-written homework assignment submissions will neither be accepted nor graded. Programming assignments will also have a specified due date. Programming assignments turned in after this date will be penalized 5% per day (not counting weekends and holidays), and no programming assignment will be accepted after it is more than 5 days late. After that time, you will get no credit for the late assignment, so be sure to turn in your programming assignments on time! Homeworks and programs are treated as separate assignments, and should be turned in separately. Assignments will be announced primarily in class and on the CS122 World-Wide-Web Home Page. Additional information regarding assignments may be sent by e-mail. Be sure to bring a copy of all assignments to class for review and clarification. All papers to be turned in should be organized in a neat and orderly fashion. Pages of printouts should be gathered in order and stapled in the upper left corner to make a 'booklet'. Your name should be written by hand on the front page, in the upper right-hand corner. Not all assignments will have the same grading weight as others. The weighting of each assignment will generally be indicated when assigned. The programming assignments will require more than just typing a C++ program into the computer and running it. These requirements will be discussed in detail in class and in additional files. Text: Introduction to Computer Science with C++ by Lambert, Nance, and Naps I highly recommend your buying and using the text. Incompletes: The University policy on the grade of Incomplete (I) will be adhered to strictly. The grade of I will only be granted in extraordinary circumstances. For this reason, if circumstances indicate that you may not be able to successfully complete the coursework, you should strongly consider withdrawing, auditing, or changing your grade option to pass/fail (if a grade is not needed). Come see me immediately if you become concerned about this. Cheating: Cheating on tests, programs or homework will not be tolerated. University policy dictates that the minimum penalty for cheating is to receive a grade of "E" for the course. As for what constitutes cheating on a program, any direct use of another's program, or allowing another the direct use of your program will be considered cheating. Ideas may be discussed between students, but coordinated writing or using of code is cheating, even if variable names, format, comments, etc. are different. Person or persons using another's code, as well as the person whose code is being used, will all be considered guilty of cheating. Computer Accounts: This semester will will be using Unix accounts on HP computers in the Library Microlabs, called "sac.uky.edu". Be careful to treat your computer account as you would your personal and confidential records. Be sure to change your password frequently, choosing a password which is not easy to guess. Be sure to protect your account (via the "chmod" command in Unix) so that others cannot read your files. And, most importantly, don't abuse the system by doing things which are inconsiderate, annoying, or disruptive to other users, or destructive to other accounts. Your right to use the UK computer systems can be taken away if you abuse the privilege.