draw the use case diagram

$1)$When adding a new food item, the user should define the following attributes: category, name, weight or quantity, and the expiry date. Some of these attributes can be optional. The user should also be able to modify these attributes, when needed.

By default, there are several standard categories. These include bread, milk, cheese, chicken, meats, fruits, and vegetables. The user can define new categories as well.

$2)$ Scanning the expiry dates

When adding a new food item, it should be simple for the user to enter the expiry date for the food item. This can be done by supporting the feature of scanning the expiry dates. When an expiry date is read, it is displayed to the user who can confirm the date or change it if necessary.

$3)$ Scanning the bar codes of food items

When adding a new food item, the user can scan the bar code as well. This should ease adding new food items by scanning the bar code to automatically identify the item and fill in its details. The user should always be prompted to confirm the details of new food items before adding them. Also, the user should be able to edit the details of any food item stored by the app.

$4)$ User notification

When the expiry date of a food item stored by the app is close, the app should notify the user about this. There should be a default pre$-$expiry period before notifying the user which may depend on the food category, and the user should be able to change this period as well.

$5)$ Near local food banks

When the user is notified of the expiry date of a food item, there should be an option to display local food banks that are near to the user$$s address.