CSE logo University of Washington Computer Science & Engineering
 CSE 461: Computer Communication and Networks (Winter 2008)
  CSE Home   About Us    Search    Contact Info 

Course home
 Home
Administrivia
 Overview
 Using course email
 Email archive
Schedule
 Lectures and readings
 Section and tutorials
 Midterms and exams
Assignments
 Homework
 Projects
Lab information
 Getting lab accounts
 Unix tutorials
   

Course Overview

  Topics
  Grades

Exams

Homework

Projects

Policies


 
Topics

This course introduces the basics of networking, ranging from sending bits over wires to the Web and distributed computing. We focus on the internetworking ground between these two extremes, particularly focusing on the protocols and design aspects of the Internet. The goal of the course is to give you an appreciation of the fundamental challenges of networking, design strategies of proven value, and common implementation technologies. Topics will include: framing, error correction, packet switching, multi-access (Ethernet), addressing and forwarding (IP), distance vector and link state routing, queueing and scheduling, reliable transport, congestion control (TCP), quality of service, naming (DNS), and security.

back to top     


 
Grades

     I reserve the right to change this, but grades will be assigned roughly as follows:

  • Projects: 45%
  • Homework: 10%
  • Midterm: 20%
  • Final: 25%

back to top     


 
Exams

     There will be one midterm exam and a final exam for this course:
  • Midterm : TBA
  • Final : TBA

back to top    


 
Homework

There will be three kinds of homework assignments given throughout the class:
  • Reading: you will be given reading assignments from the course textbook associated with each lecture. You should finish the reading before coming to the lecture- I will assume you've done this reading, and my lectures will enhance the material, rather than regurgitating it.
     
  • Textbook-style questions: occasionally, I will assign written homework based on either questions from the text, or made-up questions. These assignments should be handed in at the end of class on the due date. (Make sure you read the late policy below.)
     
  • Extra-credit questions: from time to time, I may pose a question or give a programming assignment that is purely extra credit.

back to top    


 
Projects

As you've probably guessed from the allocation of grades, programming projects will be a major portion of this class. For this quarter, we will be using Nokia N800 tablet PCs and will be developing a peer-to-peer file sharing application on them. More information regarding the projects is available on the projects page.

back to top    


 
Policies

(Many of these policies are taken verbatim from previous instances of this course.)
  • Late Policy: unless otherwise indicated, assignments and projects are due by the end of lecture on their due date. If you hand in an assignment late, we will take off 20% for each day (or portion thereof) it is late. We will not consider granting Incompletes as grades.

  • Reasonableness: the "Reasonable Person Principle" applies throughout this course. This principle simply states that a reasonable request made in a reasonable fashion shall be reasonably handled by reasonable persons. The TA's and I are reasonable people: we expect that everybody else involved in this class will be as well.

  • Cheating vs. Collaboration: Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense. Please don't do it! Concern about cheating creates an unpleasant environment for everyone. If you cheat, you risk losing your position as a student in the department and the college. The department's policy on cheating is to report any cases to the college cheating committee. What follows afterwards is not fun.

    So how do you draw the line between collaboration and cheating? Here's a reasonable set of ground rules. Failure to understand and follow these rules will constitute cheating, and will be dealt with as per university guidelines.

    The Gilligan's Island Rule: This rule says that you are free to meet with fellow student(s) and discuss assignments with them. Writing on a board or shared piece of paper is acceptable during the meeting; however, you should not take any written (electronic or otherwise) record away from the meeting. This applies when the assignment is supposed to be an individual effort or whenever two teams discuss common problems they are each encountering (inter-group collaboration). After the meeting, engage in a half hour of mind-numbing activity (like watching an episode of Gilligan's Island), before starting to work on the assignment. This will assure that you are able to reconstruct what you learned from the meeting, by yourself, using your own brain.

    The Freedom of Information Rule: To assure that all collaboration is on the level, you must always write the name(s) of your collaborators on your assignment.

back to top   


CSE logo Computer Science & Engineering
University of Washington
Box 352350
Seattle, WA  98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX