Final Project
The climax of this course is its final project. The final project is your opportunity to take your newfound savvy with programming out for a spin and develop your very own piece of software. So long as your project draws upon the course’s lessons, the nature of your project is entirely up to you, albeit subject to the staff’s approval. You may implement your project in any language(s) as long as the staff approves. You are welcome to utilize any infrastructure, provided the staff ultimately has access to any hardware and software that your project requires. All that we ask is that you build something of interest to you, that you solve an actual problem, that you impact campus, or that you change the world. Strive to create something that outlives this course.
Inasmuch as software development is rarely a one-person effort, you are allowed an opportunity to collaborate with one or two classmates for this final project. Needless to say, it is expected that every student in any such group contribute equally to the design and implementation of that group’s project. Moreover, it is expected that the scope of a two- or three-person group’s project be, respectively, twice or thrice that of a typical one-person project. A one-person project, mind you, should entail more time and effort than is required by each of the course’s problem sets. Although no more than three students may design and implement a given project, you are welcome to solicit advice from others, so long as you respect the course’s policy on academic honesty.
Extensions on the final project are not ordinarily granted, except in cases of emergency.
Ideas
Here are just some of the possibilities. Discuss any and all with the the staff! And if you’d like to solicit collaborators for an idea you have, do post in Ed!
- a web-based application using JavaScript, Python, and SQL
- an iOS app using Swift
- an Android app using Java
- a Chrome extension using JavaScript
- a command-line program using C
- a hardware-based application for which you program some device
- a web-based application using Node.js
- a game using Lua with LÖVE
- …
Specifications
Extensions on the final project are not granted, except in cases of emergency.
Proposal
Gradescope will not allow you to see the questions or begin to work on your proposal until 2024-02-11T00:00:00-05:00.
due by 2024-02-17T23:59:00-05:00
The proposal is your opportunity to receive approval and counsel from the staff before you proceed to design. If collaborating with one or two classmates, make sure to include your groupmates in your Gradescope submission (this is the only assignment in the course where group submission is explicitly authorized, and you are allowed to submit in a maximum group size of 3.)
If part of a group, one group member (and only one!) should submit on behalf of all group members, being sure to include everyone as part of their “group submission” on Gradescope.
The staff will either approve your proposal or require modifications on your part for subsequent approval. Your proposal, even if approved, is not binding; you may alter your plan at any point, provided you obtain the staff’s approval for any modifications.
Projects submitted without approval will not receive credit.
What to Do
- Go to CS50’s Gradescope page.
- Select Final Project: Proposal.
- Answer all questions therein.
Status Report
Gradescope will not allow you to upload your status report until 2024-02-23T00:00:00-05:00.
due by 2024-02-28T23:59:00-05:00
Not only is the status report intended to keep the staff apprised of your progress, it is an opportunity to keep yourself on track.
If part of a group, one group member (and only one!) should submit on behalf of all group members, being sure to include everyone as part of their “group submission” on Gradescope.
What to Do
- Go to CS50’s Gradescope page.
- Select Final Project: Status Report.
- Answer all questions therein.
Implementation
Gradescope will not allow you to upload your final implementation until 2024-02-29T00:00:00-05:00.
due by 2024-03-06T23:59:00-05:00 There are no extensions or late submissions allowed, for any reason!
Ultimately due are implementation and documentation of your final project. Your submission thereof must include all of the below. If part of a group, one group member (and only one!) should submit on behalf of all group members, being sure to include everyone as part of their “group submission” on Gradescope.
- Documentation for your project in the form of a Markdown file called
README.md. This documentation is to be a user’s manual for your project. Though the structure of your documentation is entirely up to you, it should be incredibly clear to the staff how and where, if applicable, to compile, configure, and use your project. Your documentation should be at least several paragraphs in length. It should not be necessary for us to contact you with questions regarding your project after its submission. Hold our hand with this documentation; be sure to answer in your documentation any questions that you think we might have while testing your work. - A “design document” for your project in the form of a Markdown file called
DESIGN.mdthat discusses, technically, how you implemented your project and why you made the design decisions you did. Your design document should be at least several paragraphs in length. Whereas your documentation is meant to be a user’s manual, consider your design document your opportunity to give the staff a technical tour of your project underneath its hood. - Any and all files required to run your software (even if intended for some infrastructure other than cs50.dev), including source code as well as, if applicable, configuration files, Makefiles, sample inputs, SQLite databases, and so forth. Needless to say, all source code should be thoroughly commented.
- A short video (that’s no more than 2 minutes in length) in which you present your project to the world, as with slides, screenshots, voiceover, and/or live action, ideally with you yourself appearing in the video. Your video should somehow include your project’s title, your name, and any other details that you’d like to convey to viewers. See CS171’s tips on how to make a “screencast” though you’re welcome to use a phone or actual camera. Upload your video to YouTube as “public” or “unlisted” and include the URL of the video in your README.md file.
How to Submit
If part of a group, one group member (and only one!) should submit on behalf of all group members, being sure to include everyone as part of their “group submission” on Gradescope. Every member of the group should then confirm they see a submission on file for themselves on Gradescope.
If your project requires (for execution and testing) hardware or software other than that offered by VS Code, be sure that the the staff are aware of and have approved your project’s needs.
- Download a ZIP file of your final project. You could do so, for example, by running
zip -r project.zip *within your project’s folder in VS Code. Find theproject.zipfile in the file browser and right-click to choose Download. (If you created your final project outside of VS Code, you should still create a ZIP file of the project folder.) - Go to CS50’s Gradescope page.
- Click “Final Project: Implementation”.
- Drag and drop your ZIP file to the area that says “Drag & Drop”.
- Click “Upload”.
You should see a message that says “Final Project: Implementation submitted successfully!”
Trouble uploading to Gradescope? It suffices to submit your README.md and DESIGN.md by the deadline (which is absolutely required), so long as your README.md includes a link to your code files publicly accessible on, e.g., Google Drive, Dropbox, etc. We recommend you upload your project at least once, at least one hour prior to the deadline. Even if you make a subsequent upload later, at least you have a submission on file if something goes wrong with the upload at the last minute.
And that’s it; you’ve finished. This was CS50!