The following is a prioritized list of design goals for the Qookie database.
The following is a list of things that are not required by the Qookie database.
The database is implemented through a middleware layer, in order to abstract the physical database access away from the data itself.
This is also done in order to make porting the data storing to other databases an easy task.
A component is the super class of all data components in Qookie. It contain all common attributes:
| ||Integer||A unique number defining this component.|
| ||String||The name or title of the component.|
| ||String||A short description of the component.|
| ||Binary||An image of the component.|
A named sequence of text blobs or images with a text blob, containing the atomic steps in a preparation procedure.
A basic ingredient, such as flour, an egg or a tomato.
An ingredient is made out of the following attributes:
| ||Unit||The unit in which the ingredient is measured|
| ||Season||The season in which this ingredient can be acquired.|
| ||Integer||The usual quantity in which the ingredient can be acquired.|
| ||Integer||Units/pr gram.|
| ||String||To what category does this ingredient belong.|
A recipe is an atomic component of a dish, i.e. cheese sauce, fried potatoes, meat balls.
| ||List<Integer>||A list of ingredient uids, used in the dish.|
A course is a combination of several dishes all served together at the same time, i.e. fried potatoes with meat balls and cheese sauce.
| ||List<Integer>||A list of dish uids, used in the course.|
A menu is a combination of dishes to be served together or after each other. A standard menu is aperitif, starter, main course and desert.
| ||List<Integer>||A list of course uids, used in the menu.|