| This page last updated on: Oct 01, 2001 Contents and Related Links |
Note - Most of this page is oriented towards the C++ courses rather than the FOOAD (Foundations of OO Analysis and Design) course. The FOOAD syllabus has instructions for submitting assignments. Assignment Source Code Standards ConformanceAssignments are required to be written in standard C++ conforming code (with few exceptions). (After many years of assignments that did not compile due to compilers that support older non-standard behavior, this requirement was put in place as a matter of self-preservation.) If the assignment does not compile, it might be returned to be modified before any grading is performed. Besides instructor convenience, there are many good reasons to know how to write standard conforming code, as well as the issues and tradeoffs associated with code portability and standards conformance. With few exceptions, it's not hard to write code that will compile on multiple compilers -- here's a list of compiler tips and non-conformance workarounds, particularly MS VC++: C++ Compiler Tips
Assignment SubmissionAll programming homework is to be turned in either by e-mail (highly preferred, as this allows additional programming help and support to be made between class sessions), or on a 3.5" floppy, DOS formatted. If you wish to turn in a printout as documentation, it is gladly accepted, but will not count as the assignment. For submitting assignments through e-mail, please attach the source code files (zipped or tarred, if possible) to the e-mail message rather than including them directly in the message (unless there's no other choice). Creating a zipped file (using a utility such as WinZip or PKZIP or the built-in facilities in Windows ME) or creating a tar file and attaching the zipped or tarred file is by far the most convenient way for both students and the instructor. Mime, Uuencode, and BinHex all work fine as attachment methods. Send only the source code (and associated test data files, if appropriate), not object code, or project directories. Specifically, do not include any executable files ('.exe') - the main reason is that I've received viruses from students (accidentally sent from an infected system), requiring me significant hours to reformat and rebuild my hard disks. A secondary reason is that executable files tend to be large and take a long time to download. It is recommended that the email have as its subject your name, followed by the word “Assignment” and the assignment number, or by the phrase “Final Exam”, depending on which item you are submitting. It is also suggested to send a test e-mail with a zipped attachment early in the quarter to verify correct operation though e-mail application and ISP. Extra credit and makeup assignments are encouraged, as well as resubmitting assignments that have been improved and enhanced. For planning purposes, please talk to me in advance before performing any extra credit or makeup work. C++ courses - name the source files as required in the assignments - the
assignment may be returned to you with a request to rename the source files
if you do not follow the requirements. However, individual style choices
are encouraged within the source code (e.g. class and variable names), as
long as a consistent and intuitive approach is followed. Grading80% required for SC, per UW Extension Certificate requirements.General assignments and project work (C++) will be graded with the following guidelines:
|