Here are the final requirements for turning in your final project. Remember, while successful projects with working code are appreciated, so are valiant efforts that didn't turn out quite as planned; be sure to pay special attention to documenting your journey if you believe yourself to be mostly in the latter category.
Note, as an explicit exception to many plagiarism rules, you are 100% absolutely freely allowed to copy-and-paste whatever you want from what you've written in your previous assignments in this class (or perhaps others) for this assignment, for the purpose of telling me what you did.
As with the proposals, you have some freedom with how you do the write up, but all of the following MUST be addressed.
- Name of project
- Personal goal(s): What is/was the *personal* goal(s) of your project? I.e., not necessarily what you wanted your code to do — but what did YOU want to do or get out of this experience? Frequently, this will come in the form of "write some code to do __" or "learn about __" (Remember SCOPE here, it may also be useful to tell me what you did NOT intend to do as well)
- Code goal(s)What is/was the goal of your code? What processes was it originally designed to execute? (Ditto on SCOPE)
- Name the Technologies (Languages, Frameworks, Libraries, Programs, Other people's code) you intended to use.
- In regard to any of the above — did these change over the course of your project, if so, how?
- Finally, give some conclusions. Tell me where everything ended up for you. Especially please include where you might go FROM here.
You'll need to provide me access to your code as well as any other code you used; along with a CLEAR indication of what you wrote/did vs. what was written by someone else. If there is a great deal of "intermixing" here, a decent way to accomplish this is to simply provide both your code and the code you used so I may compare.
Access: I'll need one or more of the following:
- If using "Torch" - the private path to your final project (doublecheck and confirm this works, please)
- If using the web, but NOT Torch — either internal access to the code, or a compressed (e.g. zip) copy of all of the code you're using.
- If not using the web; a compressed copy of the code you're using, or some other means to access the source. Git hosting works for this as well.
This is where I get to see your code "in action," if possible.
- If web based and using "Torch" — the public path to your final project. This should be a FUNCTIONING url. When I click on it, I should be taken easily to the project in action.
- If web based and not using "Torch" - either a url to the final project or an easily uncompressed copy that I can use myself. If mixing backend and and front end technologies (e.g. php etal) the URL is strongly prefered
- If not web based - I will need executable code in the form of a file or files, compressed.
If any of the above is unclear or (through my fault or yours?) or difficult or questionable to execute as presented, it is your responsibility to contact me before the deadline for clarification. Good luck and I very much look forward to checking out everyone's work!