Home | | Requirements | | Syllabus | | Assignments | | Lectures

    Course Requirements | | Late Policy | | Collaboration Policy

    Course Requirements
    1. Laboratory Assignments
    Laboratories will be held weekly. One section meets Monday afternoon and the other section meets Tuesday morning. Attendance at the lab sections is mandatory. There will be 12 laboratory assignments. Each will be due at the end of the lab section. Each laboratory is worth 25 points, for a total of 300 points.

    2. Programming Projects
    There will be 5 programming projects during the semester. You will have two to three weeks to complete each one. Please consult the schedule for due dates. The first three will be worth 50 points and the last two will be worth 75 points for a total of 300 points.

    3. Midterm Exams
    There will be two midterm exams held in the evening on the following dates:

      Exam 1: Wednesday, October 6, 6:30 - 8:30 p.m.
      Exam 2: Wednesday, November 10, 6:30 - 8:30 p.m.

    If you cannot attend one or both of these exams, please see your instructor immediately to arrange an alternative time.

    4. Final Exam
    The final exam will be held at the following time:

      Thursday, December 16, 8:30 a.m.

    5. Final Grade
    The final grade will be computed as follows:

      Laboratory Assignments15%
      Programming projects25%
      Midterm Exams40% (20% each)
      Final Exam20%

    Late Policy

    1. Lab assignments
    Lab assignments should be turned in at the end of each lab. However, generally the final due date for the labs will be at 11:00 a.m. on Wednesday following the lab (with an exception for Thanksgiving week). Please refer to the assignment schedule for a list of lab due dates.

    2. Programming Projects
    Programming projects are due at 11:00 a.m. on the dates specified on the assignment schedule. You have ample time to complete these projects, so you should plan to have your project finished several days in advance so that a last minute illness or computer crash does not interfere with the due date.

    3. Penalties for late work Projects or labs submitted within 24 hours of the time when they were due will be penalized 10%. Penalties will accumulate for each day late, losing 10% per day late. The late penalty is determined by the time of the electronic submission and the time when the assignment is physically transferred to the instructor or "signed in" by any Math/CS faculty member or the departmental secretary (whichever is later), so turning in an assignment in the wee hours will be difficult. Once an assignment/project is returned to the class, no late work will be accepted.

    Collaboration Policy
    In doing any work in this course (e.g. assignments/programming projects/tests) it is expected that the work you turn in is your own work. The amount of collaboration allowed differs between laboratory assignments and programming projects, so please read the following guidelines carefully. If you are in doubt, be sure to ask the course instructor.

    Laboratory assignments
    Collaboration is allowed on lab assignments. You may refer to your texts, your class notes and your course instructor for help. In addition, you may talk to your TA's, instructors, and fellow students about how to go about solving the various problems presented. However, you must write and type in your own code. Also, if you receive substantial help from some source, e.g. a book, an instructor, or a fellow student, please acknowledge that collaboration.

    Programming projects
    Limited collaboration is allowed on programming projects. You may use your texts, your class notes and your course instructor for help. You may discuss the logic for solving a programming problem and the meaning of compiler error messages with other students. You may not discuss specific pieces of program code with other students. A good check for this is that you must speak in standard English, not using source code phrasing when discussing assignments. You must write and type in your own code. You may not work with another student to write a piece of code and have each student turn in that code. You may not copy the file of another student and turn it in as your own work. If you receive substantial help from some source, e.g. a book, an instructor, or a fellow student, please acknowledge that collaboration.

    Home | | Requirements | | Syllabus | | Assignments | | Lectures

    Constance Royden--croyden@mathcs.holycross.edu
    Computer Science 131
    Date Created: August 10, 2000
    Last Modified: August 10, 2004
    Page Expires: August 10, 2005