COSC311 Algorithms and Data Structures
Last modified: "October 7 , 2008 13:30:27 by evett"
Final Exam: Thursday, December 11, normal time and classroom.
Textbook: Weiss, Data Structures and Problem Solving using Java 3rd
Edition, Addison-Wesley, 2006. Look for the 
symbols below!
Make sure you check out the course's Blackboard site: webct2.emich.edu.
Lecture Notes
- On-line demonstrations
of searching algorithms.
Assignments
To submit assignments, go to webct2.emich.edu. From there, go to our course's page. Click on the "Assignments" tab in the left-hand column.
Currently, all assignments are under construction. The ones shown below are
from an older version of this course. Some of them will be adopted to the current
course. I've left them here for you to peruse.
- Homework #1, due Thursday, 9/18.
- Program #1, Simple Priority Queues, due Thursday, 10/9, start of class.
- Homework #2, due Thursday, May 15. From Weiss: Exercises from chapter 7,
#1, 7, 8, 12, 16, 21. (16 is difficult!)
- Program #2, ShellSort, due Tuesday,
Nov. 18, start of class
- Extra Credit: Recursion, Find Groups, due Thursday, Nov. 20
- Program #3, Extending Weiss's TreeSet. Due Tuesday,
Dec. 9. Exercise 19.32.
Program #2, Queues, due Thursday, May
29, start of class
-
-
-
-
Notes on assignments, in general
See the page on Stylistic Requirements for
programming assignments, here.
Programming and other assignments should be completed
by each student on their own. It is expressly forbidden for students to
collaborate on assignments without the express permission of the
instructor. A few friendly pointers and a bit of advice is fine, but
"borrowing" or copying another's work is grounds for punitive action,
including a failing grade and possible expulsion from the University.
If, you want, you can instead download all the source code
with one click here. You'll have to decompress this file using WinZip, or a similar
utility. This will create a directory containing over 80 source code files.
Grading of programming assignments
As specified in the course syllabus, program functional correctness accounts
for only about 70% of the grade assigned to a program. The remainder of the grade
accounts for the program's style (including header and in-line comments, indentation,
identifier names) and design (how you decompose the solution, what classes you
use, etc.) A fuller description of stylistic and design
requirements is here.