FSU Seal - 1851 Course Calendar
COP 4530 Data Structures, Algorithms, and Generic Programming
Spring Semester 2005
Root View: Course Components
Syllabus The course syllabus establishes course policies on grading, attendance, and exams. The syllabus should be read in detail at beginning semester.
Lectures This is the main knowledge resource for the course. Lectures are in the form of a slide show with an accompanying narrative. (Click "Narrative on" to see the narrative. Click "Frames[Windows]" to toggle between displaying the narrative in a separate frame or a separate resizable window.) Please report bugs/corrections in the appropriate Blackboard discussion forum. Note: The lecture notes are undergoing revision during the semester.
Assignments Assignments will be released here. You need the specific file name appended to this URL.
My FSU The FSU/Blackboard Portal, where you will find this course. The course site is the main communication resource for the class. Here you can get help, talk to other students, retrieve your grades, and generally keep up with course news and announcements.
Extras: Miscellaneous Resources and References
COP 3330 The lecture notes from the pre-requisite course
Make A tutorial on the make utility and makefiles
E1 E2 E3
E4 E5 Midterm04 		Some old exams. Note that students are encouraged to discuss these exam questions on Blackboard, where a forum has been set up for the purpose. Please don't ask instructors to participate or for individual help on them.
MazeBuilder A nifty JavaScript maze accessory by Isaac Olson. This application requires Internet Explorer 6.0 or higher.
01_06_05
01_13_05_A
01_13_05_B
01_20_05_A
01_20_05_B
01_27_05_A
01_27_05_B
02_03_05_A
02_03_05_B
02_10_05_PWServer
02_17_05_Deques&ADTS
 Podcasts by Josh Simmons: mp3 files from in-class discussions
Temporal View: Course Calendar
WeekDatesCoverageAssignmentsDue Date
1 1/5 - 1/9 Chapter 1: Introduction
Reviews and Background 		Homework 1a: Unix and Emacs
Homework 1b: Building Projects
 1/16
1/16
2 1/10 - 1/16 Chapter 2: BitVectors
Chapter 3: Strings 		Homework 2: Sieve of Eratosthenes 1/23
3 1/17 - 1/23 Chapter 4: Hashing
Chapter 5: Templates 		0 NA
4 1/24 - 1/30 Chapter 6: Vectors
Text: 3.1-3.5 (optional) 		Project 1: Password Server 2/13
5 1/31 - 2/6 Chapter 7: Algorithms 0 NA
6 2/7 - 2/13 Chapter 8: Lists
Text: Chapters 6, 9 (optional) 		Project 2: RingBuffer 2/27
3/6
7 2/14 - 2/20 Chapter 9: Deques 0 NA
8 2/21 - 2/27 Chapter 10: Abstract Data Types
Text: Chapter 8 (optional) 		Project 3: The Rat Pack 3/20
3/27
9 2/28 - 3/6 Midterm Exam: See Syllabus for details
9 3/7 - 3/13 Spring Break
10 3/14 - 3/20 Chapter 11: Function Objects
Chapter 12: Iterators
Chapter 13: Generic Algorithms
 Homework 3: Function Objects and Generic Algorithms 3/27
4/3
11 3/21 - 3/27 Chapter 14: Generic Set Algorithms
 0 NA
12 3/28 - 4/3 Chapter 15: Tables
 Project 4: Internet Router 4/17
SUN 4/24
13 4/4 - 4/10 Chapter 16: Heaps
 Homework 4: Priority Queues 4/24
FRI 4/29
14 4/11 - 4/17 Project Work 0 NA
15 4/18 - 4/24 Review 0 NA
16 4/25 - 5/1 Final Exam: See Syllabus for details
17 5/2 8:00 AM: Grades Turned In To Registrar

Unix Script Submission Process:

Most programming assignments will be submitted via a specific Unix script from your CS Majors account logged in to shell.cs.fsu.edu. Submission scripts will be located in the directory ~cop4530p/spring05/submitscripts/. Availability of these scripts will be announced in the assignment document.

Submission via script should generate two email responses:

  1. When your submission is received, a receipt is sent via email. The date/time stamp of this email is the official submission time.
  2. After your submission has been unpacked and placed in your portfolio, a second message is sent containing a copy of all files that were unpacked. This is a record of exactly what was received and placed in your portfolio.

After submission, be sure to check your email for these two messages. Normally these would arrive within a few seconds of submission. If you do not get both email responses, a malfunction occurred. When you do receive these confirmation emails, save them. If a problem were to arise with your files, these emails are your proof of submission.

Note that revisions may be submitted any time prior to the deadline and will automatically replace the previous submission.