fjborquez / aang Goto Github PK

PHP 80.11% JavaScript 0.15% Blade 19.44% Dockerfile 0.30%

aang's Introduction

About Laravel

Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experience to be truly fulfilling. Laravel takes the pain out of development by easing common tasks used in many web projects, such as:

Simple, fast routing engine.
Powerful dependency injection container.
Multiple back-ends for session and cache storage.
Expressive, intuitive database ORM.
Database agnostic schema migrations.
Robust background job processing.
Real-time event broadcasting.

Laravel is accessible, powerful, and provides tools required for large, robust applications.

Learning Laravel

Laravel has the most extensive and thorough documentation and video tutorial library of all modern web application frameworks, making it a breeze to get started with the framework.

You may also try the Laravel Bootcamp, where you will be guided through building a modern Laravel application from scratch.

If you don't feel like reading, Laracasts can help. Laracasts contains thousands of video tutorials on a range of topics including Laravel, modern PHP, unit testing, and JavaScript. Boost your skills by digging into our comprehensive video library.

Laravel Sponsors

We would like to extend our thanks to the following sponsors for funding Laravel development. If you are interested in becoming a sponsor, please visit the Laravel Partners program.

Premium Partners

Contributing

Thank you for considering contributing to the Laravel framework! The contribution guide can be found in the Laravel documentation.

Code of Conduct

In order to ensure that the Laravel community is welcoming to all, please review and abide by the Code of Conduct.

Security Vulnerabilities

If you discover a security vulnerability within Laravel, please send an e-mail to Taylor Otwell via [email protected]. All security vulnerabilities will be promptly addressed.

License

The Laravel framework is open-sourced software licensed under the MIT license.

aang's People

Contributors

Watchers

aang's Issues

Get Houses By Person

As a Data owner
I want to get the houses who are registered in the system by person
So that obtain relevant information for

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

Scope

Get data from users table and show the following fields.

house by default indicator

House

City

Out of scope

create, update, delete and other non-showing processes.

Acceptance Criteria

		AC	GIVEN	WHEN	THEN
	1	Get houses data by person id	houses date storaged	getting house data process is triggered	houses information will be obtained as a result from the endpoint by person id
	2	Get houses data after register a new house	a new house has been created	getting house data process is triggered	houses information will be obtained as a result from the endpoint by person id including data for the new 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
	Spike, PoC or benchmarks findings documented

Update User Data Manually

As a Data Owner
I want to Update Data User Manually
So that to ensure that I have user information up-to-date and contribute to User privacy , data management and analytic

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#6
	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

Scope

Resolve card #2 identified as a dependency
Create endpoints for user update data
The following fields can only be modified:

Name

Last name

Email

Password

Out of scope

create, delete and other non-update processes.
not including profile update.
not including login.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Update name and last name	Data user fields are filled up correctly	press on update button	the information will be updated successfully
2	User update fails for lack of data	Some data user fields are missing	press on update button	an error message will appear and the data won't be updated successfully
3	User name and last name incorrect format	Name and lastname fields are incorrect format (for example: including numbers and/or symbols)	press on update button	an error message will appear and the data won't be updated successfully
4	User name and last name incorrect dimension	Name and lastname fields are greather than 30 characters	press on update button	an error message will appear and the data won't save successfully
5	Length of a password is shorter than 8	User password is shorter than 8 characters	press on update button	an error message indicating the incorrect longer will appear and the data won't be updated successfully
6	Including a number and a symbol at least	User password is not including numbers neither symbols	press on update button	an error message indicating the incorrect because not including numbers and symbols will appear and the data won't be updated successfully
7	Email fails for incorrect format	User email is not following the standart for email structure	press on update button	an error message indicating the incorrect because not including correct format will appear and the data won't save successfully

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
	Spike, PoC or benchmarks findings documented

Enable and disable users data

As a Data Owner
I want to enable and disable user data from the system
So that I can manage users data by status (enable or disable)

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

Scope

Create endpoints for user enable/disable data.
Select user from users data table information and confirm the action ENABLE or DISABLE.

Out of scope

create, update and other non-delete processes.
not including profile update.
not including login.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Start disable user data from data table	A table with information about users	disable button is clicked	a frontend structure will appear to confirm or cancel the action
2	Start enable user data from data table	A table with information about users	enable button is clicked	a frontend structure will appear to confirm or cancel the action
3	Confirm user data enable/disable	a frontend structure for confirm the action	confirm button is clicked	the user information selected must be unable/disable from database and refresh the table
4	Cancel user data unable/disable	a frontend structure for confirm the action	Cancel button is clicked	the structure must disappear and keep the user information, not unable/disable.

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
	Spike, PoC or benchmarks findings documented

Server error when get a user

As a data owner
I want to get a user
So that I can check the information

