Development specification
We wrote a basic project development specification document.
File for download
We must do (commitment; necessary technological minimum; part of the project documentation):
- web presentation (static page, information about the project, articles, photos...) about the project (info page)
- modern web application "SmartCook"
- database, records:
- raw materials (name, type, units, allergens, prices...)
- prices (guide price of the raw material for the given country, I would give the ISO code for the country id)
- recipes (name, description)
- recipe_has_raw material (in addition to FK, quantity and unit)
- about allergens
- about...
- generate recipes according to preferences for a few days in advance, including a shopping list
- generation filter (selection preference):
- about raw materials
- (yes and no)
- expiration of food (days until consumption?)
- quantity (value + unit)
- cost level (cheap, standard, luxury?)
- about diets (only deal with allergens yet?)
- by the number of servings
- about raw materials
- REST API (server side, JS, PHP, HTTPS, JSON...)
- GUI (web, HTML, CSS, JS…)
Czech do:
- Web presentation (status, fulfillment of articles)
- Web application (development, implementation, testing)
- We take pictures and film the progress of the work
- Workshops
Poles do:
- educational presentation of the gastronomy industry
- social networks
- recipes for the web application
- cooks/takes pictures of food
Comment:
- Do the minimum necessary, then deal with system expansion!
- Administration with user accesses and management is not required.
- No user management required. Maybe then in version 2.0.
- The recipe will be unit (default is one "standard" portion) and thus scalable.
- How to effectively insert recipes without administration? Use REST and JSON?
- Static elements to JSON, dynamic elements to relational DB.