1 Feasibility

While we will continue to tweak the Feasibility slide deck… our focus will now be on adding Design and Prototype Design materials.

2 Risks

The various risks straddle the line between Feasibility and Design.

While the Feasibility discussions have included Technical Risks… the focus was on

Can we even build the solution?

The focus during Design is on

We know these techical issues and difficulties will occur. What is the plan to address them?

3 Design

The Design materials will be a superset of slides (i.e., the Design slides will include all Feasibility slides). After recitation today:

1. Make all Feasibility updates discussed during recitation

2. Label the slides as “Feasibility Presentation” or “Feasibility” (title slide and footer)

3. Submit the slide deck URL under Final Feasibility Slide Deck Link in Canvas

4. Create a copy of the slide deck

5. Label the just-copied slide deck as “Design Presentation” or “Design”

6. Add the following slides to the new slide deck:

   1. Work Breakdown Structure - this is a visual breakdown of everything that will need to be built, set up, designed, or tested during development.

   2. Algorithms - a listing of the algorithms that your team will need to build (e.g., data scraping and analysis)

   3. Database Schema - a description of the data to be stored and the structure of that data

   4. Real World Product vs Prototype - a table listing the features that will be present in the Real World Product (RWP) and Prototype.

   5. Development Tools - a listing of the tools (e.g., Git) that your team will use to write, test, and run your code

   6. Required Libraries, Tools, & Technologies (Dependencies) - a listing of all existing libraries (e.g., NumPy, Pandas), languages (e.g., Python), frameworks (e.g., Flask or Django), and other technologies (e.g., MongoDB, PostgreSQL) that your project will utilize