Definition Of Ready (DoR)

	Definition	Observations
	Story where the bug was identified or an easy way to reproduce	#14
	Environment (Dev, Test, prod)	prod
	Severity (Low, Medium, High)	low

Bug Description

Server error is showed when try to access to user information

Steps to Reproduce

Go to user list

Click on edit link

A server error message is displayed

Expected Behavior

Get the user information

Actual Behavior

Get a server error message

Impact

Can not get user information for loading fields in user edit form.

Create person endpoint

As a data owner
I want to create new persons using API
So that can expose the API to other microservice

Scope

Create new person

Out of scope

Create new user

Result

A new person is created.

Server Error unchecking house by default

Definition Of Ready (DoR)

	Definition	Observations
	Story where the bug was identified or an easy way to reproduce	#25
	Environment (Dev, Test, prod)	prod
	Severity (Low, Medium, High)	high

Bug Description

Server error when uncheck the house by default and update

Steps to Reproduce

Go to users

Click on "view houses" link on Ash Ketchum user

Ciudad Verde in SANTIAGO select "edit" link.

Uncheck the checkbox "house by default"

Click on update button

The server error message will appear

Evidence

Expected Behavior

Don't allow the updating because the system needs one house by default at least

Actual Behavior

Server error and updating of the data.

Impact

Operation flows stopped

set active property true or false in a House entity

As a Data Owner
I want to disable or enable house data from the system
So that I can only keep the relevant data

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

Scope

Create endpoints for user delete data.

Out of scope

create, update and other non-enabling or non-disabling processes.

Acceptance Criteria

		AC	GIVEN	WHEN	THEN
	1	Enable house	a house with active property is false	setting status process is triggered with the property true	active property will be set as true
	2	Disable house	a house with active property is true	setting status process is triggered with the property false	active property will be set as false

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
	Spike, PoC or benchmarks findings documented

Register a new user account

As a User
I want to register for an account on the system
So that I can access the features and services offered.

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

Scope

Work with the following entities:
User

Id

email

password

isActive

person

Person

Id

name

lastName

dateOfBirth

nutritionalProfile

NutritionalProfile

person

nutritionalRestriction

NutritionalRestriction

Id

description

All the properties are mandatory except to NutritionalProfile.

Out of scope

Any other entity beyond User and Person.
Implementations such as Login or sessions management are out of scope.

Wireframes

This card scope is about the RED RECTANGLE

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Register an user account successfully	an person entity with all its fields correct	the person registration process is triggered	a new person will be created and return the ID generated
2	Register an user account successfully	an user entity with all its fields correct included an Person as a part of the user entity	the user account registration process is triggered	a new user will be created with isActive property value is false and return the ID generated
3	DON'T register an user account because of name is missing	an person entity without name property (empty or null)	the person registration process is triggered	the person won't be created and return an error message like "name is missing"
4	DON'T register an user account because of lastname is missing	an person entity without lastname property (empty or null)	the person registration process is triggered	the person won't be created and return an error message like "lastname is missing"
5	DON'T register an user account because of date of birth is missing	an person entity without date of birth property (empty or null)	the person registration process is triggered	the person won't be created and return an error message like "date of birth is missing"
6	DON'T register an user account because of name incorrect dimension	an person entity which name characters are greater than 30	the person registration process is triggered	the person won't be created and return an error message like "name exceeds maximum of 30 characters"
7	DON'T register an user account because of lastname incorrect dimension	an person entity which lastname characters are greater than 30	the person registration process is triggered	the person won't be created and return an error message like "Lastname exceeds maximum of 30 characters"
8	DON'T register an user account because of name incorrect format	an person entity with incorrect name property	the person registration process is triggered	the person won't be created and return an error message like "name has an incorrect format"
9	DON'T register an user account because of lastname incorrect format	an person entity with incorrect lastname property	the person registration process is triggered	the person won't be created and return an error message like "lastname has an incorrect format"
10	DON'T register an user account because of date of birth incorrect format	an person entity with incorrect date of birth property	the person registration process is triggered	the person won't be created and return an error message like "date of birth has an incorrect format"
11	DON'T register an user account because of future date of birth	an person entity with a future date of birth property	the person registration process is triggered	the person won't be created and return an error message like "Future date of birth are not allowed"
12	DON'T register an user account because of email is missing	an user entity without email property (empty or null)	the user registration process is triggered	the user won't be created and return an error message like "email is missing"
13	DON'T register an user account because of email incorrect format	an user entity with an email that's not following the standart for email structure	the user registration process is triggered	the user won't be created and return an error message like "email incorrect structure"
14	DON'T register an user account because of password is missing	an user entity without password property (empty or null)	the user registration process is triggered	the user won't be created and return an error message like "password is missing"
15	DON'T register an user account because of password length	an user entity with password property is shorter than 8	the user registration process is triggered	the user won't be created and return an error message like "password incorrect longer"
16	DON'T register an user account because of a password is not including a number and a symbol at least	an user entity with password property is not including numbers neither symbols	the user registration process is triggered	the user won't be created and return an error message like "password must include numbers and symbols at least one"

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
	Spike, PoC or benchmarks findings documented

