Submission

Deliverables - Portfolio Report/Code due Monday 3/9 at 11:59 pm

The following components are required:

  • Report Your full report (10-15 pages) written document as a PDF and name it report.pdf. Do not turn in a Word Document, ODT, or plain text file.
  • Code All code and test files, including documentation.

All submissions will use Gradescope. Due to grading restrictions, we are unable to accept late submissions or resubmissions. If you are not done by the due date, you will need to submit what you have before the due date passes.

When submitting, we recommend making a zip file of your whole portfolio folder and submitting that to Gradescope so you only have to submit one file. Most operating systems come with a built-in feature to make a zip archive of a folder on your computer, so you should search how to do so on your computer.

Note: If you are using git to help manage your portfolio, please do not submit the hidden .git folder in your portfolio; one way to do this is to copy your portfolio files to another folder and make a zip of this new folder when you submit.

Report

Submit a roughly 10-12 page report documenting your findings. You should update any of the previous sections based on feedback from the Vision Statement.

Outline your report with at least the following sections (make sure to label your sections in your report):

  1. Title and author(s)
  2. Portfolio Narrative / Theme Same as Vision Statement, updated according to feedback.
  3. Selected Creative Work For each of your five revised portfolio pieces (including THA 4 and THA 5), include the following:
    • Brief summary of the assignment. What was the original task? What problem were you solving?
    • Design choices and revisions. Describe the key design decisions you made in your implementation. What approach did you take and why? What changes did you make from your original submission, and what motivated those changes? This should build upon and revise the written components from your original homework submissions.
    • Code quality improvements. Explain how you improved the quality of your code. Did you refactor for readability? Improve efficiency? Add better documentation? Be specific about what you changed and why.
    • Challenges and solutions. What challenges did you encounter while working on this piece, either originally or during revision? How did you overcome them?
    • Connection to portfolio theme. How does this piece fit into your overall portfolio narrative? What skills or concepts does it showcase?
  4. Challenge Goals Update Same as Vision Statement, updated with any changes made during implementation. If you find that your challenge goals have been scaled back, expanded, or changed since your proposal, explain those changes here, along with your updated plan for meeting the challenge goals.
  5. Revision Plan Evaluation Evaluate your proposed work plan. How accurate were your proposed work plan estimates? Why were your estimates close to reality or far from reality? What tasks still need to be completed, and how much time do you estimate you’ll need for them?
  6. Testing Describe how you tested your code and why you tested in that way to ensure your results were correct. Note that you are only required to include testing files if the original THA assignment required testing. If testing was not required for an assignment, briefly explain how you verified the correctness of your code (e.g., manual testing, output inspection, etc.). Make sure you tell us why we should trust your results!
  7. Conclusions and Reflections What did you learn by doing the work for your portfolio? Give at least two things you feel went well, two things that could have gone better, and two ways you might extend your portfolio in future work.
  8. Citations and Collaboration State the other people and/or resources that you consulted during the project aside from the course staff. These do not need to adhere to a formal citation style, but you should be consistent in your references!

Some additional formatting guidelines are as follows:

  • All visualizations must be captioned and titled AND be described or referenced in the body of the report. Make sure to explain how your visualizations were produced and contribute to the narrative. Any visualization which is not referenced in the body of the report should be excluded or moved to an appendix.
  • All pages must be numbered. If you choose to include a title page, it must also have the page number. All other headers and footers are optional.
  • The report must have the title report.pdf (exactly as such!) in order to be counted on Gradescope.
  • The report is not to exceed 15 pages. This is a hard limit, as even professional journals and conferences also have page limits! Not even one word or one line over! Optional title page and appendix do not count towards the 15 pages.
  • Do not single-space your report. Font size must be 11 or above. Beyond this, you are free to use whatever font, spacing, and margins you’d like.
  • You may choose to include additional information or references in an appendix that follows the report. There is no limit to how long your appendix may be, but its contents will neither be assessed for quality nor read in detail.

Code

Your code should meet the following requirements.

  • Your portfolio must be delivered in Python scripts (.py files). You are more than welcome to experiment and/or develop in a Jupyter Notebook, but your end result must be a runnable Python script to output all your results. Your portfolio should use the main method pattern for modules that can be run. Include the revised task description in your file header for each .py file. You will be submitting at least 5 .py files, one for each revised creative component. It is OK to put all of your testing code into the same .py file.
  • Your code must pass flake8 and should follow the CSE 163 Code Quality Guide. Your source code documentation can assume that the reader has already read your report — you do not need to repeat any of those details, but it doesn’t hurt to restate the highlights.
  • You must submit five separate Python scripts: tha1.py, tha2.py, tha3.py, tha4.py, and tha5.py, corresponding to your revised work from each respective Take-Home Assessment.
  • Any demonstrations of code output should use the main-method pattern for their respective Python module (e.g., running code in main for tha2.py).

Submissions and Grading

You will be graded on the quality and thoughtfulness of your report and code, so make sure you are giving adequate time to each section.

There will be no resubmissions or late work accepted since this assignment is a project component. Make sure that you are managing your time wisely!

Submit your work on Gradescope by 9 March 2026, 11:59pm PST. Make sure to include your report as a PDF titled report.pdf, and at least six Python modules (five for your creative work, and one for your testing file)! Do not submit Jupyter notebooks.

We will grade based on the quality of the code written, analysis done, and quality of the report overall. The following are not comprehensive but encompass the major areas in which your projects are assessed:

  • Does the report have all of the required components?
  • Is the report comprehensive and coherent?
  • Does the code meet the requirements and include appropriate forms of testing?
  • Does the code you wrote demonstrate a sufficient challenge from the perspective of our challenge goals?

Submit Report and Code