|
|
CMPT370 Milestone 2
|
|
|
**CMPT370 Milestone 2**
|
|
|
|
|
|
|
|
|
Product Description
|
|
|
|
|
|
A receipt scanning website to log purchases and track spending.
|
|
|
Essential features:
|
|
|
**Product Description**
|
|
|
- Product Name: CrabMyReceipt
|
|
|
- A receipt scanning website to log purchases and track spending
|
|
|
- Essential features:
|
|
|
- Upload/scan a photo of a receipt and log purchases
|
|
|
- Track and visualize spending
|
|
|
- Personal Edition and Business Edition
|
|
|
|
|
|
Need and Value
|
|
|
|
|
|
It’s going to be the same as other products but worse. It differs from other products
|
|
|
because it is free and full of ads.
|
|
|
Businesses need a simple, free solution to tracking their spending
|
|
|
|
|
|
|
|
|
Stakeholders
|
|
|
|
|
|
We don’t have any stakeholders because nobody wants to be friends with us.
|
|
|
|
|
|
|
|
|
Quality Assurance
|
|
|
|
|
|
We plan on using many industry standard QA techniques and software engineering principles.
|
|
|
|
|
|
|
|
|
Technology requirements
|
|
|
|
|
|
HTML/javascript/CSS
|
|
|
Python: Django, tesseract OCR or tensorflow
|
|
|
|
|
|
|
|
|
Action plan
|
|
|
|
|
|
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’.
|
|
|
|
|
|
- Track spending over a certain period of time
|
|
|
- Visualize what you spent
|
|
|
|
|
|
**Need and Value**
|
|
|
- Consumers need a simple, free solution to track their spending
|
|
|
- Cross platform
|
|
|
|
|
|
**Stakeholders**
|
|
|
- Low income families who want to track how much they spend
|
|
|
- Small companies that need to keep track on business expenditure
|
|
|
|
|
|
**Quality Assurance**
|
|
|
- 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
|
|
|
- Requiring System testing for all parts of the software working together
|
|
|
- Use the Agile method of software development
|
|
|
|
|
|
**Technology requirements**
|
|
|
- Electron
|
|
|
- Frontend
|
|
|
- HTML/JavaScript/CSS
|
|
|
- Backend
|
|
|
- NodeJS
|
|
|
|
|
|
**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.
|
|
|
|
|
|
- **Expected completion date:** Friday January 24th
|
|
|
- **Expected hours of effort:** 2-4 hours per member |
|
|
\ No newline at end of file |