Task template

As a Project Team Member
I want to Update project documentation to include the diagram of the user maintenance microservice called aang
So that all team members have a clear understanding of the microservice architecture.

Scope

Update project documentation to include the diagram of the user maintenance microservice.

Ensure the diagram is clear, concise, and accurately represents the microservice architecture.

Out of scope

Including any other diagram that is not related to the user microservice.

Result

Put the link on this space or comments area...

Create a house

As a Data Owner
I want to create a house data to the other users
So that they can access to completely created data and utilize the data related to the house for their respective needs

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

Scope

Create data in the entity Person:

id (integer, mandatory).

description (string, mandatory, max 30 chatacters).

city_id (foreign key)

Out of scope

create, delete and other non-creation processes.

For the cities entity: province, region and country are out of scope.

Wireframes

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Create a house successfully	a house description correctly	the house creation process is triggered	the house will be created to the table houses.
2	Create a house successfully with isDefault property is true	a house description correctly and isDefault property is false	the house creation process is triggered AND the person has NOT any house registered	the house will be created to the table houses with isDefault property true.
3	Create a house successfully with isDefault property is true	a house description correctly and isDefault property is true	the house creation process is triggered AND the person has at least one house registered	the house will be created on the table houses with isDefault property true AND the old one set the isDefault property false and will be updated with isDefault property false.
4	Create house successfully with isDefault property is false	a house description correctly and isDefault property is false	the house creation process is triggered AND the person has at least one house registered	the house will be created to the table houses with isDefault property false.
5	Don't create new house because of lack of description	a house description null or empty	the house creation process is triggered	the house WON'T be created to the table houses.
6	Don't create the house because of maximum characters allows	a house description with more than 30 characters	the house creation process is triggered	a new house WON'T be created to the table houses.
7	Don't create a house because of data duplication	a house description correctly AND person has one house with the SAME description in the SAME city registered	the house creation process is triggered	a new house WON'T be updated to the table houses .
8	Don't create a house because of lack of city	a house's city is null or empty	the house creation process is triggered	the house WON'T be created to the table houses.
9	Create a house NOT because of data duplication	a house description correctly AND person has one house with the SAME description but NOT in the SAME city registered	the house creation process is triggered	the house will be created to the houses table.
10	Create a house NOT because of data duplication	a house description correctly AND person has one house with a DIFFERENT description but in the SAME city registered	the house creation process is triggered	the house will be created on the table houses.
11	Create house NOT because of data duplication	a house description correctly AND person has one house with a DIFFERENT description in a DIFFERENT city registered	the house creation process is triggered	the house will be created on the table houses.

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
	Spike, PoC or benchmarks findings documented

Server error updating house

Definition Of Ready (DoR)

	Definition	Observations
	Story where the bug was identified or an easy way to reproduce	#25
	Environment (Dev, Test, prod)	prod
	Severity (Low, Medium, High)	high

Bug Description

Give the #25 card testing, AC number 7 is not being fulfilled.

Steps to Reproduce

Go to users

Click on "view houses" link on Ash Ketchum user

Ciudad Verde in CONCEPCION select "edit" link.

Change "Ciudad Verde" to "Ciudad Celeste"

Click on update button

The server error message will appear

Evidence

And yet, when the user clicks the "back" link in the house listing, we realize that the record was updated, which should not happen. Now there are two houses with the same name in the same city, violating AC7.

Expected Behavior

Respect the AC7 of the card #25

Actual Behavior

Server error and updating of the data.

Impact

Now there are two houses with the same name in the same city, violating AC7.

Considering food from different nationalities in recipe recommendations.

Bug Template

As a Data Owner
I want to Register Data User Manually
So that I ensure secure login and authentication

Definition Of Ready (DoR)

	Definition	Observations
	Story where the bug was identified or an easy way to reproduce	#2 AC3
	Environment (Dev, Test, Prod)
	Severity (Low, Medium, High)	Low

Bug Description

When attempting to register a user, the system allows an incorrect format for the user's name and last name, not allowing spaces.

Steps to Reproduce

Fill in the registration form with the user's name and last name.

Include one or more spaces in either the name or last name field.

Click on the register button to submit the form.

Expected Behavior

The system should validate the format of the user's name and last name, allowing any input that includes ONLY NOT CONSECUTIVE SPACES.

Actual Behavior

The system doesn't allow registration even if the name or last name field includes one o more spaces, violating the acceptance criteria.

Impact

Not allowing spaces in the name and last name fields could exclude some users like "De la carrera", "De la fuene", etc.

