Milestone 2.1: Project Plan

Task Breakdown:

• Research - 

  • What part of the Brain relates to stress?

  • What is the main cause of stress?

  • What is best to do with the stress information?

  • What do people usually do to deal with stress?

  • What is the metric of measured stress?

• Create a program that will clearly indicate stress level from the Open BCI device

Team Breakdown (Two Groups):

• • Software and Hardware Focused

    • Work on constructing the Open BCI

    • Work  on the software for the Open BCI

  • Research Focused

    •  Conduct interviews in the field

    •  Conduct research to figure out the relationship between stress, the brain, and brain activity

Project Plan:

• Month 1:

  • Project Site

  • Project Scope Assessment

• Month 2:

  • Problem Formulation

  • Solution Development

• Month 3:

  • Intellectual Properties

  • Abstraction and Modeling

  • Synthesis

Milestone 2.2: Concepts

Design Concepts:

• Form Factor - 

  • We know that Psyche will have sensors dedicated to detecting stress, but we are considering different housings for sensors.

  • Helmet (prototype): 

    • The helmet will be our initial proof of concept proving that the Psyche is capable of sending signals based on the helmet readings.

    • The helmet is too bulky and uncomfortable to be used in an actual product.

  • MVP:

    • Along with the helmet, we'll have the OpenBCI software that can measure and quantify stress.

  • Earpiece (alternate design):

    • We will try and fit the sensors from the prototype helmet into a smaller form factor so that seniors will find it more practical to use.

  • Helmet (alternate design):

    • Using electroencephalography, we will make the helmet more comfortable to wear and have the sensors be more compatible. 

Milestone 2.3: Concept Selection

Design Alternatives:

• OpenBCI Helmet

https://shop.openbci.com/products/d-i-y-neurotechnologists-starter-kit

• • Pros:

    • Gives the best balance of portability and hardware able to run the OpenBCI software

    • Adjustable sensor placement 

  • Cons:

    • It is not comfortable for long periods of time

    • Can be difficult to dial in adjustability

• EEG Cap

https://shop.openbci.com/products/openbci-eeg-electrocap?variant=16456881766472

• • Pros:

    • More comfortable than the helmet

    • Offers similar performance and cheaper than the helmet 

  • Cons:

    • Only has 19 out of the same 35 locations that the OpenCBI Helmet can sense

    • Limited in what size heads it will fit

• Earpiece

https://www.frontiersin.org/articles/10.3389/fnins.2019.00943/full

• • Pros:

    • Portability makes it easier to fit on more customers

    • Least intrusive out of all design alternatives

  • Cons:

    • Very expensive to fit OpenBCI technology into a small form factor

    • More prone to failure and inaccurate readings

• EKG Stickers

https://www.buyemp.com/category/ecg-ekg-electrodes/166

• • Pros: 

    • Hygienic, single use eliminates the need for cleaning the product

    • Stickers are cheap alternative to buying headgear

  • Cons:

    • Potentially inconsistent readings due to placement on the body

    • Stickers will not produce a reading if hair is in between skin and sticker

Milestone 2.5: Analysis

Hardware:

• OpenBCI Ultracortex 3D printed parts (PLA plastic)

  • Frame

  • Inserts

  • Board holder

  • Board cover

  • Wire clips

• Cables

• No. 6 Screws

• Spikey units

• Flat units

• Comfort units

• Ear clips

• OpenBCI 32-bit Board

• OpenBCI USB Transceiver

Software:

• OpenBCI GUI

• OpenBCI Python Library BrainFlow

  • Will  be used to create our custom program

Milestone 2.6: Test Plan

We will base our testing plan off of the V Development model as seen below.

This model helps with development working from a broad view and narrowing down to make a final product. The development model involves starting research from the top left, then narrowing down to coding.  Once we have completed the coding, we can test each component individually. Next would be to test how components interact with each other, then test them all as one system. The total system will be our software. Next is to test how the software interacts with the hardware. Finally, acceptance testing will take the form of interviews with more customers.