Overview | CS 367 covers data structures (including lists, stacks, queues, trees, graphs, and hash
tables) and their applications; the development, implementation and analysis of
efficient data structures and algorithms (including sorting and searching); and provides additional
experience in use of an object-oriented programming language (Java). |
---|---|
Prereqs | CS 302 or consent of instructor. Students are strongly encouraged to take CS 367 within two semesters of having taken CS 302. |
Enrollment Waiting List |
If you are waiting to enroll in CS 367, please attend the course during the first two weeks. As space opens, those on the waiting list will be invited to enroll. Invitations are sent to your @wisc.edu email address and your invitation will expire so please act quickly. Priority is given to those on the signup sheet passed out in lecture and based on any special circumstances that you list on that sheet. |
Course Accounts | Each student registered for the course has an account on the CS instructional Linux machines located in room 1350 of the Computer Sciences building. |
Course Resources | The material comes from many sources: lecture, the on-line readings, the course web site, and piazza. There is no required textbook for the course. |
Course Website | http://pages.cs.wisc.edu/~cs367-1
The CS 367 website is under construction for the fall semester. Some links might not work. |
Course Work | Grades are determined using the following breakdown:
|
Collaboration Policy |
Homework must be done individually. Collaboration on homework assignments is not allowed.
Programs can be done in pairs. You may have one partner for each programming assignment. Your partner must be currently enrolled in this course. You may not pair program with multiple partners on the same assignment. You may change partners on different assignments. |
Academic Misconduct |
Using someone else's work or allowing someone else to have access to your work in violation of the collaboration policy is academic misconduct and will be dealt with in accordance with University Academic Misconduct procedures. If you are not sure if something violates the collaboration policy, please ask me. Ignorance of what constitutes a violation of the policy is not a defense; it is your responsibility to know what is allowed/disallowed. |
Syllabus | The following is a tentative schedule of the topics to be covered:
|
Reminders |
|