Final Document

[Nick Berk]

Team-

So we need to figure out how the final document thing is going to work.

I think that we should send Rony a copy without a lot of the fluff. With that in mind, here are the sections I think we should complete:

1. Introduction

2. User Overview

3. Project Plan

4. Technology and Tools Used

5. Summary of Risks and Problems Encountered

I think we should put the bulk of our explanations in the "Design Decisions" section. For that, I think everyone should write a description of the front-end and the back-end of whatever code they wrote.

I'm unavailable Saturday, so I can't compile it if we want to turn it in after Friday. I'll commit to writing about my sections, and the Introduction.

Can everyone respond to 1) pick a section 2) confirm that they'll write about the work that they did and 3) commit to a time we'll have it done?

[Larry Hunt]

So, if I understood this correctly, I'll commit to Technology and Tools Used by video time tomorrow.

How much content, pages wise, are we looking at?

[Steven Caporaso]

I would prefer to do project plan. But open if someone really wants it. I can do something else

[Nick Berk]

Larry, that sounds right. 

Just do whatever you think is sufficient. Everyone is free to refer to last semester's final document (on Google Drive).

[Jason Philippi]

Dibs on Summary of Risks and Problems Encountered