This course explores various topics in modern operating systems and computer architecture, including process synchronization, memory management (caching, virtual memory & disk, etc.), and security. We also look at techniques that are used to enhance processor performance at the hardware and software level. You will learn a variety of techniques that will make you a better IT professional, and will get an understanding of what's happening "under the covers" in modern computer systems.
MW 1:30-3:00 (Towne 303)
F 3:00-4:30 (lab/recitation; location TBA)
Back to Top
- Modern Operating Systems (3rd edition), by Andrew S. Tanenbaum
- Introduction to Computing Systems: from bits & gates to C & beyond, by Yale N. Patt and Sanjay J. Patel
- The C Programming Language, by Brian W. Kernighan and Dennis M. Ritchie, often referred to as "K&R"
- Problem Solving and Program Design in C, by Jeri R. Hanly and Elliot B. Koffman
- Practical C Programming, by Steve Oualline (also can be found on Safari Online Textbooks through Penn Library)
Supplemental Books on reserve in Engineering Library:
- Structured Computer Organization – 5th Edition by Andrew S. Tanenbaum
- Principle of Computer Architecture by Miles J. Murdocca and Vincent P. Heuring
Online Resources: A lot of online material throughout the course can be found under the Resources section.
Back to Top
- Homework assignments (45% of grade)
- These are primarily programming assignments that must be completed on your own.
- There will be occasional non-programming assignments that should preferably be typed.
- Late homeworks submissions will be subject to a 10% grade deduction per day. Homeworks will not be accepted more than one week late, so that solutions may be posted.
- In-class exams (25% of grade total)
- There will be two in-class exams
- Exams are closed book and notes
- This is a comprehensive exam that will be scheduled by the university registrar
- This exam is also closed book and notes
- Recitation will be held Fridays from 3-4pm
- Some sessions will be optional; check the Syllabus for details
Credit for work will be recorded only as reported by the TA in the Gradebook on Blackboard. It is your responsibility to make sure that your work has been properly recorded in the Gradebook.
Make sure you notify the TA of any problems regarding missing records or incorrectly entered scores; the grade entries on the Blackboard will be considered permanent one week subsequent to their posting.
Our TAs will be responsible for adjudicating problems related to grading; the instructor will only be involved as a possible court of last appeal in case there is some truly difficult decision to make (i.e., in most cases, I will not be willing to second guess the TAs' decisions). To submit a request to the TA for a regrade of an assignment, email the TA stating the nature of the problem and the remedy you desire. You must submit this adjustment request within one week of the return of the material in question. The TAs will not consider any requests for grade adjustments that are submitted later than this one week grace period.
Back to Top
All work submitted for this class is expected to be your own, unless otherwise noted in the assignment instructions. If you are caught submitting work that is completely copied from some other source, or that has been prepared by somebody other than you, you will face severe discipline by the university.
Homework assignments are to be completed individually unless explicitly stated. You may talk to fellow classmates regarding the assignment and share ideas on Blackboard, but keep in mind what is appropriate and inappropriate about your collaboration:
- Person A doesn't understand what exactly the problem is asking, e.g. writing actual C code vs. pseudocode. He discusses this with Person B to arrive at one or the other.
- Person A does not understand a particular concept. Person B explains the concept using an example, other than one asked on the homework.
- A attempts half the problem, and B attempts the other half. A and B copy the solutions to half the assignment that the other person wrote.
- Together, A and B work out each homework problem on chalk/white board; then they separately copy down their work and turn it in.
- Person A completed a programming assignment and just before turning it in, he deleted his program - oh no!!!. In desperation, he asks Person B if he can turn in a copy of her program.
- Person A happens to be in the lab working on the assignment and notices that Person B is working on the same assignment. Person A is having trouble compiling his program, and asks Person B to fix the problem for him. Sounds safe, right? It's not.
Note: When in doubt always ask the instructor or TA first, to avoid any potential collabration that can lead to academic dishonesty.
Back to Top
You will turn-in all programming assignments using Blackboard. Follow the steps below.
- Log into Blackboard
- Open your course (CIT 595).
- In the main menu on the left-hand side, click "Assignments".
- Click on the assignment for which you want to submit your homework.
- In Section #2, "Assignment Materials", leave the "Submission" (the text area at the top) blank, as your submission will consist of files that you will upload.
- Below the textbox, next to the label "Attach File", click the "Browse for Local File" button. After you choose the file, you should see it listed next to the label "Attached files" (i.e., it should be uploaded automatically when you select it). Unless otherwise noted, your submission should consist of a single .zip or .tar file.
- After uploading all files, click the "Submit" button.
You may submit multiple times, but only the last submission will be graded.
Submissions after the deadline are subject to a 10% per day penalty, up to seven days, after which the submission will not be accepted.
Back to Top