|
|
CMPT370 Milestone 2
|
|
|
|
|
|
|
|
|
Product Description
|
|
|
|
|
|
* Provide a brief description of the product and identify the essential product features
|
|
|
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
|
|
|
|
|
|
* Describe the opportunity for the product, its value, and why it differs from what is currently available
|
|
|
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.
|
|
|
|
|
|
* A stakeholder is someone that a vested interest in the product. Some stakeholders never interact with the system but will care how the system behaves
|
|
|
|
|
|
Quality Assurance
|
|
|
|
|
|
* Initial ideas on how you will ensure that you produce a quality and useful product
|
|
|
We plan on using many industry standard QA techniques and software engineering principles.
|
|
|
|
|
|
|
|
|
Technology requirements
|
|
|
|
|
|
* Identify technology needs both for your development and for the deployed product as best you can at this state in the project.
|
|
|
HTML/javascript/CSS
|
|
|
Python: Django, tesseract OCR or tensorflow
|
|
|
|
|
|
|
|
|
Action plan
|
|
|
|
|
|
* Provide a list of who did what for this milestone, and who will work on what for the next milestone. At this stage, most activities will be group activities. Provide expected dates of completion and expected effort in hours. |
|
|
\ No newline at end of file |
|
|
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’.
|
|
|
|