2018-12-18

posted Dec 18, 2018, 6:25 AM by Konstantinovich Samuel   [ updated Dec 18, 2018, 6:25 AM ]
Final Project Guidelines:

Pair Projects.
1. Choose a partner in the same period.
2. [Approval Required] Have a project proposal by Thurs Dec 20th.
3. DO NOT WRITE ANY CODE OVER BREAK. NO CODE WRITTEN OVER BREAK WILL COUNT.
4. [20 points] Your group must have 3 hard copies of a prototype by Thurs Jan 3rd (one to be submitted and one per group member). If it looks like you spent minimal effort, you will lose points.
5. Make a final project repo, add your partner as a collaborator. Make sure that every computer you use commits correctly. Look at the list of commits and see if your commits have your username + show your icon. ***OR YOU GET NO CREDIT***
6. [10 points] Your repo must have the following in README.md:
    -Instructions including how to compile, run, and use the program. (Updated before the demo and before the final deadline)
    -A development log that summarizes daily progress/changes/bugs. (Updated approximately once for every day you work)
7. [15 points] You must
    -commit regularly **starting after break**.
    -use proper commit messages.
8. [40 points] In class demo + Final Project
    -Your code should be readable
    -Include comments in your code
    -Proper variable/method names
    -Include good class heirarchy    

     
Total 85 Points.


Deadlines:
Dec 20th : 1-2 paragraph proposal describing what you plan to create.
Jan 3rd - Prototype due. (More details on requirements to follow)
    -Detailed Description of what you plan on doing
    -UML Diagram
    -Step by step plan which features to implement first
Jan X - Your Demo commit. This should be a working version of your final project, that you will improve upon over the next week. 
Jan Y - Your Final commit.

Presentations:
Jan X-? You will present the version you committed on Jan X (by 8am, you MUST make a demo branch to make it easy to pull. ) . I will clone everyone's demo branch. Please run through how you will demo beforehand. If you commit something that is UNTESTED, you will demo the untested code. TEST Your code as if you were going to demo it!


Types of projects:
Games are not prohibited, but I strongly urge you to consider something else for the 1st semester. 

Terminal Programs:
Easy:
Image Filters - Apply various effects to images.

Moderate:
Calculator - evaluate expressions, solve equations

Hard:
CSV editor - display the cells and let you

Games:

Easy text based games:
Board Games (not Monopoly/Catan)
Checkers
2048
Pacman

Moderate:
Chess for 2 human players (not computer AI)
Rogue-like game

Harder:
Tetris
NetHack

Text Adventure (Prohibited, generally they are poorly done and have too little structure)

To get keystrokes in the terminal:


Comments