Temporal and Spatial Attributes
- Sec 0101 TuTh 12:30 - 1:45 pm CSIC 3117
Text: Computer Systems: A Programmer's Perspective, by Randal E. Bryant and David O'Hallaron, Prentice Hall, 2003. ISBN 013034074X (Required) Text: The C Programming Language, 2nd ed., Brian W. Kernigan and Dennis Ritchie, Prentice Hall, 1988. (Recommended) Text: Pointers on C , Reek, Addison-Wesley, 1998. (Recommended) Extra resources: books you choose and on-line (search engines, wikis) Handouts Lectures Labs
Cumulative Final Exam : May 14, 2010 from 4PM-6PM 30%-45% Best 2 out of 3 tests (2/??, 3/??, 4/??, ): 20%-40% Four labs: 10%-25% Class Participation: 0%-5%
- Attendance will not be taken at lectures. However, you are responsible for all material presented in the classroom and in the designated readings. The instructor reserves the right to give pop quizzes.
- You may appeal your grade up to seven calendar days from the date your grade was posted. For a lab, you should first appeal to the TA responsible for grading that lab. If you are not satisfied after your discussions with the TA, you may appeal to Dr. Hugue. Appeals on exam grades should be made directly to Dr. Hugue. Please note: grades will only be changed if an error has been made in the grading. Please also read http://gtalumni.org/news/ttopics/win96/wiesen.html
- Late assignments will be docked 10% each day for the first three days. Assignments more than 3 days late will not be accepted, unless you have arranged an extension in advance with Dr. Hugue. Extensions can only be given by Dr. Hugue and will only be given in extenuating circumstances as per the University rules.
- Even if you can not complete the assignment- turn-in your work. Partial credit may be given if you made progress on the problem.
- Sharing code or other electronic files: either by copying, retyping, looking at, or supplying a copy of a file.
- Sharing written assignments: Looking at, copying, or supplying an assignment.
- Asking anyone but a TA or a faculty member to look at your assignment without the express permission of Dr. Hugue.
- What is not cheating
- Clarifying ambiguities or vague points in class handouts or textbooks.
- Helping others use the computer systems, networks, compilers, debuggers, profilers, or other system facilities.
- Helping others with high-level design issues.
- Helping others debug their ideas (not their code) at a high level.
- Documenting any human assistance as a resource, just like a book or webpage reference.
- Refusing to allow anyone to see your code or to show you their code.
- Seeking aid in debugging code from a TA or a faculty member or from any person designated to help you by Dr. Hugue.
Plan on spending at least twice as much time outside of class as in-class--reading, doing labs, and doing problems. If you don't like my books, pick others that cover the same material. Take advantage of on-line resources, especially topic-specific webpages, and other peoples' course notes. Read the discussion groups regularly and post ALL your lab and course-specific queries there. Keeping up with the reading will make the lectures more relevant. Don't expect to use ONLY Lecture notes to study--you MUST read and do labs. Don't expect to use ONLY books to study--some lectures are unique and understanding the labs is essential to the course. Follow directions. Read. Read. Read!!!