Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
# Project Title
> Team Member 1 (sunet1) [ ,Team Member 2 (sunet2) [, and Team Member 3 (sunet3) ] ]
## Overview
*This section should be on the order of a few (1-2) sentences. After reading this, we should have a general sense of your final project topic. You can imagine that this is the description blurb for your project if we were to make a CS41 Final Project Program.*
At a high-level, what do you propose to work on for your final project?
## Background
*This section should be on the order of a few (1-2) paragraphs. If your project is highly domain-specific, this section may be longer.*
Give us some context for your project. We may not be as informed about the topic as you are. Why are you excited about this topic? Do you have any experience with projects like this? What effects could this project have on the outside world?
## Implementation Strategy
*This section should be on the order of a few (2-3) short paragraphs, and captures your current program design.*
At a high-level, how do you plan to implement your project? How does it incorporate Python?
What are the main pieces that your projects breaks down into?
How do these pieces connect to each other? If they share data in some way, how?
Which Python packages do you plan to work with? How will these external modules connect to the code you write?
## Tasks
*This section is the most important because it gives us a sense of the scope of your project and forces you to think about the deliverables to which you'll hold yourself.*
Break down your project into a sequence of small tasks that you can feasibly accomplish to incrementally build towards a complete working project.
Include at least three stretch goals. A *stretch goal* is an extension that you think would be really awesome, but would probably be outside the scope of the final project.
What tasks do you think will be easy? What tasks do you think will be hard? Tedious? Trivial? Give us a sense of your current outlook on these project tasks.
Annotate each of the tasks (including stretch goals) with an estimate for how long you believe the task will take you. If you're in a group, also annotate each task with the names of anyone responsible for the task.
If you've already accomplished some of the tasks, make a note of it! If you're incorporating a final project for another class into this final project, you'll be held to a higher standard of quality and quantity, so make a note of that too.
This task list isn't binding - you can change your mind, modify tasks, etc - but it's a good starting point to organize incremental development.
## Resources
*This section is smaller and less vital than the others. If you're not using any external resources, you can leave this blank.*
What external resources will you be working with? If you are working with a dataset, how will you acquire the data set? If you're publishing some project (e.g. web app), how will you host your project? If your project requires hardware, how will you get it? Are there any other resources you need to acquire before starting?