|
|
|
|
|
The ideal proposal would
- be written in HTML and delivered as a URL which I could link to on the
class site. You can then update it as time progresses.
- List the group name and team members.
- state clearly the problem you are addressing and what you hope to
create as an artifact. Technically, you could satisfy this requirement with
a single sentence (and some groups did with the preproposal), but this time
I'm looking for much greater detail. If your project has a big UI
component, can you include a figure showing what it might look like? Can
you include an architectural diagram? The more detail the better, and of
course you can change your minds later.
- Break the project's development into (much) smaller chunks. Describe
each chunk thoroughly. What dependencies are there between the pieces? Can
you connect the overall project as a linked schedule or pert chart?
Estimate the estimate the time required to develop each chunk and sum up
the total time along critical paths. Who will work on each chunk?
Most likely, these plans will change as time evolves, but it is a very
useful exercise to plan it out anyway.
- Describe the series of milestones you expect to pass as a way of us
each being able to monitor progress at roughly 2.5 week
intervals. In order to be concrete, I suggest that you use the following
dates for your milestones:
- May 7 - milestone 1 due
- May 26 - milestone 2 due
- June 11 - no final exam; instead we will use the exam period for
oral presentations by all the groups, discussing what they
accomplished. Written reports and code are due electronically
before class with a stapled paper version of the report brought to the
class.
- if machine learning is involved in your project, describe where you'll
get your training (and testing) data
- explain how you will evaluate
success. What will you measure, how will you measure it, how will you
display it in the final report? (graphs are usually better than tables if
you can think of a good way to visualize the data)
|
CSE Home 
About Us
