USC CSD Home
 

Course Description - CSCI 551, Spring 2008, TuTh Section

 
Focus
The main focus of this course is on networking (mainly the Internet) protocols. There is no required textbooks (but there are recommanded ones). The required reading materials mainly come from a list of technical papers.
 
Academic Integrity Policy
Please make sure you read the Academic Integrity Policy of this course.
 
Recommanded Textbooks
 
Syllabus / Topics Covered / Academic Calendar
Please see the list of technical papers covered in this course. A link to the USC Spring 2008 academic calendar is provided here for your convenience.
 
E-mail
Most class related announcements will be done through e-mail via an e-mail reflector setup by the instructor. Please see instructions on how to get on this list (you should do this as soon as possible).

Please do not ask the following types of questions in your e-mail (although they are appropriate for office hours):

  • Here is my understanding of X. Am I right (or is this correct)?
    (You can do this for just about everything and in many different ways. I do not have the bandwidth to deal with too many questions like this.)

  • I don't understand X. Could you explain X to me?
    (It's your responsiblity to come to lectures and ask questions during lectures if there is something you do not understand.)

[BC: Paragraph added 1/26/2008]
Although this is not related to e-mails, it's a type of question I get often. Please do not ask this types of question:

  • Here is what I am thinking of or doing... is it acceptable (or is this okay)?
    (What you are really asking is whether you will receive full credit or not. Wouldn't it be great if you can ask this during exams? It's not an appropriate question for assignments for the same reason it is not appropriate for exams. Although there is a difference between programming assignments and exams, but since you are asking about grading, it's inappropriate.)
 
Homework
There will be 2 to 4 homework assignments consisting of problems.

Some problems will be based on readings and class discussions. Some will be ns/nam simulation problems. Please note that the only allowed file formats are ASCII text, PDF, Postscript, and HTML.

 
Projects
A major programming project to be writeen in C or C++. (Sorry, no Java.) Please see the projects specifications for details.
 
Exams
A midterm and a final examination will be given. The date of the midterm examination will be posted near the top of the class home page. The date of the final examination is firm and it is also listed near the top of the class home page. Any schedule conflicts regarding the midterm exam date must be resolved with the instructor at least one week before the exam date.
 
Grading
Projects:   35%
Midterm Exam:   25%
Final Exam:   40%

Pleaes also note the following:

  • The above percentages will be used to calculate your total score. Final grades (A,B,C,D,or F) will be determined using a modified curve (i.e., we won't necessarily assign an equal number of failing grades as passing grades) based on this total score. No other methods will be considered. (So, please do not ask the instructor to take how much you have improved since the beginning of the semester into account. You are expected to try your best from the beginning!)

  • We will assign grades of C and below to individuals who do not perform satisfactorily in the above areas. (i.e., you should not assume a B- or even C if you perform unsatisfactorily.) However, we hope that everyone will perform well.

  • Your assignments are your own work! No group assignments are allowed or will be tolerated. You are free to talk to other students about assignments but no actual material (files, photocopies etc.) should be shared. We will act harshly at any sign of copying.

  • We will not assign incompletes unless it is for a documented medical reason (in accordance with USC policy).
 
Late Policy
All homeworks and project assignments must be turned in on time. Late submissions will receive severe penalties. Due to clock skews, electronic submissions of projects and homeworks assignments will be accepted within 15 minutes after the specified deadlines without penalties. If you submit with the next 24 hours, you will receive 75% of your grade. You will receive a score of zero afterwards (and your assignment will not be graded).

If you are unable to complete a homework or a programming assignment due to illness or family emergency, please see the instructor as soon as possible to get an extension. A doctor's note is required as proof of illness or emergency. In general, when you get sick, it's best to see a doctor and get a note just in case you may need it later.

 
Regrading Policy
All requests to change grading of homework, programming projects, or exams must be submitted in writing within one week of the time the initial grade was given. Requests must be specific and explain why you feel your answer deserves additional credit. A request to re-grade an assignment can result in the entire assignment being re-evaluated and as a result the score of any part of the assignment be increased or lowered as appropriate.
 
Office Hours
The instructor's office hours are held two hours each week.

You are welcome to make an appointment to see the instructor outside of office hours.

 
Extra Credits
No extra credit assignments will be given for this class. So, there is not need to ask. Try your best from the beginning!
 
Implicit Student Agreement
All work including homeworks, programming assignments and exams must be that of the individual student. It is often productive to study with other students. However, if any portions of homeworks or programming assignments are found to be shared between two (or more) students, zero credit will be given to all students concerned and all students will be disciplined. This policy is in the interest of those students who do their own work, which hopefully applies to all of you in this class. 

This policy also holds for  programming assignments. In this class, we will use sophisticated automated program checkers to detect cheating. Be aware that the program checkers have demonstrated very good results and are widely used within the academic community. Any student caught cheating will be given zero credit and will be disciplined.

It is the students responsibility to submit their assignments to the TA in time. 

For students who satisfied the CSci402 prerequisite at other universities or through work experience, this course assumes that you understand concurrency, synchronization, and UNIX programming. You should be able to write large programs in C/C++. No special assistance or consideration will be offered if your background is inadequate.

 
Student Responsibilities
During the semester you are responsible for completing the assigned readings, homeworks, programs, and exams.

You are expected to read all the papers in detail. Not all details will be covered in class.  We will assume knowledge of material covered in EE450 and a C language programming proficiency from CSci402 or its equivalent. If you covered the introductory material at some other school it is YOUR responsibility to fill in any missing background. Feel free to ask me for advice on appropriate introductory readings if you feel your background is insufficient.

We expect you to attend every class meeting. If you do happen to miss a session, you are responsible for finding out what material was covered and if any administrative announcements were made. You must do so BEFORE the next session (e.g., if there is an assignment given during the missed session, you are still responsible for completing it by the next week along with the other students).  You are advised to read the papers for a particular lecture before attending the lecture. This will greatly enhance your understanding of the subject matter.

 
Fairness
The instructor must treat all students equally and cannot give special treatment to any particular student. Therefore, please do not ask special favors from the instructor because of your circumstances. This may seem unfair to you because you believe that your circumstances are special (understandably, everone does). But the rule the instructor must follow is that whatever he offers you, he must offer to the entire class.
 
Auditing
Auditing is not permitted for this class.
 
Additional Resources
(These resources are provided for your information. Please note that the instructor has not read most of them. Please use these resources at your own risk!)

Programming:

Networking: UNIX:
 

[Last updated Wed Dec 31 1969]    [Please see copyright regarding copying.]