Course Basics

Instructor:

Graduate Teaching Assistants:

Undergraduate Teaching Assistants:

Prerequisites: C or better in CS 211 or CS 222, and C or better in CS 110 (CS 110 can be a co-requisite with CS 262).

Format: Lecture

Lectures:

Textbooks:

Blackboard: Blackboard will be used for all official announcements, course slides, assignments (including submissions), and grades.

Piazza: Piazza will be used for online discussion; any information discussed on Piazza will be assumed to be known to students.

• The discussion board on Piazza is required reading for all projects. You MUST read the discussion board for clarifications and project updates.
• Course schedule, announcements discussion. GTA/UTA contacts and office hours will be on Piazza too.
• Do not e-mail course staff about programming problems; use the discussion board.
• Use public posts on Piazza to discuss programming project requirements, labs, and other material related to the course.
• When prompted by a TA, use private posts on Piazza to share portions of your code pertaining to your questions. Don't share your project code in public posts.
• Email course staff only for logistical issues such as meeting outside of office hours, missing lab/lecture, grading disputes, medical situations, etc. Email addresses are listed on above and on Piazza.

Course Information

Course Description:

Course Outcomes

By the end of the semester, students will:

• Be able to implement, test and debug a designed solution to a problem in a low-level programming language, specifically the C programming language.
• Have a good understanding of C language constructs such as pointers, dynamic memory management, and address arithmetic.
• Have a good understanding of C libraries for input and output, and the interface between C programs and the UNIX operating system.
• Have the ability to use UNIX tools for program development and debugging.

Coursework

Programming assignments

Students will receive a number of programming projects (3)during the semester. These programming projects will be a primary focus of your grade - each one should take multiple sessions of coding, with questions asked in between. Don't be surprised if you're spending 20+ hours on each one. All project grades will be averaged together evenly. Programming projects are INDIVIDUAL work.

• Submission
  • All projects are to be submitted to Blackboard. You can submit your work an unlimited number of times to BlackBoard, and by default only the last version will be graded.
  • Turning in the wrong files will likely result in a zero. You can and should download your submitted attempts to verify that you turned in a working copy.
  • Broken Code == Bad Scores. Any code turned in that does not compile is likely to receive a zero. Make sure your code compiles and runs correctly before submission.

• Notes:
  • Submission times are automatically recorded by Blackboard, and there's no distinction between a tiny bit late and nearly a day late - plan ahead to make sure that your submission is on time.
  • Blackboard being unavailable is not an excuse for turning in a late assignment; in the rare situation that the website is somehow unavailable or giving the student an error, the student MUST email their submission to their GTA before the deadline, otherwise it will be considered late.
  • Catastrophic computer failure will not be cause for an extension. Use a backup service such as DropBox (or any cloud service), emailing yourself, storing to a USB drive, whatever it takes. Every semester multiple students' computers die, are stolen, or otherwise 'lose' projects. Don't be the student who forgot to (frequently) back up your work!

Grading Procedures

Grade Distribution

Grading Policies

• Grades within a category (i.e. tests, projects, labs) are weighted equally.
• Students must have Respondus Browser locakdown installed before taking any quiz or exams.
• The final exam is cumulative.
• Challenging of any grade must occur within a week of when the graded assignment has been returned.
• To receive a passing grade in this course, the average score for all exams (Tests and Final exam) must be at least 60%.
• Any number of resubmissions are allowed (the most recent is used), however a resubmission turned in after the deadline will be considered a late submission.
• In general, make-ups are not allowed except on exams ( under very special circumstances).
• Assignments are typically due at midnight on the listed due date.
• Late submission policy (up to 48 hours) is as follows: <=24 hours with 10% off, >24 hours &&<=48 hours with 25% off, > 48 hours will receive 0. For example, if you are late by 10 hours and you get 75 on the assignment, your final points will be 67.5. Submission times are automatically recorded by Blackboard, and there is no distinction between a minute late and a day late. Please plan ahead to make sure that your submission is on time. Taking backups regularly is highly recommended.
• Code must run on Mason's Zeus platform (zeus.ite.gmu.edu) using gcc. Students may develop programs using any computer system they have available. However, submitted programs must run under gcc compiler available on Mason. Your documentation should clearly state which software was used for compilation, and once makefiles are introduced, a makefile should be included with each assignment submission.

Grading Scale

Honor Code

Unless specific instructions are given to the contrary, programming assignments are an individual effort, no group work is allowed. In addition to code, this includes the sharing of test cases, pseudocode, or approaches, receiving assistance in debugging code, as well as the use of external Internet sites.

Both the GMU Honor Code and the CS Department Honor Code apply in this class. Any use of a direct contribution on any program, homework, quiz, or exam will be reported as a violation of the honor code.

We take the honor code quite seriously. Any attempts at copying or sharing code, algorithms, or other violations of the honor code simply will not be tolerated. We use automated software to flag suspicious cases, and then review them to find the cases that must be submitted to the Office of Academic Integrity. The penalty for cheating will always be far worse than a zero grade, to ensure it's not worth taking the chance. Confirmed cases of cheating almost always translate into course failure.

Some kinds of participation in online study sites violate the Mason Honor code: these include accessing exam or quiz questions for this class; accessing exam, quiz, or assignment answers for this class; uploading of any of the instructor’s materials or exams; and uploading any of your own answers or finished work. Always consult your syllabus and your professor before using these sites.

Special Accommodations

Students who have a right to accommodations due to disabilities or other conditions should discuss this with the instructor as soon as possible. Accommodations will follow the recommendations of the University's Office of Disability Services.

Tentative Schedule