16 Database implementation

[e-Steffen]

Database implementation

As a user, I want my activities to be stored and retrievable within the application, so that my data is always available even if I reload the page or clear the browser cache.

Description

Design and implement the MongoDB database to handle the backend data storage needs of the vivaVenture project. This involves setting up the database schema, establishing connections, and ensuring that CRUD operations are integrated into the application

Acceptance criteria

• [x] The application must establish a successful connection to the MongoDB database
• [x] The connection should handle errors
• [x] New activities should be saved and remain available even after the user reloads the page or clears the browser cache
• [x] Users should be able to create, read, update, and delete activities
• [x] error messages should be displayed for invalid entries

Tasks

• [x] Configure MongoDB Atlas server
• [x] Set up environment variables for the database
• [x] Ensure a secure connection to the database
• [x] Identify data requirements and design the schema accordingly
• [x] Use Mongoose to define schema models
• [x] Develop functions for creating, reading, updating, and deleting Activities
• [x] Integrate these functions with the existing application logic
• [x] integrate error messages for invalid entries

[Roland-Hufnagel]

Why not writing a userstory? It is a big value to have the data available from different devices.

Create a schema that accommodates the current data requirements Use Mongoose to define schema models

These two points are more like tasks for the developer then AC. Please write the AC from a user / tester perspective. E.g. 'New created activities are available even if the user reloads the page or deletes the browser cache.'

[Roland-Hufnagel]

Looks good now.