CSE logo University of Washington Department of Computer Science & Engineering
 CSE 143 Autumn 2002 -- Homework Policy
  UW Home     CSE Home   Announcements    Message Board    Contact Info 

CSE 143
 Home page
 Syllabus
Classwork
 Calendar
 Homework
 Exams
People
 Instructors
 TAs
 Consultants
 Consultant Schedule
 Pictures
Software & Computing
 Programming Lab Info
 Using BlueJ
 Computing at Home
 Java Libraries
Staying in Touch
 Mailing Lists
 Discussion Board
 Announcement Archive
   

CSE142/143 Homework Submission Policy

These policies generally apply to all programming parts of homework assignments. However, particular assignments may have specific instructions, which take precedence over these. Deadlines and procedures for other parts of homework assignments or other assignments will be announced as necessary.

Web submission cut-offs are given in the instructions for each homework.

Submission of written/printed material is at the beginning of class period (lecture or lab, depending on the assignment).  Loose pages should generally be stapled together (and there won't necessarily be a stapler available in class!).  To ensure prompt grading, clearly label your work (for example, the first page for lecture submission) with the following information in really, really big print:

  • course title ("CSE 142" or "CSE 143")
  • name
  • homework number (e.g. "Homework 2, Problem 1 or Part A")
  • TA's name (very important!)
  • quiz section (usually two letters)

You may lose points if you do not follow these instructions.

Barring exceptional circumstances, web submission of homework will not be accepted after the cut-off time specified in the instructions for the homework.  Web submissions will be accepted but marked as late for a few minutes after the due time, to take into account small differences between clocks, but will stop working soon after. 

Even though late homework is not accepted, you are still encouraged to complete all assignments as a learning experience, and may ask your TA if s/he has time to discuss them with you, even if you cannot receive credit.

Explanation of Turn-In Mechanism

When you submit your program using the turn-in mechanism, we immediately compile it using Sun's JDK compiler.  The compiler warnings and errors, if any, are copied into the "receipt" page.  If you see compiler errors, your program did not compile with our compiler.  It is your responsibility to figure out why, to fix your program so that it will compile, and to go through the turn-in procedure again.

For many assignments, you will be expected to print the receipt and hand it in.  Once you leave the receipt page, there is no way to recreate it.  Print the receipt while you have it on the screen, or save it to a file.

Testing and Running Your Turned-In Program

Your program is generally not run at the time you turn it in.  Instead, we may run it later, while grading it.  You won't know in advance what test cases may be used for grading.  So test your program carefully, on a variety of cases.  On occasional, the grading may be based all or in part on an examination of the source code and other materials, without executing it.  In other case, you may be asked to perform a personal, live demonstration, or to answer questions in person about the program's operation, organization, and contruction.

Team and Group Projects

Some homework assignments may permit or require students to work together in small groups.  Generally, only one person from each group will perform the turn-in.  All group members will receive the same score, except under unusual circumstances.  On some occasions, each member of the group may be asked to do some task individually, or turn in some part of the project individually. 


CSE logo Department of Computer Science & Engineering
University of Washington
[comments to cse143-webmaster]