A receipt scanning website to log purchases and track spending.
-A receipt scanning website to log purchases and track spending
Essential features:
-Essential features:
- Upload/scan a photo of a receipt and log purchases
- Upload/scan a photo of a receipt and log purchases
- Track and visualize spending
- Track spending over a certain period of time
- Personal Edition and Business Edition
- Visualize what you spent
Need and Value
**Need and Value**
- Consumers need a simple, free solution to track their spending
It’s going to be the same as other products but worse. It differs from other products
- Cross platform
because it is free and full of ads.
Businesses need a simple, free solution to tracking their spending
**Stakeholders**
- Low income families who want to track how much they spend
- Small companies that need to keep track on business expenditure
Stakeholders
**Quality Assurance**
We don’t have any stakeholders because nobody wants to be friends with us.
- We plan on using many industry standard QA techniques and software engineering principles
- Requiring Unit Testing to be written for all code
- Requiring Integration Testing for functions that work together
Quality Assurance
- Requiring System testing for all parts of the software working together
- Use the Agile method of software development
We plan on using many industry standard QA techniques and software engineering principles.
**Technology requirements**
- Electron
Technology requirements
- Frontend
- HTML/JavaScript/CSS
HTML/javascript/CSS
- Backend
Python: Django, tesseract OCR or tensorflow
- NodeJS
**Action plan**
Action plan
- For milestone 2, it was a group effort in coming up with an idea. After much deliberation and debate, we finally agreed (settled) on the aforementioned idea.
- For milestone 3 we plan on each group member brainstorming epics, personas and stories separately. Then we will meet and discuss them and compile them into a list or do some more brainstorming for more epics stories or personas. We will also familiarize ourselves with the technologies we will be using.
We all came up with ideas and they were all promptly shutdown so we have settled on a placeholder idea until we can settle our feudin’.
-**Expected completion date:** Friday January 24th
-**Expected hours of effort:** 2-4 hours per member
