Starting this page for scoping - Christina Riley to add initial detail.
| Responsible Person: | |||||||||||||
| Other parties to review/input: | |||||||||||||
| FYI: | |||||||||||||
| Targeted release date: |
| ||||||||||||
| Jira Status: |
|
Status
# | Step | Status |
|---|---|---|
| 1 | Responsible prepares rough business analysis/reqs doc | IN PROGRESS Pierre Dane |
| 2 | Get CHAI review | |
| 3 | ||
| 4 | Get Ona feedback | |
| 5 | Responsible - 1 iteration for feedback | |
| 6 | Ona sign off | |
| 7 | Ona tech spec scoping | |
| 8 | Ona LOE | |
| 9 | Ona scheduling |
Definitions
- DT comment: Christina Riley, can you please review and validate these definitions?
- Inactive structure: a non-valid structure that was created erroneously and should be removed from play completely (e.g., duplicate residential structure record created by accident)
- This is effectively soft deleting the structure
- Ineligible structure: a valid structure that is ineligible to participate in an intervention for a valid reason (e.g., a residential structure where the inhabitants are not currently residing but may return in the future)
- This is a form field specific to the activity
...
- The ability to mark a structure as ineligible is the priority feature - the feature to mark structures as ineligible inactive can be developed in a future release and should be created as a separate scoping document (once this document has been completed)
- No structures are ever deleted from Reveal, they can only be marked as inactive
...