[IMPORTANT]: blank spaces not consecutive must be allow it.

Studying ways to process necessary business flows for product efficiency

As a product team, we need to explore and evaluate technologies and approaches for efficiently integrating multiple API calls into a single screen within our product. This spike is essential for understanding the feasibility and technical requirements of implementing this functionality, which involves handling complex business flows that require data retrieval from various external services.

What we need:

Research and identify potential technologies and frameworks that support the integration of multiple API calls.
Evaluate the scalability, performance, and maintainability of each technology option.
Investigate the feasibility of implementing a hexagonal architecture for modularizing the integration logic.
Conduct a comparative analysis of the pros and cons of each technology, considering factors such as ease of implementation, community support, and alignment with our existing tech stack.
Document findings, including recommendations for the best approach and technology stack based on the evaluation.

Update user data is not working properly because of the email

As a Data owner
I want to update data users without issues
So that I can keep the data updated whenever i want

Definition Of Ready (DoR)

	Definition	Observations
	Story where the bug was identified or an easy way to reproduce
	Environment (Dev, Test, prod)	prod
	Severity (Low, Medium, High)	medium

Bug Description

In user story #4 , there is an error with the email since it says that the email already exists, which is a correct validation for user registration, not for their update.

Steps to Reproduce

Go to users screen

Click on edit button

Edit information (not the email)

The error message will appear

Expected Behavior

Update user information regardless of whether the email was updated or not.

Actual Behavior

User data udate is not possible because the email already exists

Impact

Cannot update user date without a non-unique email

Server error when a user is created

As a data owner
I want to create new users without issues
So that I can add new users

Definition Of Ready (DoR)

	Definition	Observations
	Story where the bug was identified or an easy way to reproduce	#14
	Environment (Dev, Test, prod)	prod
	Severity (Low, Medium, High)	medium

Bug Description

There are many changes in database for user story #14 . After those changes, the user's creation is failing.

Steps to Reproduce

Go to users screen

Click on add link

Fill the form fields

Click on Register button

Expected Behavior

New user was created.

Actual Behavior

Server error is returned.

Impact

Can not add new users to the system.

Add resident to house

As a Data Owner
I want to include residents to the house entity
So that they can access complete data and use house-related information for their individual needs

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#32
	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

Scope

A resident is a representation of the person entity.
Many persons can belong to many houses.

Out of scope

Activities unrelated to adding residents to the house entity.

