Course Information

CSCI 466
Networks
Fall 2012

COURSE SYLLABUS

Description:

A study of the fundamental principles of computer based communication. Principles, design, and standards of networks will be discussed, including standard network protocols. Includes an introduction to telecommunications and basic data transfer processes. Prerequisite: CSCI 332.

Instructor:

Keith Vertanen

(406) 496-4385 (if I'm not in, send me an email instead of a voicemail)
Museum 102 (left of the main lab)
Office hours: Mon 3-4pm, Wed 2-3pm, Fri 2-3pm, or by appointment.

Classes:	Monday	1:00 - 1:50pm	lecture	Health Science 001
	Wednesday	1:00 - 1:50pm	lecture	Health Science 001
	Friday	1:00 - 1:50pm	lecture	Health Science 001

Resources:	Textbook	Computer Networking: A Top-Down Approach (6th edition) by James Kurose and Keith Ross
	Class web page	http://katie.mtech.edu/classes/csci466/
	Moodle for grades and assignment submission	https://moodlemtech.mrooms3.net/course/view.php?id=6004
	Booksite	http://wps.pearsoned.com/ecs_kurose_compnetw_6/216/55463/14198700.cw/index.html

Evaluation:	Midterm	15%
	Final	25%
	Assignments (programs, labs, presentations)	60%
	Staff discretion (participation and extra-credit)	±?%

Assignments and late policy:
Assignments will consist of written exercises/labs, programming assignments, and presentations. The exact details of how and when to submit an assignment will be stated in the assignment description. Your programs will be graded on correctness, programming style (including comments), and efficiency. Partial credit is possible so if you run out of time, submit what you have.

You get a total of four free late days which can be applied to written or programming assignments. Each late day buys you a 24-hour extension to the submission deadline. If you are out of free late days, any further late submissions will be given a zero. In the case of a group assignment, the group only has as many free late days as the minimum of any member of the group.

Academic honesty:
Cheating will not be tolerated and can result in failure of the course. Submitted programs must be entirely your own work (except for designated group assignments). Under no circumstances should you copy another person's code. Exams are to be strictly your own effort. Unless specified, no electronic devices are allowed in exams.

General:
Any student who may need an accommodation due to a disability, please make an appointment to see me during my office hours. A letter from a Montana Tech Disability Coordinator authorizing your accommodations is needed.

Expectations:

E1. Students have implemented advanced data structures (hash table, balanced search tree, and a graph) using OOP design in a high level programming language and used them in simple programs. (CSCI 332)
E2. Students understand the syntax and semantics of programming languages and can formally describe portions of a programming language's syntax and semantics. (CSCI 305)
E3. The student can write short papers reviewing technical topics. (WRIT 101)

Course Outcomes:

R1. Students demonstrated conceptual knowledge of the traditional IETF networking protocol stack. (CAC-i; EAC-k)
R2. Students described common internet protocols and chose the appropriate protocol and protocol level when designing networked applications. (CAC-a, i, j, k; EAC-a, e, k; SEC-1, 2)
R3. Students designed simple client/server applications that used the TCP and UDP protocols. Students implemented these designs in a high-level programming language, such as C, C++, or Java. (CAC--a, i, j, k; EAC-a, e, k; SEC-1, 2)
R4. Students expressed a conceptual understanding of networking and their solutions for common applications through well organized and documented presentation. (CAC-f; EAC-g)
R5. Students demonstrated a conceptual understanding of application-level networking problems and their solutions for common networked applications such as remote file systems, RPCs, electronic mail, and applications that use the World-Wide Web. (CAC-i, EAC-k)
R6. Students demonstrated knowledge of how the Internet is constructed, physically and logically, and how high-level user actions in networked applications are mapped to concrete low-level data representations over networks. (CAC-i, EAC-k)

Page last updated: December 26, 2012