Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redesigning Database Model for Users and Persons Entities #14

Closed
Norbbs opened this issue Apr 8, 2024 · 0 comments
Closed

Redesigning Database Model for Users and Persons Entities #14

Norbbs opened this issue Apr 8, 2024 · 0 comments
Labels
enhancement New feature or request technical story technical story

Comments

@Norbbs
Copy link
Collaborator

Norbbs commented Apr 8, 2024

As a Developer
I want to redesign the users database for microservice Aang
So that I can keep the model updated and prevent a major technical debt in the future.

Definition Of Ready (DoR)

Definition Observations
The story meet the INVEST and SMART criteria
Dependencies identified and resolved
Written acceptance criteria with test scenarios, understood by the team and agreed upon
The user story was understood and agreed upon in a refinement session with the dev team
The team has an idea of how to make the demonstration of the finished story

Technical context

  1. Entities Model: Users Diagram
  2. MIRO entity model: click here

Scope

  1. Update user model seeing the entites model in the technical context with the following considerations:
  • Ensure that the current flows remain functioning correctly.
  • Include new flows (Persons, Nutritional profiles, nutritional profiles and nutritional restriction)

Out of scope

  • Fill up the nutritional restriction table.
  • Work on any other non-aang microservice

Acceptance Criteria

AC GIVEN WHEN THEN
1 Create persons table a technical requirement review the database model a new table called person will be showed with the following fields: id, name, lastname, date of birth
2 Detele User profile table a technical requierement review the database model user_profiles table won't exist
3 Create nutritional profiles table a technical requirement review the database model a new table called nutritional_profiles will be showed with the following fields: nutrition_restrition_id, person_id
4 Create nutritional restrictions table a technical requierement review the database model a new table called nutritional_restrictions will be showed with the following fields: id, description
5 Update users table a technical requirement review the database model a table called users will be showed with the following fields: id, email, password, person_id
6 Create houses table a new technical requirement review the database model a new table called houses will be showed with the following fields: id, description
7 Create persons_houses table a technical requierement review the database model a new table called persons_houses will be showed with the following fields: person_id, house_id, default_house

Definition of Done (DoD)

Definition Result
All acceptance criteria have been met
No significant or critical defects
Deskcheck ceremony has been made
Keep minimum test coverage of 80% over the necessary code and components
Technical documentation published https://github.com/fjborquez/aang/wiki/Entities#versi%C3%B3n-2
Spike, PoC or benchmarks findings documented
@Norbbs Norbbs added enhancement New feature or request technical story technical story labels Apr 8, 2024
@Norbbs Norbbs added this to the USER DATA REGISTRATION milestone Apr 8, 2024
@fjborquez fjborquez self-assigned this Apr 9, 2024
@Norbbs Norbbs closed this as completed Apr 14, 2024
@fjborquez fjborquez removed their assignment Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request technical story technical story
Projects
None yet
Development

No branches or pull requests

2 participants