Your final project is to develop some aspect for the BWI project.
You will be required to work in teams of 2-3 people each.
The schedule is as follows.
The proposal should be at least 3 pages double spaced. I prefer double-sided printing. Make sure you proofread and spell-check. It should be formatted similar to the papers we have been reading (i.e. with an abstract, sections, citations, etc.).The proposal should be written with the goal of convincing us that what you are proposing to do is interesting and non-trivial (though not necessarily completely original - see below). Connect the proposal to the class readings as much as possible. Team members should clearly identify what their roles will be with relation to the overall project.
The proposal will be evaluated on written expression , coherence of argument, and content. Please turn in one hard copy of the report at the beginning of class, and submit an electronic version via turnin (with grader shweta and hw name proposal) before class. Reports that arrive after that (including partway through class) will be considered late.
It is completely legitimate to propose to do something based on something you read about or based on open-source code. Just make sure to acknowledge any ideas (and code) that you borrow and be sure to clearly identify what you are going to do.It is also fully expected that your final projects may differ from what you propose. As you work on the project, you are likely to discover new ideas and approaches, realize some of your ideas will not work, realize your proposal was too ambitious, etc. Do not feel like your project has to exactly match your proposal.
The progress report should be at least 4 pages double spaced. I prefer double-sided printing. Make sure you proofread and spell-check. It should be formatted similar to the papers we have been reading (i.e. with an abstract, sections, citations, etc.).It should be written with the goal of convincing us that what you are doing is interesting and non-trivial, and that you are making progress towards your goal. It is expected that a good portion of the progress report will be identical to the proposal. Team members should clearly identify what their roles have been and will be with relation to the overall project. The progress report will be evaluated on written expression , coherence of argument, and content.
Please turn in one hard copy of the report at the beginning of class (double-sided printing is preferred), and submit an electronic version via turnin before class (with grader shweta and hw name progress). Reports that arrive after that (including partway through class) will be considered late.
You must turnin four items for your final project:
Final Report (Due Thursday, May 2nd at 12:30 pm)
Source Code (Due Thursday, May 2nd at 12:30 pm)
Demo Video (Due Friday, May 10th, at 5 pm)
Page maintained by Todd Hester
Questions? Send me mail