CS 2430 - CONTROL AND CONCURRENCY (3-3-4) Administrative Information Note: This "Administrative Information" document is also available via "printdoc" from the CS 2430 "workon" environment. Type "printdoc" at the "workon" prompt for a description of the documents that are available, and instructions on how to print them. General Description: Algorithms, data structures, and problem solving techniques for attacking and solving problems that are generic to con- current systems. Emphasis on real-world problems, featuring case studies. There is a laboratory component for this course, and several programming assignments will be given (outside of lab) to allow practice on course-related topics. Prerequisites: CS 1502 or equivalent Instructor: Jim Greenlee (note: please call me Jim !) College of Computing 115, 894-6049 Office Hours: MWF 10:00-11:00, 12:00-1:00 Th 9:30-11:00 (other times by appointment) UNIX Mail: jkg@anywhere (prism, cc, eecom, ...) A local newsgroup (git.cc.class.2430) is available for this course - it will be used for announcements, clarifications, and answering questions about course topics. In particular, many issues pertaining to programming assignments and lab work will be handled via the newsgroup. Postings made to the newsgroup carry the same weight as if they were made in class. Each student is responsible for keeping up with news postings. Required Texts: Bacon: Concurrent Systems - An Integrated Approach Weiss: Efficient C Programming Various: UNIX On-line Manual Pages Grading: 20% Programming Assignments 25% Homeworks 25% Quizzes 30% Final Exam Programming Assignments: A more detailed description of the programming assignment will be posted to the CS 2430 newsgroup, shortly before the first assignment is distributed (check the syllabus to see when that will be). The project description document will contain an overview of the project, how it will be distributed, how to turn it in, and how it will be graded. Please read the docu- ment carefully as soon as it becomes available. Homeworks: A homework assignment will be given out each week of class. It will normally be posted to the newsgroup on or about Monday of each week, and students will have until Wednesday of the fol- lowing week to complete the homework and turn it in. Homeworks must be submitted electronically via the "turnin" program, before 6:00 PM on the day that they are due. Late homeworks will not be accepted for grading, and will receive a grade of 0 (zero). Makeup assignments will not be provided or accepted. All homeworks count equally toward the Homework portion of the final grade. Quizzes: Scheduled quizzes will be given approximately every other week, during the first 30 minutes of recitations (the syllabus shows during which weeks a quiz will be given). Quizzes must be taken on their scheduled date unless you have cleared with your recitation TA at least 24 hours prior to the quiz that you will be missing it for a valid reason. Your recitation TA will make the final determination as to what constitutes a ``valid reason''. All quizzes count equally toward the Quiz portion of the final grade. Makeup quizzes will not be given. Final Exam: A comprehensive exam will be given during the appointed time period during finals week. Details about this exam will be forthcoming nearer the end of the term. Recitations: Recitations are held weekly. If a quiz is scheduled, then it will be given at the beginning of the recitation. During weeks when a quiz is not scheduled, the recitation TA will go over some relevant aspects of the programming project that was assigned during the previous week. After the allotted time for the quiz or project discussion (whichever is appropriate for the week in question), the reci- tation TA will discuss pertinent aspects of the homework assignment that is due that week. Often, this discussion will be conducted as a "question and answer" session, so be sure that you have looked over the homework prior to coming to recitation. Requests to change to a different recitation section must be approved in writing by the course instructor. In no event will approval for a change be given after the end of the first full week of classes. Academic Honesty: It is expected that (unless specific instructions to the con- trary are given) all student submissions of coursework in this academic course will be individual efforts. Students who show evidence of having violated this rule will receive a grade of Incomplete, and will be reported to the Dean of Students on suspection of academic misconduct. Section XIX.B. of the Student Rules and Regulations defines academic misconduct as ``any act that does or could improperly distort student grades or other student records.'' Among the list of items that are cited in this section is the following: 1. Possessing, using or exchanging improperly acquired writ- ten or verbal information in the preparation of an essay, laboratory report, examination, or other assignment included in the academic course. In layman's terms, this means that if any student receives or provides any information that would enable himself/herself or any other person to complete an assignment or examination that is not wholly the work of the person submitting that assign- ment or examination, then that student is in violation of the academic honor code of Georgia Tech. Any such incidents will be dealt with accordingly, and penal- ties for conviction can be severe - up to and including notice of academic misconduct on a transcript, failure in the academic course, expulsion from the College of Computing, expulsion from Georgia Tech, and community service. Note: we use "cheatfinder", so don't even think about it.