CS 3

Write a concise (one to two pages) description of the project you would like to execute. You will be graded based on the project rubric, so double-check that before handing in your proposal. In general, your proposal should include the following parts:

1. Claim: the specific hypothesis you plan to test (which is a statement, not a question) and some background context.
2. Data: a short description of your data source.
3. Programming Elements: number the steps of your analysis and list what programs and tools you will use for each (e.g. Spreadsheets/Excel or Python). You should also describe your expected milestones. You have about three weeks to complete this project. By the first week, you will have this proposal written and some start on the programming/data formatting. What parts do you expect to complete in week 2? What parts do you expect to complete in week 3?
4. Potential Roadblocks: a list of potential obstacles.
5. Interactivity: a description of how you will make your project interactive.
6. Visual Presentation: a description of how you will visually present your results for your website (e.g., table, chart, screenshot, etc.).

It is a good idea for you to include skeleton code in your proposal, but it is not required. Use what you've learned from the past two projects to organize your code early on. This will set you up for success as you finish your code and analysis.

• Skeleton code for Google Spreadsheets/Excel is a loosely-sketched-out workbook with descriptive spreadsheet names, column headings, and one or two text boxes on each sheet concisely describing the data that will appear in that sheet and how (in the abstract) it will be computed from data in other sheets. The leftmost sheet should contain a sketch of the public "take-homes" of your analysis or interactive elements, as well as a description of the other sheets. You should order the sheets so that the data in a given sheet will generally be computed only from sheets to its right. The rightmost sheets will contain raw data (though they don't have to be filled in in your skeleton version).
• Skeleton code for Python should follow the style guidelines described for Project 2, both in the original handout and in the feedback email that I sent. This means that every function should contain a documentation string describing its behavior, inputs, and outputs. Functions should be ordered in the file from highest-level at the top to lowest-level at the bottom — you should order them so that each function will generally only call functions that are positioned below it. The bodies of most functions in your skeleton code, especially the higher-level ones, should include calls to lower-level functions to demonstrate how the different functions use each other, as well as explanatory comments to describe things to be implemented or steps you will need to figure out.

Hand in the proposal (named YourName_FinalProject_Proposal.txt or LastName_Lastname_Project_Proposal.txt for pairs) and optional skeleton code similarly titled to cs0030handin@gmail.com with the subject "Final Project Proposal".

Refer to previous project descriptions and the project rubric for details about grading. Keep in mind that:

1. You must have a small test dataset or test spreadsheet showing that your calculations are correct.
2. You must comment all code (both in Spreadsheets/Excel and Python).
3. For spreadsheets, the first sheet must describe all other sheets. Input cells should be highlighted and instructions for use should be clear.
4. For Python files, comments at the top of the program should explain what the program does. Comments throughout the code should make your program easy to follow.

You will also create a website that presents your analysis and results. The site should be made publicly available as we'll compose a page of final projects. You may optionally restrict the access to just people with a Brown email address. The site should contain the following things:

1. Project description and hypothesis.
2. Concise explanation of your methods.
3. Your results, presented in a clear and informative manner.
4. Discussion of the trends you see in your analysis. You should point out expected and unexpected results.
5. Reflection of the project. What went well? What didn't?
6. Python/Spreadsheet/Data files available for download.

Create a zip file named FirstLast_FinalProject.zip or Lastname1_Lastname2_FinalProject.zip for a pair project. It should contain a folder that includes the following:

1. All files you used in your project, including Python files, Spreadsheet/Excel files, data files, and test files.
2. (Optional) A text document named supplement.txt with additional information (tests, analysis, etc) that did not make it on the website.
3. A text file named README that contains (1) the URL of your web page and (2) a list of all files contained in the zip folder with a short description of what they are.

Share the FirstLast_FinalProject.zip with cs0030handin@gmail.com.