Textbook(s)

	Computer Systems: A Programmer's Perspective, 3rd edition, Randal E. Bryant and David R. O'Hallaron, (the previous editions of the book will not work, international edition of the book had some mistakes as of a year ago)
	The C programming language, 3nd edition, Brian W. Kernighan, Dennis Ritchie, Optional, but strongly recommended (you can use any C programming book as an alternative).

Prerequisites

Passing CSCI.UA.0102 with a grade of C or better. You are expected to know and remember the material from CSCI.UA.0101 and CSCI.UA.0102 courses.

Grading

Your grade will be based on:

• exams (65%): one midterm exam (25%) and the final (40%),
• programming projects (25% total)
• recitation activities, quizzes (10% total)
  • activities will be completed during recitations (usually in small groups) - you cannot get credit for these unless you are in the recitation (if you do not think that you make it to an 8am recitation, plan your schedule to register for another section of this course)
  • pop-quizzes will be given during lectures and recitations, not announced - no make-up quizzes will be given

Grades will be determined using the following scale:

    A 	95-100
    A- 	90-95
    B+ 	87-90
    B 	83-87
    B- 	80-83
    C+ 	76-80
    C 	72-76
    D 	65-72
    F 	less than 65

The grade of Incomplete is reserved for students who, for legitimate and documented reason, miss the final exam. The grade of Incomplete will not be given to student who started falling behind in class. Those students should withdraw from the class or switch to Pass/Fail option.

Absences (excused and unexcused)

I generally do not take attendance.

The missed quizzes and recitation activities cannot be made up. Four lowest scores on quizzes and recitation will be dropped at the end of the semester. This is to account for any excused or unexcused absences.

The exams can be made up only in case of an excused absence with appropriate documentation.

If you will miss an exam due to a religious observance, please familiarize yourself with University Calendar Policy on Religious Holidays and talk to me well in advance to come up with alternative arrangements.

Recitations

Recitations for the course are used to answer your questions regarding the material and posted homeworks/projects. During recitations you will also get some hands on practice by participating in (usually group) activities.

You should be bringing your computer to the recitations. Make sure its fully charged since the room does not have too many outlets.

Projects

Projects will be given on a regular basis. In general, they will be due one-two weeks after they are assigned. They will require you to write and, often, read significant amount of code (C and assembly).

No projects can be accepted after the last day of classes.

Late and missed projects: For each project you will have a 5 hour buffer window after the due date. You can submit or resubmit the project during this time without any point penalty. The late project submissions lose 30% of their value for each day they are late. If you submit the project 5-24 hours late, the maximum score is 70 (instead of 100). If you submit the project 24-48 hours late, the maximum score is 40 (instead of 100).

Exams

There will be a midterm and a final exam. All exams are cumulative.

Missing an exam: There will be no make-up exams. Failure to take an exam counts as a zero grade on that exam. The only exception to this rule is for students who have a legitimate medical or personal emergency (documented). These students need to talk to the instructor as soon as possible (trying to excuse an exam absence a week after it happened will not work).

Academic Integrity Policy

I use MOSS (a system for detecting software plagiarism) to make sure that the submitted assignments are not duplicates of one another. Your code has to be your own.

I follow the department's academic integrity rules.

In short, it is fine to talk to other students about your ideas and your programs, but it is not fine to work together on assignments or copy someone else's assignment. You cannot copy other people's work without giving them a proper credit (and part of your grade).
Any sharing or copying of assignments will be considered cheating. By the rules of the College of Arts and Science, I am required to report any incidents of cheating to the department.
If you have any doubt if something that you are doing qualifies as academic dishonesty, talk to me!

So what is cheating?

• Sharing code/solutions: by copying, retyping, looking at, or supplying a file (this includes posting partial or complete solutions on the course discussion board, a public repository - think GitHub, or any place where others can access it)
• Coaching: helping your friend to write their code line by line (send them to the tutors or office hours, if you want to help them)
• Copying code from previous course or from elsewhere on WWW. You are only allowed to use code from the textbook and what we supply on the course website.
• Hiring someone to complete your assignments for you.

What is NOT cheating?

• Explaining how to use systems or tools
• Helping others with high-level design issue

Topics Covered

This is a tentative list of the topics and their order:

• C: basic types, control flow
• C: pointers and arrays
• Bits, bytes, ints, floats
• C type conversion
• Machine programming
• Linking
• System hardware
• Memory hierarchy
• Caching
• Virtual memory
• Dynamic memory allocation
• Exceptions and processes
• Multitasking and signals
• System-level I/O
• Concurrent programming

For detailed schedule, see the Daily tab of this page.

Academic Email Etiquette

• Check the school email address on a regular basis. You can simply forward its content to another email account that you use regularly.

• Use your school's email account to send emails to professors, instructors, TA's, graders, administrators, etc. OR make sure that your email address contains your true name, not "frabjous@gmail.com", "BabyGurl@yahoo.com" or some other cool alias.

• Start your email with proper salutations! Use the correct titles (Professor, Dr., etc.) and spell first and last names correctly. If you are on the first name basis with your instructors, use their names, not "Hey". For example: "Dear Professor Drummer" or "Dear Robert", not "Hey Bob".

• Sign your name under the body of your email, otherwise you expect people to read emails from anonymous.

• Do not write everything in upper-case letters. Do not write everything in lower-case letters.

• Make sure you included everything you wanted before hitting send. Don't send three emails one after another because you forgot something in the first one.

• Proofread the text in your email before sending it. Most of the email clients check for typos, but they cannot tell if your email makes much sense. Read it, before you send it.