Your final project for this course is either a game or visualization that shows off what you’ve learned over the entire semester. It will be scored against the course learning objectives, as with our other assignments.
|Rough Draft Due
|Peer Feedback Due
|Last due date for feedback on project
|3/15 by 5:30 PM
|Final Draft & Reflection Due
At any point between these deadlines please feel free to come see me to get additional feedback on your final project, so long as it is before the final feedback date (3/9).
The final project is meant to be a culmination of all of the skills you have learned in this course, so that in the future you can quickly and easily demonstrate the skills you have mastered by presenting this project. Therefore, your project should contain all of the following:
- L1: Basics: Your program should contain:
- Conditional statements and loops
- Functions you have written yourself
- Some data storage structure (lists, tuples, dictionaries)
- L2: Data Processing: Your project should process both external files and user input.
- L3: Debugging: Your program should be free of errors, and should handle user-input errors gracefully (e.g. with a message).
- L4: Style: Your program should be well-commented and use organized functions.
- L5: Code Review: You will be asked to give peer feedback to your classmates’ projects; you should complete this peer feedback for credit.
- L6: Collaboration: Your project should be uploaded to GitHub, where you should be able to see changes between the draft and final version.
- L7: Reading: You should have a
.READMEfile in your repository that explains what your project does and how you created it.
- L8: Reflection: You will be asked to submit a final reflection with your project.
If you hit all of these points, you’ll be given full mastery credit. 5-7 will be given Proficiency, and less than 5 will be given Novice.
Types of Projects
You have two choices for what kind of final project you’d like to create.
Option 1: Game
The first type of project is a computer game. Your game should incorporate some level of actual AI decision making. By this, I mean that the computer should play against you or manage your game in a moderately intelligent way. The computer doesn’t have to be that good at it, really! But you should make a concerted effort on this front, meaning that your AI will go above and beyond a simple random strategy.
Your game can include a true graphic interface, or it can be a terminal-based ASCII program, but should include some degree of feedback for the user.
Remember that your time is limited, so pick a game that you will be able to implement between now and the end of the term.
Option 2: Data Interaction
The second type of project is some type of interactive database or data visualization. By “interactive”, I really just mean that the user can choose what kind of data should be displayed. It is up to you how to display this data and what kind of data you want to work with, with the caveat that your data should be from some publicly available source.
We do not cover visualization methods in great depth in this class, so you may have to do some outside work to find your preferred method of visualization. Instead of visualization, you can also create an interactive database as below in the examples. I’m happy to discuss some options with you!
Proposal and Draft
I will require that you turn in a project proposal and a project draft. The proposal will only go to me; the draft will go to your peers.
The project proposal is a simple, ~100 word explanation of what you hope to accomplish for your final project. It should include, at a minimum:
- What game or visualization you intend to make
- What you hope the project will be able to do
- What external modules, packages, or data you think you’ll need to complete this project (does not have to be exhaustive)
- What uncertainties you have about the project
Below is an example:
For my project, I am going to create a “hot or cold” style game where people will have 10 chances to guess a US state. They will first put in a state name as a guess. Then if they are wrong the program will tell them if they are “Freezing”, “Cold”, “Warm”, or “Hot”. When they’re right the program will say “Congratulations!” and print out a picture of the state. For this project I don’t think I’ll need any external packages but I will need some pictures or ASCII templates of the states. I also need some way to tell how far their guess is from the state that is the right answer so I can figure out whether it’s hot or cold. I need some help figuring out how to measure that distance.
I will only accept late proposals up to Monday, 2/13. If you need an extension beyond this, you must contact me or you will get an “Incomplete” for this assignment.
The project draft does not have to be a completed version of your project, but you will only receive peer feedback on what you submit.
This must be turned in on time (end of the day Thursday, February 23). Note that this cannot be turned in late because your peers must have ample time to submit their peer reviews.
This lab will be turned in as a link to a GitHub repository; all the code you have written for the project should be uploaded to the repository. If you started writing your code without first making a repository, you should:
- Create a new repository on GitHub.
- Clone the repository to your computer.
- Copy your files from wherever they are located on your computer into the newly cloned GitHub repository.
- Add, committ, and push the changes to GitHub.
Specifications: Peer Review
You will be asked to review two of your classmates’ project drafts and give feedback on their design and implementation. This will come in the form of a pull request on GitHub.
You have been assigned three project drafts; pick any two to review. You will get full credit for reviewing two. You can review all three if you wish to see some more drafts.
To complete your peer review, do the following:
- Fork your assignee’s repository.
- Clone the forked version to your computer
- Try things out. Make comments about anything you don’t understand; you can even make changes to the program if you have an idea of what to do differently. The important thing is that you change the file in some way, either with a comment like “I’m not sure what’s going on here” or “you could use a dictionary here instead of two lists” or something similar. This part is freeform.
- Add, commit, and push the changes to GitHub.
Make a pull request to merge back into your assignee’s repository. In the longer comment box for the peer review, answer the following questions.
- How readable did you find the code? How easy was it to figure out what was going on or what the code was intended to do?
- What was something you found well-done about the code? Something you feel would be a strong place to build from, either already implemented or an idea of an implementation?
- What was something you think could be improved and do you have an idea to improve it?
This constitutes your peer review.
This must be completed on time (before lab on Thursday, March 2). Note that this cannot be turned in late because your peers must have ample time to revise their projects given your feedback.
Your final reflection is a reflection of both your project and the course. It is a short piece of writing that gives you room to reflect on your intro programming journey.
It is not scored, but you will get feedback and it will help me put your semester into context!
- 1 to 2 pages, single spaced ( >= 500 words)
- PDF or Markdown
- Due with your final draft of the project
You do not have to answer all or even any of the following questions; they’re just a guideline for what I’m hoping you get out of this reflective portion.
- What grade do you expect to receive in this course? Do you feel like that grade is an accurate reflection of your learning? Why or why not?
- What was the process of completing a final project like? Is there anything you wish you’d done differently? Anything you’d add or change if you had another week to work on it? Anything you’d subtract?
- How did the mastery-based grading style of the class impact how you approached the homeworks and labs? Or did not really impact you at all?
- Was there a time in this class when something finally “clicked” for you after struggling with it for a while? What made it click?
- What can you take forward from this class to other classes? This could be something concerete you learned, an approach that you tried, or something that didn’t work at all that you’ll consciously avoid next time.
- Anything else you want to write about that will place your work into context for you and for me.
Your project will be turned in as a GitHub repository. Your project will be evaluated on the version of the project that is on GitHub at 5:30 PM Central on March 15, 2023. For legal reasons, I cannot accept work past this date and time.
If you want to turn in an earlier draft of the project to receive feedback, you can let me know at any time prior to 11:59 PM on 3/9. This is your last date to receive feedback from me on your project before its final evaluation.
Your GitHub repository should:
- Have a README.md which outlines the following:
- What your project does (the game, visualization, etc) in 1-2 sentences.
- What outside tools (modules, packages, datasets) were used to create your project
- What contributions you made to the project in 1-2 sentences
- Have instructions for how to download and run your project, or instructions on how to run your project if web-hosted
- Contain all the code necessary for someone to download and run your project on their own computer without going to any outside source (besides possibly installing python or python modules)
Here are some final project repositories from past years.
- PacMan by Gabriel Gomes (Fall 2022)
- Coin Pickup by Kaylee Wu (Fall 2022)
- Password Math by Annika Urness (Fall 2022)
- ATU Fairytale Index by Emmeth Murphy (Fall 2022)
Portions of this document are taken from Dr. Anya Vostinar.