CPSC410 Operating Systems and Architecture I
Syllabus
1/5
CPSC 410 Operating Systems and Architecture I
Required, 3 Credits
SYLLABUS
Department of Physics, computer Science and Engineering
Christopher Newport University, 1 University Place, Newport News, VA 23606
Instructor:
Telephone:
Email:
Dr. Ming Zhang
Contact Room:
GOSNOLD 137
(757) 594 – 7563
Fax:
(757) 594 - 7919
mzhang@pcs.cnu.edu
URL http://www.pcs.cnu.edu/~mzhang
1. Message from the Provost:
We want you to succeed at CNU; therefore I may notify the Academic Advising Center if
you seem to be having problems with this course. Someone may contact you to help you
determine what help you need to succeed. You will be sent a copy of the referral form. I
invite you to see me at any time that I can be of assistance in helping you with the course
material.
2. Catalog Description:
Introduction to operating systems, I/O processing, interrupt structure and multiprocessingmultiprogramming, job management, resource management, batch and interactive
processing, deadlock problem, computer networking through teleprocessing and system
performance evaluation.
3. Text:
William Stalling, Operating Systems-internal and design principles, 2005, fifth edition,
Prentice Hall, INSB: 0-13-147954-7
4. Prerequisite/Co-requisite:
Prerequisites: CPSC 270; CPEN 214.
Prerequisite or co-requisite: CPSC330 or CPEN414
5. Prerequisites by topic:
1. Data Structures
2. Java programming skill
3. Principles of computer architecture.
6. Objectives:
1. To understand the basic principles of operating systems involving processes, I/O, memory
management, (and file systems).
2. To develop an understanding of operating systems by studying the implementation of the
UNIX-like MINIX operating system for the IBM PC.
3. To investigate first hand the implementation of the MINIX/UNIX operating systems by
the means of C programs and interactive work with the MINIX operating system.
CPSC410 Operating Systems and Architecture I
Syllabus
2/5
7. Topics:
0. Operating system history
1. Computer system overview
2. Operating system overview
3. Processes
4. Thread
5. Mutual exclusion and synchronization
6. Dead lock and Starvation
7. Memory management
8. Virtual Memory
9. Uniprocessor Scheduling
10. Multiprocessor & Real Time Scheduling
11. I/O Management and Disk Scheduling
12. File Management
8. Schedule:
Two 75-minute class sessions/week
9. Computer Usage:
Computer lab exercises (including several small Java and C/C++ programs to illustrate
key system calls plus a series of labs involving the operating system)
10. Outcomes:
1. an ability to apply knowledge of mathematics, science, and computer engineering
2. an ability to design and conduct experiments, as well as to analyze and interpret data
3. an ability to design a hardware and software systems to meet desired needs
4. an ability to use the techniques, skills, and engineering design automation tools necessary
for effective computer engineering practice.
11. Assessment and Examination:
Exercises (Attendances)*:
20% of the semester assessment
Test 1:
5% of the semester grade
Test 2:
5% of the semester grade
Test 3:
10% of the semester grade
Large software system programming project: 25%
Final Exam:
35% of the semester grade
* Exercises (Attendances): The student could be given credit when the student signed the
attendance sheet and also submitted the exercise before the deadline. No credit will be assigned if
the student only submitted exercise before the deadline but not sign the attendance sheet. And no
credit will be assigned if the student only signed the attendance sheet but not submitted exercise
before the deadline.
CPSC410 Operating Systems and Architecture I
Syllabus
3/5
Your large software system programming project will be graded based on the following table.
No.
7
8
9
10
11
12
13
14
15
Item
1 Report 1: system selection and analysis
2 Report 2: system detail design
3 Report 3: embed Operating System principles, policies,
techniques, or architectures
4 Attendance of the final report oral presentation
Oral presentation of the final report
If you do not give the final report oral presentation, you will lost
the following 20 points for item 5 to 15, no matter if you submit
the project materials or not.
5 PowerPoint slides for final report oral presentation
6 Larger software system programming codes
Codes between 0 – 1999: - 18
Codes between 2000- 2199 lines: 0
Codes between 2200-2399 lines: 2
Codes between 2400-2599 lines: 4
Codes between 2600-2999 lines: 6
Codes equal or more than 3000 lines: 8
Final Report: Executive Summary
Final Report: System selection
Final Report: System analysis
Final Report: System design
Final Report: embedded Operating System principles, policies,
techniques, or architectures (Yes/No)
If answer is “No”, you also lost following 8 points of items of
12, 13 and 14.
Final Report: Significance of points
Final Report: Solution(s)
Final Report: Methodology and technology
Final Report: References
Total
Mark
Available
1
1
1
Mark
Given
2
2
8
0.25
0.25
0.25
0.25
0.5
2
2
4
0.5
25
12Grading Scale:
Each test, technical essay, final exam and final grade will be based on 100 points and is
intended to have the following scale:
A: 93-100; A-: 90-92.9
B+: 86-89.9; B: 83-85.9;
C+: 76-79.9; C: 73-75.9;
D+: 66-69.9; D: 63-65.9;
F: 0-59.9
B-: 80-82.9
C-: 70-72.9
D-: 60-62.9
CPSC410 Operating Systems and Architecture I
Syllabus
4/5
13. Exercise/Homework:
Total 20 Exercises will be assigned in or after class.
14. Makeup:
There will be no makeup tests. Only one absence from the tests might be accepted.
Excused absences from tests will be assigned the equivalent percentage achieved on the
final exam. Unexcused absences will be handled similarly with a penalty of 50%. In order
to be excused for missing a test or handing in an assignment late, it is imperative that you
alert instructor to your individual situation as soon as possible.
15. Attendance:
You are expected to be in class, on time, each day. Absences should occur only when
absolutely necessary and for valid reasons. If you are absent, you are responsible for all
material covered in class, class notes, assignments and deadlines.
Quiz, Exercises, and Attendances: The student could be given credit when the student
signed the attendance sheet and also submitted the quiz or exercise before the deadline.
No credit will be assigned if the student only submitted quiz or exercise before the
deadline but not sign the attendance sheet. And no credit will be assigned if the student
only signed the attendance sheet but not submitted quiz or exercise before the deadline.
CNU will introduce a grade of "UI" (unauthorized incomplete), which “indicates that a
student did not participate academically in a course beyond the 60% date in the semester;
this is computed in the cumulative GPA in the same manner as an F.”
Instructors will be directed to award the grade of UI in this circumstance; whereas the
grade of F shall be awarded to a student only if the student participated academically after
the 60% date (but failed the course nonetheless). For all purposes except for the handling
of financial aid, the effect of a UI upon a student will be equivalent to that of an F. (Note
that many instructors give an "I" to a student who really did NOT receive authorization to
get an incomplete; the instructor simply did not feel like giving an F.) We will now be
able to assert that an F means an "earned" F, ie a grade that is only awarded if a student
continues in the class for the duration of the semester (or - at least - beyond the 60%
date). After the introduction of the UI, it is anticipated that the number of financial aid
students who received all W's and UI's will be considerably smaller than the number of
problem students (as defined above) prior to this policy change, thereby leading to a
decrease in labor performed by CNU staff, including Financial Aid officers. CNU will
continue to pay this money to the government and will strive to extract reimbursement
from the student, but it is anticipated that this sum of money will be considerably less
than the $50K which CNU repaid to the government during the last academic year.
CPSC410 Operating Systems and Architecture I
Syllabus
5/5
16. Honor Policy:
You are expected to do your own work. You should not directly collaborate on homework
or programs. As a reminder, here is the University Honor Pledge. "On my honor, I will
maintain the highest possible standards of honesty, integrity and personal responsibility.
That means I will not lie, cheat, or steal and as a member of this academic community, I
am committed to creating an environment of respect and mutual trust." EVERYTHING
YOU TURN IN TO MEET COURSE REQUIREMENTS IN THIS CLASS IS TO BE
INDIVIDUAL WORK.
17. Getting Help:
It will be easiest for you to obtain assistance from me via email. Please email me your
questions if at all possible. You are all welcome to see me in my office hours.
18. Writing Center:
Because all writers can benefit from having other writers respond to their work, I strongly
encourage you visit the CNU Writing Center. Consultants can help you at any stage of the
writing process, from invention, to development of ideas, to polishing a final draft. The
Center is not a proofreading service, but consultants can help you to recognize and find
grammar and punctuation errors in your work as well as provide assistance with global
tasks. You can call for an appointment (594-7684) or drop in. Go as early in the writing
process as you can, and go often!
19. Disabilities:
If you believe that you have a disability, you should make an appointment to see Dr. Kelly
B. Cartwright, Associate Provost for Academic Services of Christopher Newport
University (757-594-7949; kewright@cnu.edu) to discuss your needs. In order to receive an
accommodation, your disability must be on record in Disability Support Services, Room
101, McMurran Annex (Telephone: 594-8852)
20. Prepared by: Dr. Ming Zhang