EE 312 Projects

EE 312
Projects Page

Project Number	Due Date	Description
1	Friday, September 7, 9 pm	Code Camp - a warm-up assignment.
2	Monday, September 17, 11 pm	Song - procedural decomposition practice (worth 10 points, not the usual 20)
3	Tuesday, September 25, at 11 pm	Rocketship - practice with procedural decomposition, constants, and nested loops
4	Tuesday, Oct 2, at 11 pm	Transposition cipher - practice with arrays, strings and user input
5	Thursday, Oct 18, at 11 pm	String ADT - ADTs, dynamic memory, structs and pointers
6	Friday, Oct 26, at 5 pm	Polynomial Module - linked lists and dynamic memory
7	Monday, Nov 5, at 11 pm	Recursion - practice writing recursive functions in C
8	Tuesday, Nov 13, at 11 pm	C++ Startup - getting started in C++
9	Monday, Nov 26, at 11 pm	The Game of War - object-oriented programming
10	Thursday, Dec 6, at 11 pm	Binary Search Trees - the last project! (And there was much rejoicing!)

General Project Requirements:

Individual assignments are to be completed by you alone. You may not share code with other students or other programmers. Review the class policy on inappropriate collaboration in the class syllabus.

Follow the rules from the program style guide.

Until C++ is introduced in class, programs must be written in C.

You will have 4 free late (slip) days in 1 day units (1 second late to 24 hours late = 1 slip day) for the semester.

You may divide your slip days across the projects in any way you wish to extend deadlines for the projects except that you may not use more than 2 slip days on a single project, and you may not use slip days on the first or last assignment.
You may not use slip days to turn a project back in for a re-grade.
Weekends and holidays count as slip days. E.g., if an assignment is due on Thursday at 11 p.m., you must submit it by the next Saturday at 11 p.m. (in which case, you use 2 slip days.)
If you turn in a project late and do not have the required number of slip days, your project score is 0.

Projects must compile and run with gcc installed on the 64-bit ECE linux machines. The grader will compile and run your program from the command line.

Projects must be turned in via Canvas. You must turn in a file with the specified file name and in the proper format. The project page will specify exactly what to turn in.

If you fail to follow the instructions for turning in projects, you will likely lose all points. You must add the header and fill it in for every file you turn in or you may lose points. You may not use disallowed libraries, functions or programming constructs. You will lose points for doing so.

Projects will be checked for plagiarism and copying using Moss. You may discuss high level design issues with your fellow students, but sharing algorithms or code or obtaining solutions from another source constitutes academic dishonesty and will result in an F in the course.

The teaching staff will grade, comment, return and post the grade for an assignment within 6 days. A grade can only be disputed within the following 5 days. (This isn't a weekend bazaar. If there is an error in your grade, by all means, let us know. But your grade is not the starting point of a negotiation. We won't go back at the end of the term and re-grade early assignments.)

Please do not ask for a regrade lightly. Your grade could go down as a result of the regrade. Do not quibble over a few points. Regrades are serious issues. We will not change the way we awarded partial credit on an assignment as part of a regrade - that would be unfair to other students.

Please contact your TA if your assignment is not graded in a timely and accurate fashion.

All grade disputes must be made in writing by email to the grader with supporting evidence and will result in the entire assignment being regraded.