Database design

[qy21gafy]

User story

1. As a software developer
2. I want / need ma design for my database
3. So that I can initialize it for the project

Acceptance criteria

• Database design should consider user data (name, company, permissions, admin status etc.)
• Database design should consider booked desks of each user (desk, time, place, user etc.)
• Database design should consider available resources of each company (name, type, place, capacity etc.)
• Database design should consider different company data (e.g name, country, locations, buildings etc.)
• Database design should be normalized

Definition of done (DoD)

• Added only after week 5
• The same for all features
• Here goes the project specific part

DoD general criteria

• Feature has been fully implemented
• Feature has been merged into the mainline
• All acceptance criteria were met
• Product owner approved features
• All tests are passing
• Developers agreed to release

[xilef45]

@Faoilthiama @jantiegges This ist our first Sketch:

@All: What do you think? We should talk about the authentication for our role management. So how do we restrict who can book a particular desk, or generally inside a building, how this permission gets inherited etc.. This is still missing in our database design. Also, keep in mind that there might also be a couple of fields that are still missing at the moment, such as more detailed descriptions etc., but we focused primarily on the fields that are important for the relations and main functionality for now.

[Ardianpalloshi]

Hi, this looks good. Do you think this is something you would like to discuss with our indrustry partner in tuesday in regards to authentication? Maybe he can share some more details.

[Ardianpalloshi]

I am not sure if this answers the question, or makes sense in this step. But any person which has a username with the domain of the company should be able to book, restriction would be that if the domain does not match then it is not possible to book. Meaning, that when you add the company in the first step, all users need to use the company email address to register and book tables

[n3rdc4ptn]

For me the sketch looks also good. Do you discussed about creating an ER diagram? Such a diagram could be perfect for our documentation and to look at it when working on our code. For the authentication we can maybe add user groups inside a company? So a user can be part of a user group and a user group has a list of rooms and buildings which they can access? Or we leave it out for now to have a more minimal prototype in the beginning which has no permission management for the users and every user can book every desk in its company?

[qy21gafy]

Maybe we could also add an "isApproved" or "awaitingApproval" bool property to the user for the registration/login function.