Handing In Process
Ensuring that you hand in the correct pieces of information, in the correct format and to the correct location is critically important. If I do not receive it or receive the wrong items, I can not mark your work!
Use this template for all your assignments.
Here are the parts of the assignment you will be including:
- Cover Page
- this will include the course code, assignment # and your name
- Design Document(s):
- this might include Story Board(s), Top-down Design, Flow-chart(s), Pseudo-code, Class Diagrams, ...
- Test Cases:
- at least three (3) test cases (maybe more if it is needed!) done by some other method than your (or some else's) program
- the purpose of this is to ensure your program actually does what was required of it; you need to test your program against known solutions to prove it works, so you need to create these test cases before you start coding
- Screen Shots:
- screenshots of your running program
- you will include a screenshot for each test case you have from above, proving your program actually works
- Code:
- you must get ALL of the code into your document (in a logical order) as plain text and colored.
- GitHub link
- always include the "root" URL of your code. 1 repo per program per language.
If it is a two (2) week programming assignment do the following:
- Week 1, include the following in a single *.PDF, in this order
- Cover Page
- GUI
- Top-down
- Flowchart(s)
- Test cases
- Week 2, include the following in a single *.PDF, in this order
- Cover Page
- GUI
- Top-down
- Flowchart(s)
- Test cases
- Screen Shots
- Code
- GitHub repo