fjborquez / aang

0 stars 0 forks source link

Delete resident #38

Closed Norbbs closed 2 months ago

Norbbs commented 5 months ago

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
  • - [x]
The story meet the INVEST and SMART criteria
  • - [x]
Dependencies identified and resolved #36
  • - [x]
Written acceptance criteria with test scenarios, understood by the team and agreed upon
  • - [x]
The user story was understood and agreed upon in a refinement session with the dev team
  • - [x]
The team has an idea of how to make the demonstration of the finished story

Scope

  1. Get the resident id must be delete.
  2. Delete the resident from table _personshouses
  3. 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

  1. 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 _personshouses.
  • - [ ]
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 _personshouses 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