In order to ensure the system maintains the highest level of integrity during database faults
as a member of the fac team
I want to have visibility into data loss scenarios and how to mitigate in the event they do happen
We're thinking we'll try implementing A and then changing B.
# Tasks
- [ ] [something we'll definitely have to do]
Process checklist
# Sketch
[comment]: # "Notes or a checklist reflecting our understanding of the selected approach"
- [ ] Design designs all the things
- [ ] Engineering engineers all the things
# Definition of Done
## Triage
### If not likely to be important in the next quarter...
- [ ] Archived from the board
### Otherwise...
- [ ] Has a clear story statement
- [ ] Design or Engineering accepts that it belongs in their respective backlog
## Design Backlog
- [ ] Has clearly stated/testable acceptance criteria
- [ ] Meets the design Definition of Ready [citation needed]
- [ ] A design shepherd has been identified
## Design In Progress
- [ ] Meets the design Definition of Done [citation needed]
## Design Review Needed
- [ ] Necessary outside review/sign-off was provided
## Design Done
- [ ] Presented in a sprint review
- [ ] Includes screenshots or references to artifacts
### If no engineering is necessary
- [ ] Tagged with the sprint where it was finished
- [ ] Archived
## Engineering Backlog
- [ ] Has clearly stated/testable acceptance criteria
- [ ] Has a sketch or list of tasks
- [ ] Can reasonably be done in a few days (otherwise, split this up!)
## Engineering Available
- [ ] There's capacity in the `In Progress` column
- [ ] An engineering shepherd has been identified
## Engineering In Progress
- [ ] Meets acceptance criteria
- [ ] Meets [QASP conditions](https://derisking-guide.18f.gov/qasp/)
### If there's UI...
- [ ] Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
- [ ] Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
- [ ] Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.
## Engineering Blocked
- [ ] Blocker removed/resolved
## Engineering Review Needed
- [ ] Outside review/sign-off was provided
## Engineering Done
- [ ] Presented in a sprint review
- [ ] Includes screenshots or references to artifacts
- [ ] Tagged with the sprint where it was finished
- [ ] Archived
At a glance
In order to ensure the system maintains the highest level of integrity during database faults as a member of the fac team I want to have visibility into data loss scenarios and how to mitigate in the event they do happen
Acceptance Criteria
We use DRY behavior-driven development wherever possible.
Scenario:
Given a data incident occurs when we encounter that we have lost data ...
Shepherd
Background
Security Considerations
Required per CM-4.
Sketch
We're thinking we'll try implementing A and then changing B.
Process checklist
# Sketch [comment]: # "Notes or a checklist reflecting our understanding of the selected approach" - [ ] Design designs all the things - [ ] Engineering engineers all the things # Definition of Done ## Triage ### If not likely to be important in the next quarter... - [ ] Archived from the board ### Otherwise... - [ ] Has a clear story statement - [ ] Design or Engineering accepts that it belongs in their respective backlog ## Design Backlog - [ ] Has clearly stated/testable acceptance criteria - [ ] Meets the design Definition of Ready [citation needed] - [ ] A design shepherd has been identified ## Design In Progress - [ ] Meets the design Definition of Done [citation needed] ## Design Review Needed - [ ] Necessary outside review/sign-off was provided ## Design Done - [ ] Presented in a sprint review - [ ] Includes screenshots or references to artifacts ### If no engineering is necessary - [ ] Tagged with the sprint where it was finished - [ ] Archived ## Engineering Backlog - [ ] Has clearly stated/testable acceptance criteria - [ ] Has a sketch or list of tasks - [ ] Can reasonably be done in a few days (otherwise, split this up!) ## Engineering Available - [ ] There's capacity in the `In Progress` column - [ ] An engineering shepherd has been identified ## Engineering In Progress - [ ] Meets acceptance criteria - [ ] Meets [QASP conditions](https://derisking-guide.18f.gov/qasp/) ### If there's UI... - [ ] Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order - [ ] Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works. - [ ] Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate. ## Engineering Blocked - [ ] Blocker removed/resolved ## Engineering Review Needed - [ ] Outside review/sign-off was provided ## Engineering Done - [ ] Presented in a sprint review - [ ] Includes screenshots or references to artifacts - [ ] Tagged with the sprint where it was finished - [ ] Archived