IST362: Network Protocols
Course Syllabus
Fall 2002, MWF 12:00pm – 12:50 pm, Morrow G31

Instructor

:  Daniel Dementiev

Office

:  Prichard Hall 208

Phone Number 

:  (304) 696-7241

Office Hours

:  Mon:  8:00 – 9:30, 1:30 – 3:00
   Tue:   8:00 – 9:30, 1:30 – 3:00
    Wed: 8:00 – 9:30, 1:30 – 3:00
    Thu:  8:00 – 9:30, 1:30 – 3:00
    Fri:    8:00 – 9:30

E-Mail

: dementiev@marshall.edu

Textbooks:  
The following textbook is required for the course:

Computer Networking: A Top-Down Approach Featuring the Internet, by James F. Kurose; Keith W. Ross; ISBN: 0-201-47711-4, Second edition.

Course Description:
Modern network protocols, technologies, and concepts are discussed. Internet protocols, architecture, and network layers are emphasized.

Credit:
The course is three (3) credit hours. It includes classroom lectures, exams. and laboratory projects. Students will participate in projects that illustrate the application aspects of the learned concepts. 

Pre/co-requisites:
IST238 – Algorithms

Desired Objectives/Outcomes:
By the end of this course, you should be able to:

Instruction method:
There will be approximately 3 contact hours of classroom lecture per week. I will try to give you at least half of one class per week to work on lab assignments once they have been assigned. The laboratory programming projects cover the major topics of the course. Students may work on their assignments in Prichard Hall 200 or 207.

Evaluation method:
Evaluation of student's performance will be based on the quality of your performance on programming assignments, exams, and class and web-based participation.  

Grading Policy:
Final grades are based on performance in assignments, exams, and attendance as indicated below.  

1 In-class Exams

30%

Final Exam

40%

Projects

20%

Attendance & Participation 

10%

In determining the overall grade for a project, you can expect the following grades based on performance:

A – Excellent work that meets and/or exceeds all of the requirements for a given project, code compiles and works for multiple test samples, all code and associated files are well-documented, and the code is written efficiently.

B – Good work that meets all of the requirements of the assignment, but may have errors in documentation or coding, or contains code that may not work with all possible data samples.

C – Average work that meets all of the requirements of the assignment, but is missing one or more of the items in its entirety that is mentioned in terms of an A grade.

D – Below average work which fails to meet one or more of the requirements of the assignment.

F – Unacceptable work which fails to meet two or more requirements for an assignment, or has code that will not compile and execute.

Final letter grades are determined based on the following grading scale: 

90-100% 

A

80-89%

B

70-79%

C

60-69%

D

Below 60

F

The instructor reserves the right to change these values depending on the overall class performance and/or extenuating circumstances.  

Policy Statement:
Programming assignments: The course includes a number of projects. All assignments are due by midnight on the due date. Late assignments will be penalized at the rate of 10% per day (including weekends).  

Exams: There are two exams. Exact dates and times of exams will be announced in class.  

Make-up Exams and Late Penalty: Make-up exams will not be given except under unusual circumstances and satisfactory written justification. Any student who misses an exam due to an unexcused absence will receive a grade of zero for that exam with no opportunity for make-up or substitution. University excused absences or those occurring with a good reason will be excused. Make up exams must be taken within one week of the original scheduled date. The decision whether to give a make up exam rests with the instructor.

Passing grade: Programming assignments and exams are required parts of the course and must be satisfactorily completed to pass this course. A student must have a passing performance on each part. A failing grade on a component may result in a failing grade in the course.  

Attendance Statement:
Class attendance is not mandatory but recommended part of the course. See grading policy.  

Withdrawal Policy:
The University withdrawal policy is followed in this course. The last day to drop an individual course for the Fall of 2002 is November 1, 2002.  

University Holidays:
The class is officially dismissed on the following dates:

Labor Day:

September 2, 2002

 

Fall Break:

November 27, 2002
November 28, 2002
November 29, 2002

 

Topics and Methodology:
For each topic discussed in the textbook, specific experience of other students and the instructor will be discussed to enhance the characteristics involved. Laboratory programming projects for the course will be based on the chapters we discuss in the textbook. Additional material may also be covered in the class.

Every student is responsible for all materials presented in class, including lectures, notes, and handouts. Students are also highly encouraged to work through the end of chapter exercises in the textbook to help with difficult concepts. In case you are not present for a class, it is your responsibility to contact the instructor and receive information about the material presented in that class. Class attendance is very important.