SYLLABUS C SC 284
Introduction to Operating Systems

Fall Semester 2000                                                                                                     1:30 M W F
                                                                                                                                      2:30 M W F
Instructor:    Arlan DeKock MCS 314
                    341-4496
                    adekock@cs.umr.edu

Scheduled Help:

TAs:


Texts:    Applied Operating System Concepts, Silberschatz / Galvin/ Gagne
             An Introduction to Unix, Wang

Goals: Having successfully completed this class you should be able to:

  1. Use Unix commands and filters with good facility
  2. Understand in details the major components of Unix
  3. Discuss the major attributes of an operating system
  4. Discuss the interaction between operating system demands and hardware features
Grading                                 Final Grades
                                    A 90 -
                                    B 80 -
                                    C 70 -
                                    D 60 -

Exams: - Closed book, closed notes, no crib sheet

Homework: - 11 C / Unix Programs

Programs must
 

  1. Contain a program overview. This may be at the beginning of the program. It must contain a complete description of the program with an absolute minimum of technical jargon!!
  2. Execute correctly: a program that doesn't execute correctly is not a program - it's a novel!
  3. Be thoroughly tested: it isn't correct unless you can prove it
  4. A program is considered guilty unless proven innocent. It is assumed that your program will do every bad thing possible unless the 'test input' demonstrates that this is a well behaved program.
  5. Be well documented: (some, but not all of the requirements)
    1. Program Header Who wrote this
    2. Which assignment is it
    3. Variables Well named
    4. Defined
    5. Functions Define PRE / POST conditions
    6. Define what it does in ONE declarative statement
    7. Define HOW it is done
    8. Define the INPUTS
    9. Define the OUTPUTS
    10. Output Neat / Understandable
    11. Comments Stated in APPLICATION terms - not C++
View a C++ Programming Example

NO GRADE LESS THAN C IS ACCEPTABLE.  ANY EXAM THAT RESULTS IN A D OR F WILL REQUIRE ONE OF TWO ACTIONS:

  1. YOU MAY SCHEDULE A RE-EXAM  WITHIN ONE WEEK TO DEMONSTRATE YOUR UNDERSTANDING OF THE MATERIAL OR
  2. YOU MAY DROP THE CLASS


ANY PROGRAM THAT RESULTS IN A SCORE OF < 70 MUST BE RESUBMITTED.

Late programs will be penalized as follows:

1st day -5
2nd day -10
3rd day -15
4th day -20
5th day - No longer accepted

Submitted programs must include