Wireframe

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Successfully add a resident (name, last name, date of birth and nutritional profile) to the house	resident details are provided correctly	the addition of a resident to a house process is triggered	the resident is added to the PersonsHouses entity
2	Do not include a resident with missing details	essential resident details are not provided (name, last name or date of birth	the addition of a resident to a house process is triggered	the resident is not added to the PersonsHouses entity
3	Name and last name incorrect format	Name and lastname fields are incorrect format (for example: including numbers and/or symbols)	the addition of a resident to a house process is triggered	an error message will be generated and the data won't be saved successfully
4	User name and last name incorrect dimension	Name and lastname fields are greather than 30 characters	the addition of a resident to a house process is triggered	an error message will be generated and the data won't be saved successfully
5	Do not include a resident with date of birth in a wrong format (if it is not equal than DD-MM-YYYY)	a date of birth	the addition of a resident to a house process is triggered	an error message will be generated and the data won't be saved successfully

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
	Spike, PoC or benchmarks findings documented

Register User Data Manually

As a Data Owner
I want to Register Data User Manually
So that asure secure login and authentication

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

Scope

Create a form with the following fields:

Name (string)

Last name (string

Email (string)

Password (string)

Create endpoints for user registration

Create a database

Create a table users with the fields mentioned in the part 1 adding PK: id.

Create an endpont for creation

Create the controller

Out of scope

update, delete and other non-creation processes.

not including profile registration.

not including login.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Register an user successfully	Data user fields are filled up correctly	press on register button	the information will be saved successfully
2	User registry fails for lack of data	Some data user fields are missing	press on register button	an error message will appear and the data won't be saved successfully
3	User name and last name incorrect format	Name and lastname fields are incorrect format (for example: including numbers and/or symbols)	press on register button	an error message will appear and the data won't be saved successfully
4	User name and last name incorrect dimension	Name and lastname fields are greather than 30 characters	press on register button	an error message will appear and the data won't be saved successfully
5	Length of a password is shorter than 8	User password is shorter than 8 characters	press on register button	an error message indicating the incorrect longer will appear and the data won't be saved successfully
6	Including a number and a symbol at least	User password is not including numbers neither symbols	press on register button	an error message indicating the incorrect because not including numbers and symbols will appear and the data won't de saved successfully
7	Email fails for incorrect format	User email is not following the standart for email structure	press on register	an error message indicating the incorrect because not including correct format will appear and the data won't be saved successfully
8	Encrypted password	a correct pasword	press on register	Data user password filled up will be saved sucessfully and encrypted

Definition of Done (DoD)

	Definition	Result
	All acceptance criteria have been met	A new defect card (bug) will be created with de AC3
	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
	Spike, PoC or benchmarks findings documented

Update House

As a Data Owner
I want to update a house data to the other users
So that they can access to completely updated data and utilize the data related to the house for their respective needs

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

Scope

Update data in the entity Person:

id (integer, mandatory).

description (string, mandatory, max 30 chatacters).

city_id (foreign key)

Out of scope

create, delete and other non-update processes.

For the cities entity: province, region and country are out of scope.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Update house successfully	a house description correctly	the house update process is triggered	the house will be updated to the table houses.
2	Update house successfully with isDefault property is true	a house description correctly and isDefault property is false	the house update process is triggered AND the person has NOT any house registered	the house will be updated to the table houses with isDefault property true.
3	Update house successfully with isDefault property is true	a house description correctly and isDefault property is true	the house update process is triggered AND the person has at least one house registered	the house will be updated to the table houses with isDefault property true AND the old one set the isDefault property false and will be updated with isDefault property false.
4	Update house successfully with isDefault property is false	a house description correctly and isDefault property is false	the house update process is triggered AND the person has at least one house registered	the house will be updated to the table houses with isDefault property false.
5	No update new house because of lack of description	a house description null or empty	the house update process is triggered	the house WON'T be updated to the table houses.
6	No update the house because of maximum characters allows	a house description with more than 30 characters	the house update process is triggered	a new house WON'T be updated to the table houses.
7	No update house because of data duplication	a house description correctly AND person has one house with the SAME description in the SAME city registered	the house update process is triggered	a new house WON'T be added to the table houses .
8	No update house because of lack of city	a house's city is null or empty	the house update process is triggered	the house WON'T be updated to the table houses.
9	Update house NOT because of data duplication	a house description correctly AND person has one house with the SAME description but NOT in the SAME city registered	the house update process is triggered	the house will be updated to the houses table.
10	Update house NOT because of data duplication	a house description correctly AND person has one house with a DIFFERENT description but in the SAME city registered	the house update process is triggered	the house will be updated to the table houses.
11	Update house NOT because of data duplication	a house description correctly AND person has one house with a DIFFERENT description in a DIFFERENT city registered	the house update process is triggered	the house will be updated to the table houses.
12	No update house successfully with isDefault property is false	a house description correctly AND this user has ALL registered houses with by default property in FALSE	the house update process is triggered	the house WON'T be updated to the table houses.

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
	Spike, PoC or benchmarks findings documented

Get residents by house

As a Data owner
I want to get the residents who are registered in the system by house
So that obtain relevant information

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#35
	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

Scope

Get data from person, persons_houses, nutritional_profiles and nutritional_restrictions tables and show the following fields.

Fullname (name + lastname)

Date of birth

Nutritional profile

Out of scope

create, update, delete and other non-showing processes.

Wireframes

Acceptance Criteria

		AC	GIVEN	WHEN	THEN
	1	Get residents data by house id	persons data storaged	getting person data process is triggered	persons information will be obtained as a result from the endpoint by house id
	2	Get residents data after register a new resident	a new resident has been created	getting person data process is triggered	persons information will be obtained as a result from the endpoint by house id including data for the new resident

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
	Spike, PoC or benchmarks findings documented

Update person data

As a Data Owner
I want to Update user data
So that I can ensure up-to-date and reliable data for their use.

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

Scope

Update data in the entity Person:

Name (string, max 30)

Last name (string, max 30)

Date of birth (date)

Out of scope

update, delete and other non-creation processes.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	User update fails for lack of name	user name is missing	the user update process is triggered	the data won't be updated successfully
2	User update fails for lack of lastname	user last name is missing	the user update process is triggered	the data won't be updated successfully
3	User name or last name incorrect format	Name or lastname fields are incorrect format (for example: including numbers and/or symbols)	the user update process is triggered	the data won't be updated successfully
4	User name or last name incorrect dimension	Name and lastname fields are greather than 30 characters	the user update process is triggered	the data won't be updated successfully
5	User update fails for lack of date of birth	date of birth is missing	the user update process is triggered	data won't be updated successfully
6	User date of birth incorrect format	Date of birth field is incorrect (not a valid date format)	the user update process is triggered	the data won't be updated successfully
7	Future user date of birth	future date of birth	the user update process is triggered	the date won't be updated successfully.

Definition of Done (DoD)

	Definition	Result
	All acceptance criteria have been met	A new defect card (bug) will be created with de AC3
	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
	Spike, PoC or benchmarks findings documented

Update entity model

As a Data owner
I want to see the entity model updated
So that I can analyze the information and take decisions based on data

Scope

View the currently model

Create a version 3

Apply the changes

Out of scope

Not implementation in the code or database on google cloud sql.

Result

New entity model with the changes applied

Add house

As a Data Owner
I want to add a house to the other users
So that they can access and utilize the data related to the house for their respective needs

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

Scope

Build an entity "House" with the following fields:

id (integer, mandatory).

description (string, mandatory, max 30 chatacters).

city_id (foreign key)

Create an entity "Cities"

Id (integer, mandatory)

description (string, mandatory)

Add a new entity to the table "houses".
Build an entity "PersonHouse" with the following fields:> -personId (integer, mandatory).

houseId (integer, mandatory).

isDefault (boolean, mandatory).

Add a new register to the table "persons_houses"with the following:

-personId: Person selected id.
-houseId: ID of the newly created 'house' entity.
-isDefault: boolean field with the value selected.

Out of scope

Any other process other than adding houses
For the cities entity: province, region and country are out of scope.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Add new house successfully	a house description correctly	the house registration process is triggered	a new house will be added to the table houses.
2	~~Add new house successfully~~	~~a house description correctly~~	~~the house registration process is triggered~~	~~a new house and person will be added to the table persons_houses .~~
3	Add new house successfully with isDefault property is true	a house description correctly and isDefault property is true	the house registration process is triggered	a new person will be added to the table houses with isDefault property true.
4	Add new house successfully with isDefault property is true	a house description correctly and isDefault property is false	the house registration process is triggered AND the person has NOT any house registered	a new house will be added to the table houses with isDefault property true.
5	Add new house successfully with isDefault property is true	a house description correctly and isDefault property is true	the house registration process is triggered AND the person has at least one house registered	a new house will be added to the table houses with isDefault property true AND set the isDefault property false and the old one will be updated with isDefault property false.
6	Add new house successfully with isDefault property is false	a house description correctly and isDefault property is false	the house registration process is triggered AND the person has at least one house registered	a new house will be added to the table houses with isDefault property false.
7	No add new house because of lack of description	a house description null or empty	the house registration process is triggered	a new house WON'T be added to the table houses niether houses_persons.
8	No add new house because of maximum characters allows	a house description with more than 30 characters	the house registration process is triggered	a new house WON'T be added to the table houses niether houses_persons.
9	No add new house because of data duplication	a house description correctly AND person has one house with the SAME description in the SAME city registered	the house registration process is triggered	a new house WON'T be added to the table houses niether houses_persons.
10	No add new house because of lack of city	a house's city is null or empty	the house registration process is triggered	a new house WON'T be added to the table houses niether houses_persons.
11	~~Add new house NOT because of data duplication~~	~~a house description correctly AND person has one house with the SAME description but NOT in the SAME city registered~~	~~the house registration process is triggered~~	~~a new house will be added to the table houses AND houses_persons.~~
12	~~Add new house NOT because of data duplication~~	~~a house description correctly AND person has one house with a DIFFERENT description but in the SAME city registered~~	~~the house registration process is triggered~~	~~a new house will be added to the table houses AND houses_persons.~~
13	~~Add new house NOT because of data duplication~~	~~a house description correctly AND person has one house with a DIFFERENT description in a DIFFERENT city registered~~	~~the house registration process is triggered~~	~~a new house will be added to the table houses AND houses_persons.~~

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
	Spike, PoC or benchmarks findings documented

Register house to user manually

As a Organic user
I want to register my house in the system
So that I can manage my products of every house separatly and get recommendations will be more accuracy 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

Scope

Create a form with the following fields:

Description (string)

Out of scope

Include address.
update, delete and other non-creation processes.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Register a house successfully	Data user fields are filled up correctly	press on register button	the information will be saved successfully
2	House registry fails for lack of data	Some data house fields are missing	press on register button	an error message will appear and the data won't be saved successfully
3	User name and last name incorrect dimension	description fields are greather than 30 characters	press on register button	an error message will appear and the data won't be saved successfully

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
	Spike, PoC or benchmarks findings documented

Create nutritional restrictions list endpoint

As a data owner
I want to get the nutritional restrictions list
So that can manage it

Scope

Nutritional restrictions

Out of scope

User profile

Result

The full list of nutritional restriction must have its endpoint

Create General Project Documentation

As a Product Team Member
I want to create comprehensive documentation for the project
So that all stakeholders have easy access to essential project information.

Scope

Compile documentation covering various aspects of the project, including:

Overview of project goals and objectives.

Links to external tools and platforms such as BigQuery, Confluence, Miro, Mural, etc.

Out of scope

Detailed technical documentation for individual components.

Implementation-specific documentation.

Result

https://github.com/fjborquez/aang/wiki

Update User Data Profile Manually

As a Data Owner
I want to Update Data User Profile Manually
So that to ensure that I have user information up-to-date and contribute to User privacy , data management and analytic

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#6
	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

Scope

Resolve card #3 identified as a dependency
Create endpoints for user update data
The following fields can only be modified:

Date Of Birth (date)

Is Vegetarian (boolean)

Is Vegan (boolean)

Is Celiac (boolean)

Is Keto (boolean)

Out of scope

create, delete and other non-update processes.

not including profile update.

not including login.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Update an user profile successfully	User profile data fields are filled up correctly	press on update button	the information will be saved successfully
2	User update fails for lack of date of birth field	Date of birth field is missing (null or empty)	press on update button	an error message will appear and the data won't be updated successfully
3	User date of birth incorrect format	Date of birth field is incorrect (not a valid date format)	press on update button	an error message indicating the incorrect date format longer will appear and the data won't be updated successfully
4	Future user date of birth	future date of birth	press on update button	an error message won't allowed future dates and the date won't be updated successfully.
5	Boolean fields	is vegeratian, is vegan, is celiac and is keto fields	press on update button	the information will ve updated successfully with any combination of these fields (true or false)

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
	Spike, PoC or benchmarks findings documented

Delete resident

As a Data Ower
I want to I want to delete a resident from my house
So that I can keep the relevant people information per houses

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#36
	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

Scope

Get the resident id must be delete.
Delete the resident from table persons_houses
If the person (resident) is not an user and that person doesn't beong to other(s) house(s), delete from table person too.

Out of scope

Indicates all that is out of scope for this user story.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Delete a resident successfully	a house id and a person id (selected resident)	deletion resident process is triggered AND selected resident IS an user OR belong to other(s) house(s)	the resident will be remove from table persons_houses.
2	Delete a resident successfully	a house id and a person id (selected resident)	deletion resident process is triggered AND residen IS NOT an user and DOESN'T belong to other(s) house(s)	the resident will be remove from table persons_houses AND from the table person.
3	Deletion fails because of match between resident and house	a house id and a person id (selected resident)	deletion resident process is triggered AND resident DOESN'T belong to that house	an error message will be generated and the deletion process will be stopped

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
	Spike, PoC or benchmarks findings documented

Implement user account activation process via email after successful registration

As a User
I want to activate my user account
So that I can access to the features securely

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

There are user stories about user registration #28 and #2, however the email validation is not a part of this process, so the field of the 'user' entity 'email_verified_at' should not be filled in immediately but rather should go through an email verification process.

Scope

After registration process, sent an email with a code * (I need to validate this with @fjborquez )

Out of scope

Indicates all that is out of scope for this user story.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	AC1 description	initial context or preconditions for the scenario being described	the action or event that triggers the behavior being tested	the expected outcomes or results that should occur as a consequence of the action described in the WHEN section
2
3
4
5

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
	Spike, PoC or benchmarks findings documented

Create seeder for nutritional_restrictions table

As a Data owner
I want to populate the system with nutritional restrictions
So that I can create different users restrictions profiles

Scope

Add nutritional restrictions.

Out of scope

Create default profiles.

Result

The table is populated with different nutritional restrictions.

Person list endpoint

As a Data Owner
I want to list all persons
So that can manage them

Scope

list all persons

Out of scope

users list

Result

A list with all users personal information

Register User Profile Data Manually

As a Data Owner
I want to Register Data User Profile Manually
So that asure secure login and authentication and will help make the user information more comprehensive

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

Scope

Create a form with the following fields:

Date Of Birth (date)

Is Vegetarian (boolean)

Is Vegan (boolean)

Is Celiac (boolean)

Is Keto (boolean)

Create endpoints for user profile registration

Create a database

Create a table user profiles with the fields mentioned in the part 1 adding PK: id and FK: user_id (from users table) 1:1 relationship

Create an endpont for creation

Create the controller

Out of scope

update, delete and other non-creation processes.

not including profile registration.

not including login.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Register an user profile successfully	User profile data fields are filled up correctly	press on register button	the information will be saved successfully
2	User registry fails for lack of date of birth field	Date of birth field is missing (null or empty)	press on register button	an error message will appear and the data won't be saved successfully
3	User date of birth incorrect format	Date of birth field is incorrect (not a valid date format)	press on register button	an error message indicating the incorrect date format longer will appear and the data won't be saved successfully
4	Future user date of birth	future date of birth	press on register button	an error message won't allowed future dates and the date won't be saved successfully.
5	Boolean fields	is vegeratian, is vegan, is celiac and is keto fields	press on register button	the information will ve saved successfully with any combination of these fields (true or false)

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
	Spike, PoC or benchmarks findings documented

Considering food with friends or other non-household groups in recipe recommendations.

Show Users Data

As a Data owner
I want to see the users who are registered in the system
So that visualize relevant information and be able to update and delete information

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#2 #3
	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

Scope

Get data from users table and show the following fields.

Name

Last name

email

User profile data:

Date of birth (DD-MM-YYYY format)

Age (in years)

is vegetarian

is vegan

is celiac

is keto

Include columns with buttons for edit and delete information

Out of scope

create, update, delete and other non-showing processes.
edit and delete buttons just must be showed, not actions are required.
not including login.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Show user data	users date storaged in a database	access to the users screen	user information will be show in a data table with all information described in the scope section
2	Show user data after register a new user	a new user has been register	press on register button	user information will be show in a data table including data for the new user
3	Show empty table	no data registered in the database	access to the users screen	an empty datatable will be showed
4	Show edit and delete buttons	users date storage in a database	access to the users screen	edit and delete buttons must be showed per row or register in the datatable

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
	Spike, PoC or benchmarks findings documented

Delete user data manually

As a Data Owner
I want to delete user data from the system
So that I can only keep the relevant data

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#6
	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

Scope

Resolve dependency with #6 .
Create endpoints for user delete data.
Select user from users data table information and confirm the action DELETE.

Out of scope

create, update and other non-delete processes.
not including profile update.
not including login.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Start delete user data from data table	A table with information about users	delete button is clicked	a frontend structure will appear to confirm or cancel the action
2	Confirm user data deletion	a frontend structure for confirm the action	confirm button is clicked	the user information selected must be deleted from database and refresh the table
3	Cancel user data deletion	a frontend structure for confirm the action	Cancel button is clicked	the structure must disappear and keep the user information, not deleted.

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
	Spike, PoC or benchmarks findings documented

Get houses by person

As a Data owner
I want to see the person's houses registered in the system
So that visualize relevant information and be able to update and delete information

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

Scope

Create an endpoint for person's houses
Get data from persons and persons_houses tables.

Out of scope

create, update, delete and other non-showing processes.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Not obtain information	a person ID	the getting houses information process is triggered AND there is not information	the endpoint will return an empty list (not null is allowed)
2	Get person's houses	a valid person ID	the getting houses information process is triggered	houses information is obtained from the data base
3	Return an error because of incorrect ID	an invalid ID	the getting houses information process is triggered	the endpoint will return an error message.

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
	Spike, PoC or benchmarks findings documented

Redesigning Database Model for Users and Persons Entities

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

Entities Model: Users Diagram
MIRO entity model: click here

Scope

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

Add nutritional profile to the registration

As a User
I want to define my nutritional profile
So that I can get recommendations about my preferences

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#28
	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

Scope

Work with the following entities:

NutritionalRestritions

NutritionalProfile

Person

Out of scope

Indicates all that is out of scope for this user story.

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	AC1 description	initial context or preconditions for the scenario being described	the action or event that triggers the behavior being tested	the expected outcomes or results that should occur as a consequence of the action described in the WHEN section
2
3
4
5

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
	Spike, PoC or benchmarks findings documented

Update resident

As a Data Owner
I want to update the resident data
So that they can access to completely updated data and utilize the data related to the resident for their respective needs

Definition Of Ready (DoR)

	Definition	Observations
	The story meet the INVEST and SMART criteria
	Dependencies identified and resolved	#36
	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

Scope

Update data in the entity Person:

id (integer, mandatory).

name (string, mandatory, max 30 chatacters).

lastname (string, mandatory, max 30 chatacters).

date of birth (date, mandatory)

Out of scope

create, delete and other non-update processes.

For the cities entity: province, region and country are out of scope.

Wireframe

Acceptance Criteria

	AC	GIVEN	WHEN	THEN
1	Update resident successfully	a resident data correctly	the resident update process is triggered	the resident will be updated on the table persons.
2	Don't update resident because of lack of name or lastname	a name or last name is null or empty	the resident update process is triggered	the resident WON'T be updated to the table persons.
3	Don't update resident because of maximum characters allows	a residen name or lastname with more than 30 characters	the resident update process is triggered	a resident WON'T be updated to the table persons.
4	Resident update fails for lack of date of birth field	Date of birth field is missing (null or empty)	the resident update process is triggered	an error message will be generated and the data won't be updated successfully
5	Resident date of birth with incorrect format	Date of birth field is incorrect (not a valid date format)	the resident update process is triggered	an error message indicating the incorrect date format longer will be generated and the data won't be updated successfully
6	Future user date of birth	future date of birth	the resident update process is triggered	an error message won't allowed future dates and the date won't be updated successfully.

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
	Spike, PoC or benchmarks findings documented

USER DATA REGISTRATION

Context

All we need to do for registring an user and profile.

Problems to solve with this epic:

Difficulty customizing user experience.
Lack of login and authentication capabilities.
Limitations on personalization of content and recommendations.

Benefis after finish this epic:

Customizing the user experience.
Secure login and authentication.
User privacy , data management and analytic.