Database

Description

In order to be able to save and retrieve information about the plants and the users, the application will be connected to a database. The database should be updated in real time.

Link to milestone features

Clarification

We are using a cloud-based database.

The plants in the database are not linked to specific users. We acknowledge that in a released version, all the users should have access to their own database and not see any other farmers' plants.

Also, once a plant is created in the database, it will not get created in the emulated environment.

Functional Requirements

1. The database shall contain data for both plants and user accounts.
2. The database shall be updated with new plants and/or user information.
3. The application shall be able to retrieve information from the database.
4. The database shall allow the deletion of plant and/or user information.
5. The application shall be able to create or read information to/from the database.

Non Functional Requirements

1. Operations to the database shall not take longer than 1 second.
2. The database should have appropriate names for roots for the path.
3. The database should have appropriate names for the children of the root.
4. The database should be based in the cloud with real time updates from the application.
5. The fields should have appropriate data types and constraints.

Assumptions

1. We assume that the database will be connected with the application.
2. We assume only authorized users have access to write and read from the database.
3. We assume that the users will not get hacked.
4. We assume that the cloud is always accessible and we therefore do not need a backup for our information.
5. We assume that our code does not have bugs in it that disrupts the safety measures for the database.