IST337:
Network Operating Systems
Course Syllabus
Spring 2002, MWF 9:00 am 9:50 am, PH 200
Instructor |
: Brian M. Morgan |
Office |
: Prichard
Hall 212 |
Phone Number |
: (304) 696-6469 |
Fax Number |
: (304) 696-6533 |
Office Hours |
: MWF: TR: MW: |
E-Mail |
Textbooks:
The following textbook is required for the course:
Operating Systems Concepts 6th ed., by Silberschatz, Galvin, & Gagne; John Wiley & Sons; ISBN: 0-471-41743-2, 2002.
Computer
Requirements:
Supplemental materials can be found contained within the WebCT environment (http://webct.marshall.edu/). I will be sending class announcements,
updates, etc. using your WebCT account (will discuss during the first
lecture). Access to a WWW browser is
required (Netscape 4.0 or higher or Internet Explorer 5.0 or higher) and Adobe
Acrobat Reader (available for download through the class WebCT site).
Course
Description:
Covers
current operating systems that support networking and distributed processes.
Topics include process management, memory management, security issues, network
support and management, and hardware management.
Credit:
The course is three (3) credit hours. It includes classroom
lectures, exams, and programming projects. Students will participate in
programming projects that illustrate the implementation of concepts in general
applications.
Pre/co-requisites:
IST236 (Data Structures I) and IST263 (Programming Practicum) or permission
Desired Objectives/Outcomes:
By the end of this course, you should be able to:
-
Discuss the developmental principles behind operating
systems design
-
Discuss issues in compatibility and connection and
use through a network
-
Discuss how memory, processes, and files are managed
-
Explain how applications and hardware interact with
an operating system
- Help someone select a network operating system based upon needs
Instruction method:
There will be 3 contact hours of classroom lecture per week. Programming
projects covering the major topics are part 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, and exams.
Grading Policy:
Final grades are based on performance in assignments and exams, as indicated
below.
2 In-class Exams |
30% |
Final Exam |
25% |
5 Programming Projects |
45% |
Attendance & Participation None
Required |
0% |
Assessment
of Projects:
The
grading of all programming projects will take into account the following:
1.
Although the most important attribute of a program is
correctness, grading will take into consideration such items as time and space
efficiency, documentation, etc.
2.
Programs must have proper inline documentation and
must be properly indented. 20% will be deducted for poorly documented and/or
poorly indented code.
3.
All submitted code must compile correctly. Code that
does not compile will receive 0 credit.
4.
When a problem does not specify a required
complexity, the grading will differentiate between efficient and nonefficient
code. For example, if you write a program that contains a number of
checks that are redundant and/or has one or more loops that iterate zero or one
time, up to 10% of the grade will be deducted.
5.
When a method name and/or parameters are specified in
an assignments description, you must use that name and/or parameters.
6.
When you write a function, remember that the function
should work for all possible inputs. Not on just your test inputs.
7.
Although interactions with other students are
encouraged, you must compose your own answers, unless otherwise noted.
Individuals
who utilize other peoples code, thoughts, or ideas must provide appropriate
references to said resources. Failure to
provide such documentation will result in a failing grade for the assignment,
and may result in a failing grade for the course.
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 programming
assignments. All assignments are due by
Exams:
There are three exams: The first will come after chapter 6, the second
after chapter 12 and a comprehensive Final exam (as scheduled). 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:
For the first time, I am NOT making class attendance mandatory. However, I will keep a record of who is
attending and who is not. If you miss
class, it is your responsibility to catch up on material missed, and will not
be the responsibility of the instructor to catch you up on material missed
during my office hours.
Withdrawal Policy:
The University withdrawal policy is followed in this course.
The last day to drop an individual course for the Spring
of 2002 is
University Holidays:
The class is officially dismissed on the following dates:
MLK, Jr. Day:
Spring
Break:
Topics and Methodology:
The following outline delineates the tentative class schedule with topics to be
addressed during the course. Please
note this is a tentative schedule and it may change upon class progress:
January 14 |
Review of Syllabus Introduction to WebCT |
January 16 |
Chapter 1 Chapter 2 |
January 18 |
Chapter 2 |
January 23 |
Chapter 3 |
January 25 |
Chapter 3 |
January 28 |
Chapter 4 |
January 30 |
Chapter 4 Project #1 Due Assign Project #2 |
February 1 |
Chapter 5 |
February 4 |
Chapter 6 |
February 6 |
Chapter 6 |
February 8 |
Chapter 6 Review for Exam 1 |
February 11 |
Exam 1 |
February 13 |
Chapter 7 |
February 15 |
Chapter 7 |
February 18 |
Chapter 8 Project #2 Due Assign Project #3 |
February 20 |
Chapter 8 |
February 22 |
Chapter 8 Chapter 9 |
February 25 |
Chapter 9 |
February 27 |
Chapter 9 |
March 1 |
Chapter 10 |
March 4 |
Chapter 10 |
March 6 |
Chapter 10 Project #3 Due Assign Project #4 |
March 8 |
Chapter 11 |
March 11 |
Chapter 11 Chapter 12 |
March 13 |
Chapter 12 |
March 15 |
Chapter 12 Review for Exam 2 |
March 18 |
Exam 2 |
March 20 |
Chapter 13 |
March 22 |
Chapter 13 |
March 25 |
Chapter 14 |
March 27 |
Chapter 14 Project #4 Due Assign Project #5 |
April 8 |
Chapter 15 |
April 10 |
Chapter 16 |
April 12 |
Chapter 17 |
April 15 |
Chapter 18 |
April 17 |
Chapter 18 |
April 19 |
Chapter 19 |
April 22 |
Chapter 19 |
April 24 |
Chapter 20 Linux Study |
April 26 |
Chapter 20 Linux Study |
April 29 |
Chapter 21 Windows 2000 Study |
May 1 |
Chapter 21 Windows 2000 Study Project #5 Due |
May 3 |
Review for Final Exam |
May 10 |
Final Exam 8:00 am 10:00 am |
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.
Effort
Required:
As a 300-level course, a considerable amount of development and research effort
is required of the student. For every
one hour in class, the student is expected to put in an effort of at least 3
hours outside the class for studying and programming. Upon background and preparedness, some
students may have to put in additional effort.
Communication:
The Bulletin Board facility of WebCT and private E-mail will be used to make
any general announcements, last minute changes, etc. It is mandatory that you monitor your WebCT
course messages at least once a day.