SDLC docs feedback and additional adjustment
This commit is contained in:
+2
-2
@@ -62,14 +62,14 @@ BRN WMS supports two deployment paths, evidenced in the repository:
|
||||
| Item | Mechanism | Status |
|
||||
|---|---|---|
|
||||
| Source code and configuration templates | Git, two remotes (`origin`, `backup`) | See Project Repository / Project Repository (Backup), work products 9–10 |
|
||||
| Database (`wms`, `wms2`) | Scheduled `mysqldump` script, run daily, output stored off-server with a retention policy | Reported by the Developer (17/08/26); script location, exact schedule, off-server destination, and retention period are not yet recorded in a controlled configuration reference, and no restoration has been tested — see Section 7 |
|
||||
| Database (`wms`, `wms2`) | Scheduled `mysqldump` script, run daily, output stored off-server with a retention policy | Operated and verified manually by the Developer; a restoration has been performed successfully. Because backup operation is manual, the script location, exact schedule, off-server destination, and retention period are not recorded in a controlled configuration reference — see Section 7 |
|
||||
| SDLC documents | External PDF export package | See Project Repository (Backup), Section 3 |
|
||||
|
||||
## 7. Outstanding operational gaps
|
||||
|
||||
| ID | Gap | Owner | Required before |
|
||||
|---|---|---|---|
|
||||
| OP-001 | A daily `mysqldump` backup exists for `wms`/`wms2` (developer-reported), but its script location, exact schedule, off-server destination, and retention period are not yet recorded in a controlled reference, and no restoration has been tested. | Developer | Final acceptance (NFR-004, Acceptance Report CON-008) |
|
||||
| OP-001 | A daily `mysqldump` backup for `wms`/`wms2` is operated manually and restoration has been verified. Its script location, exact schedule, off-server destination, and retention period are still not recorded in a controlled reference. | Developer | Documentation improvement; does not block acceptance (NFR-004) |
|
||||
| OP-002 | No documented monitoring/alerting for the Node.js service beyond log files. | Developer | Operational acceptance |
|
||||
|
||||
## 8. User and access management
|
||||
|
||||
Reference in New Issue
Block a user