MIME-Version: 1.0 Server: CERN/3.0 Date: Monday, 16-Dec-96 23:19:50 GMT Content-Type: text/html Content-Length: 10629 Last-Modified: Monday, 13-Mar-95 14:33:35 GMT CS 314 Course Information

CS 314 Course Information

Instructor

Teaching Assistants

Sections

Mon, 7:30 Upson 215, Evan
Tues, 3:35 Upson 211, Ulla
Wed, 7:30 Hollister 362, Sugata

Sections will be used to augment the lectures, present detailed examples, computer demonstrations, discuss problem sets and projects, and review for prelims. In addition, some required material will only be presented in section. Attend one section each week. You may attend any of the sections, regardless of your registration. However, it would be helpful if you attended the same section each week

Course Administrator

All routine administrative matters are handled by the course administrator, including petitions for regrade and misrecorded grades.

Prerequisites

CS 211 or equivalent. Students are expected to have programming experience using PASCAL or another procedural language, like C, Ada or Fortran. We will assume familiarity with recursion, arrays, records, pointers, linked data structures, and stepwise refinement.

Tutoring

The course TAs will be available during regular office hours for extended consulting help. Schedule an appointment by calling the undergraduate office at 255-0982 (Upson 303) at least 24 hours in advance. If you do not schedule an appointment, you may find the TA busy helping another student and, thus, unable to spend time with you.

Consulting

Consulting help will be available in Upson 305. Consulting hours are listed below.
------------------------------------------
Sun-Thurs  2:00 - 6:00 pm, 7:00 - 10:00 pm  
Fri        2:00 - 5:00 pm                   
------------------------------------------
Consultants will answer questions about the computer system, programs, homework assignments, and other things related to the content of the course. To help ensure that consulting time is used to best advantage, we ask you to observe a few ground rules:

Texts and References

Required

  1. Clements, Principles of Computer Hardware, Second Edition, PWS-Kent Publishers, 1991
  2. Motorola, M68000 Family Programmer's Reference Manual, Prentice Hall
  3. Ford/Topp, Macintosh Assembly System BasePak, D.C. Heath & Co.

Optional

  1. Patterson and Hennessy, Computer Organization and Design, Morgan Kauffman, 1993.
  2. Bartee, Computer Architecture and Logic Design, McGraw-Hill Book Company, 1991.
  3. Ford & Topp, Assembly Language and Systems Programming for the M68000, Heath, 1992
  4. Tanenbaum, Structured Computer Organization, Third edition, Prentice Hall, 1990
You are not required to buy the optional books. However, the book by Ford and Topp has an excellent presentation of assembly language programming for the M68000 family. Patterson and Hennessy is a good book for computer architecture. All books are available on reserve in the engineering library.

Handouts and Videotapes

Informational handouts and assignments will be distributed in lecture and section. Please do not lose them. Once the (limited) supply is exhausted we will not produce additional copies. Some copies of the handouts will be available outside Upson 303. The teaching staff will not have extra copies of old handouts.

The lecture will be videotaped. Copies of the videotapes will be placed on reserveand available for viewing in the Uris library media center. If you miss a lecture for any reason you are strongly encouraged to watch a video tape.

Requirements and Grading

This course contains two major projects. The first project involves writing a large program in assembly language. The second project involves design and implementation of a processor, using a gate-level design tool.

You should work in groups of two on the programming and hardware design projects except for the first programming assignment. When working in a group, submit for grading a single printout that includes the names of both students in the group. The same grade will be given to both students. I expect both students to be equally able to answer questions about the program or project. Written problem sets should be done individually.

Written problem sets should be turned in to either a CS314 consultant before the due date or at the beginning of the lecture on the due date. Students will be asked to demonstrate their programming assignements to a TA or consultant. Sign up sheets for project demonstartions will be available later. Late assignments will receive no credit, but partial credit will be given for incomplete work. If you cannot meet the due date of an assignment because of serious illness or other extraordinary circumstances, contact the the Course Administrator (Upson 303) before the assignment deadline for an extension.

Graded assignments will be returned by the consultants during consulting hours the day after the assignment is due. Graded exams wil be returned by the consultants during consulting hours two days after the assignment is due. You will need to show an ID to pick up an assignment.

Answer sheets for all homework assignments and prelims will be distributed one week after the assignment is due. These should be studied and understood. Homework questions have been known to reappear on examinations.

Grading and Regrades

Grades will be posted (indexed by a secret ID number you provide) across from Upson 303. If you believe that we have made a grading error, please first discuss the matter with one of the course consultants or teaching assistants. If, after such a discussion, it appears that a mistake has really been made, bring the error to our attention, but no later than one week after your assignment has been returned. To submit a problem set, program, or exam for regrading, obtain a regrade request form from one of the consultants or from outside Upson 303. Fill out the request form, and leave the request along with the assignment in question in Upson 303. A regrade request can cause your grade to go up or down. Regraded assignments will be returned by the course consultants.

Your course grade will be computed as follows:

------------------------------------------
20% (curve)     two prelims (15% each)      
10% (absolute)  homework                    
10% (absolute)  1st programming project   
20% (absolute)  2nd programming project   
10% (absolute)  1st hardware design project   
30% (absolute)  2nd hardware design project
------------------------------------------
Exams will be graded on a curve, homeworks and projects will graded on an absolute scale. Prelims will be on Thursday, March 2 in Upson B17 and Tuesday April 25 in Kimball B11 and will last 90 minutes. There will be no final.

Late homeworks will be accepted up to seven days after the due date, but each day an assignment is late will result in one "demerit." For every 5 demerits, a point value equivalent to one-half of a homework assignment will be deducted from your grade. For example, if you accumulate 5-9 demerits over the semester, points equivalent to one-half of a homework grade (1/2% of your total grade) will be deducted from your cumulative score, 10-14 demerits will result in one full homework grade being deducted from your cumulative score, etc. You can work off demerits by handing in assignments early. Each day an assignment is handed in early works off one demerit.

Academic Integrity

The work you submit in CS 314 is expected to be the result of your individual effort. You are free to discuss course material, approaches to problems, and details of the system with your colleagues, instructors, and Computer Services consultants, but you should never misrepresent someone else's work as your own. Permissible cooperation should never involve a student possessing a copy of all or part of another student's program or other work --- regardless of whether that copy is on paper or in a computer file on a hard disk or a floppy disk. The only exception to these rules is when two students work together to submit a joint project.

It is also the student's responsibility to protect his/her work from unauthorized access. For example, do not discard copies of your programs in public places.

Violation of the Academic Integrity Code very often results in failure in the course and permanent notations on your Cornell academic records. If you have any question as to what constitutes ethical behavior, ask the instructor first --- we will not be sympathetic to claims of ignorance or misunderstanding of the rules.

Back to the CS 314 home page