/back-end

Primary LanguageJavaScriptMIT LicenseMIT

back-end

PRODUCT VISION DOCUMENT

This is the template for the Product Vision Document that teams complete after their initial icebreaker. The PVD is crucial to the planning phase and is mandatory for all groups to complete and submit to their Project Lead before starting their project.

MEMBERS Data Engineering: Mason, Ping ML Engineering: Tatiana, Keanu Backend: Tate, Ous B Web Jonathan: Front-End WEB31 Juan: Front-end | WEB 29 Chris: WEB 30 Adrian: Front-End WEB31s

☝️ Proposal

What problem does your app solve?

Provides the strain needed based on users’ medical condition.

Be as specific as possible; how does your app solve the problem?

User is able to look up various strands, anonymously.

Gives user the dosage, intake method, and intake schedule.

What is the mission statement?

Provides users with an easy to use resource to make informed decisions about medical cannabis consumption, as an alternative to pharmaceutical drugs.

💡 Features

What features are required for your minimum viable product? Use data from a Strain API Using machine learning in order to make recommendations Ability to save recommendations. Ability to create a user (to login).

What features may you wish to put in a future release? Make a device app (where applicable)

What do the top 3 similar apps do for their users? Leafly - provides a link of conditions, based on link clicked, strain to help with condition. Potbotics - more of a personalized cannabis recommendation.

🛠 Frameworks - Libraries

What 3rd party frameworks/libraries are you considering using?

React, Redux, Node.js, Keras, Tensorflow, Flask

Do the APIs you need require you to contact them to gain access? In research - by monday 27 april Are you required to pay to use said API(s)? 🧮 For Data Scientists

Describe the established data source with at least rough data able to be provided on day one.

MVP - predict the types of strains someone would want based on their desires. 

Inputs - symptoms, emotions(happy, relaxed, etc), flavor
Outputs - strains/types, description 
Stretch: dosage, intake method
Find an API that provides us the data we need, in not use the Kaggle dataset with strains, types, and descriptions. 

Write a description for what the data science problem is. What uncertainty or prediction are you trying to discover? How could this data be used to find a solution to this problem? Prediction based on customer input Show existing Rating Basic visualizations about usage Customers that already try - ask for product/strain rating.

What kind of target output can you deliver to the Web/UX/iOS teams to work with? Is it in JSON format or something else? JSON format

🎯 Target Audience

Who is your target audience? Be specific. Individuals who seek an alternative to pharmaceutical drugs for treating their medical conditions.

What feedback have you gotten from potential users? Pharmaceutical prices are unaffordable for many, but some are uneasy about using cannabis as an alternative.

Have you validated this problem and your solution with a target audience? Describe how. Yes, a few members working this current project get medicated for various ailments/conditions.

🔑 Prototype Key Feature(s)

How long do you think it will take to implement these features? 5 days

Do you anticipate working on stretch functionality after completion of a Minimal Viable Product? Yes, hopefully to have MVP completed by the 29th

Stretch to be completed the following day.