nok/wms-app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(sdlc): align V1.0 audit evidence

Browse Source
This commit is contained in:
Thanakorn
2026-08-19 14:11:00 +07:00
parent bbc3654180
commit 7d211be7e5
14 changed files with 78 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sdlc/2-SI Process (12 Work Product)/19.Product Operation Guide/200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md
+5 -5
View File
@@ -65,12 +65,12 @@ BRN WMS supports two deployment paths, evidenced in the repository:
| 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
## 7. Accepted operational follow-up actions
| ID | Gap | Owner | Required before |
|---|---|---|---|
| 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 |
| ID | Follow-up action | Owner | Target | Closure criterion |
|---|---|---|---|---|
| OP-001 | Record the operated `mysqldump` backup control for `wms`/`wms2` in a controlled reference. | Developer | Before go-live | The controlled reference identifies the script location, exact schedule, off-server destination, retention period, responsible operator, and restoration procedure. |
| OP-002 | Document monitoring and failure alerting for the Node.js service beyond local log review. | Developer | Before go-live | The controlled procedure identifies the health check, alert trigger, recipient, escalation path, and recovery response for `server.js` and `scheduler.js`. |
## 8. User and access management