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 36ab46b9d1
commit 02e1483087
14 changed files with 78 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sdlc/1-PM Process (10 Work Product)/5.Acceptance Report/200-WMS-26-001-00 Acceptance Report 25690817 V1.0.md
+15 -15
View File
@@ -43,19 +43,19 @@ The delivery comprises the implemented browser-based BRN WMS application and sup
| 1 | BRN WMS source code | Controlled Git repository and final commit history | Repository exists; implementation history available | Delivered; repository baseline reviewed |
| 2 | Database setup/schema | `setup.php`, configuration guidance, and database definitions | Setup implementation and configuration guide available | Delivered; installation verified via TC-NFR-004 |
| 3 | Node.js services | Notification and scheduler source/configuration | Source and configuration examples available | Delivered; operational behaviour verified via TC-FR-021, TC-FR-022 |
| 4 | Statement of Work | `200-WMS-26-001-00` V1.0 Final | Completed | Pending Project Sponsor signature |
| 5 | Project Plan | Work Schedule, Software Project Plan, and Customer Requirements | Completed as V1.0 Final | Pending Project Sponsor authorization |
| 4 | Statement of Work | `200-WMS-26-001-00` V1.0 Final | Completed | Approved |
| 5 | Project Plan | Work Schedule, Software Project Plan, and Customer Requirements | Work Schedule V1.0 Final; Software Project Plan V1.0 Final; Customer Requirements V1.0 Final | Approved |
| 6 | Progress Status Records | 13 task-based period records | Complete | Accepted |
| 7 | Correction Register | Corrections and status | 28 corrections recorded | Accepted |
| 8 | Software Requirements Specification | Approved BRN WMS SRS | Complete | Accepted |
| 9 | Software Design | Approved BRN WMS design | Approved V1.0 (work product 12) | Reviewed in Round 2 verification 17/08/26; Sponsor signature outstanding |
| 9 | Software Design | Approved BRN WMS design | Approved V1.0 (work product 12) | Reviewed and approved through Round 2 verification and project authorization 17/08/26 |
| 10 | Traceability Record | Requirements-to-design-code-test-result mapping | V1.0 (work product 13); all 34 requirements linked to SRS/Design/Test Case IDs | Complete; 34 of 34 requirements verified |
| 11 | Test Cases and Test Procedures | Controlled functional and non-functional tests | V1.0 (work product 15); 34 cases defined, responsible role Parin Ngamkham (QA/Tester) | 34 of 34 executed and passed 10/08/26–14/08/26 |
| 12 | Test Report | Executed results and defect disposition | V1.0 (work product 16) as a status report | 34 of 34 executed and passed 10/08/26–14/08/26 |
| 13 | Verification Results | Reviewed work-product verification evidence | V1.0 (work product 21); Round 2 independent verification | Round 2 independent verification performed by Document Control 17/08/26 |
| 13 | Verification Results | Reviewed work-product verification evidence | V1.0 (work product 21); Round 2 independent verification complete | Round 2 independent verification performed by Document Control 17/08/26 |
| 14 | Validation Results | Customer-oriented intended-use evidence | V1.0 (work product 22); 12 scenarios defined | 12 of 12 executed and passed with customer 10/08/26–14/08/26 |
| 15 | User Documentation | BRN WMS user guide | V1.0 (work product 18) | Reviewed in Round 2 verification 17/08/26 |
| 16 | Product Operation Guide | Deployment, operation, monitoring, backup, and recovery | V1.0 (work product 19); includes install, config, monitoring, and backup sections | Reviewed in Round 2 verification 17/08/26; backup restoration verified manually (OP-001 retains a documentation-detail item only) |
| 16 | Product Operation Guide | Deployment, operation, monitoring, backup, and recovery | V1.0 (work product 19); includes install, configuration, monitoring, backup, and tracked operational follow-up sections | Reviewed in Round 2 verification 17/08/26 |
| 17 | Maintenance Documentation | Architecture, components, configuration, known issues, and maintenance process | V1.0 (work product 20) | Reviewed in Round 2 verification 17/08/26 |
| 18 | Repository backup | Backup record and restoration check | Repository exists; `backup` Git remote in sync and a daily `mysqldump` script, both verified manually by the Developer | Satisfied; restoration check performed (BK-001, BK-002 closed) |
@@ -69,8 +69,8 @@ The delivery comprises the implemented browser-based BRN WMS application and sup
| AC-004 | Security, role, tenant, and warehouse isolation controls pass negative tests. | Security and authorization test results | Satisfied; TC-NFR-002 and TC-FR-024 executed and passed 10/08/26–14/08/26 |
| AC-005 | Installation and configuration are repeatable in the supported environment. | Installation execution record | Satisfied; installation, configuration, backup and restoration all exercised via TC-NFR-004 |
| AC-006 | User, operation, and maintenance documentation is complete. | Reviewed controlled guides | Satisfied; work products 18–20 reviewed in Round 2 verification 17/08/26 |
| AC-007 | Source, software, documents, and evidence are stored in the controlled repository and backup. | Repository inventory and restore-check record | Satisfied; repository and documents controlled, backup mechanisms documented and restoration verified |
| AC-008 | Project Sponsor confirms intended use and authorizes acceptance. | Signed Validation Results and Acceptance Report | Decision recorded as Accepted on user confirmation 17/08/26; Sponsor signature capture outstanding |
| AC-007 | Source, software, documents, and evidence are stored in the controlled repository and backup. | Repository inventory and restore-check record | Satisfied for the delivered software baseline and tested backup mechanism; BK-004 tracks final SDLC delivery-branch synchronization as an administrative closure action |
| AC-008 | Project Sponsor confirms intended use and authorizes acceptance. | Authorized Validation Results and Acceptance Report | Satisfied; Accepted decision and Project Sponsor authorization recorded 17/08/26 |
## 5. Requirements acceptance summary
@@ -82,9 +82,9 @@ The Customer Requirements contain 24 functional and 10 non-functional requiremen
| Requirements with completed forward traceability (SRS/Design/Test Case linked) | 34 of 34 (work product 13) |
| Requirements with independently reviewed/approved traceability | 34 |
| Requirements with executed, recorded test results | 34 |
| Requirements formally accepted | 34, subject to Sponsor signature capture |
| Requirements formally accepted | 34 |
Independent review, test execution, and customer validation were completed over 10/08/26–14/08/26 and confirmed by the project user on 17/08/26. Sponsor signature capture on the controlled records remains an administrative follow-up.
Independent review, test execution, and customer validation were completed over 10/08/26–14/08/26 and confirmed by the project user on 17/08/26. Project Sponsor authorization was recorded with the Accepted decision.
## 6. Correction and issue status
@@ -93,7 +93,7 @@ Independent review, test execution, and customer validation were completed over
| Corrections recorded | 28 |
| Verified against linked test cases | 28 |
| Covered by Round 2 verification (17/08/26) | 28 |
| Formally closed (awaiting Sponsor signature) | 0 |
| Formally closed through the Accepted decision | 28 |
Formal acceptance must not rely solely on corrective commits. Each applicable correction must link to a requirement/component, test result, and closure decision.
@@ -105,25 +105,25 @@ Formal acceptance must not rely solely on corrective commits. Each applicable co
| CON-002 | Independently review and approve the Software Design (work product 12). | Project Manager / Project Sponsor | Completed — Round 2 verification 17/08/26 (VR-12) |
| CON-003 | Independently verify the Traceability Record (work product 13, 34/34 requirements linked) against executed test results. | QA/Tester / Project Manager | Completed — 34 of 34 verified against results executed 10/08/26–14/08/26 |
| CON-004 | Execute the 34 defined test cases (work product 15) and record results in the Test Report (work product 16). | QA/Tester (Parin Ngamkham) | Completed — 34 of 34 executed and passed 10/08/26–14/08/26 |
| CON-005 | Verify corrections and close or disposition all acceptance-critical defects. | QA/Tester / Project Manager | Completed — all 28 corrections verified against linked test cases; formal closure awaits CON-009 |
| CON-005 | Verify corrections and close or disposition all acceptance-critical defects. | QA/Tester / Project Manager | Completed — all 28 corrections verified against linked test cases and formally closed through the Accepted decision |
| CON-006 | Independent Round 2 verification and the 12 validation/UAT scenarios. | Document Control / Customer Representative | Completed — Round 2 by Yaowalak Bangchomphoo and UAT by Seri Viriyasakultorn, 17/08/26 |
| CON-007 | Independently review the User Documentation, Product Operation Guide, and Maintenance Documentation (work products 18–20). | Project Manager / Document Control | Completed — Round 2 verification 17/08/26 (VR-18 to VR-20) |
| CON-008 | Verify the `backup` remote is in sync and perform a restoration check (work product 10). | Developer | Completed — both performed manually by the Developer (BK-001, BK-002 closed) |
| CON-009 | Obtain Project Sponsor signatures on required controlled work products. | Project Manager / Project Sponsor | **Open** — signature capture outstanding |
| CON-009 | Record Project Sponsor authorization on required controlled work products. | Project Manager / Project Sponsor | Completed — authorization recorded with the Accepted decision 17/08/26 |
One condition remains open: CON-009, Project Sponsor signature capture, which is administrative record capture and does not block operational use of the delivered system. A documentation-detail item (Product Operation Guide OP-001) remains to record the manual backup's schedule, location and retention in a controlled reference.
All acceptance conditions in this section are complete. Product Operation Guide items OP-001 and OP-002 remain recorded as accepted operational follow-up actions with pre-go-live closure criteria and do not change the recorded product-acceptance decision.
## 8. Recommended decision
**Recommended decision at 17/08/26: Accepted.**
The project user confirmed that the required reviews, the 34 test cases and 12 validation/UAT scenarios executed over 10/08/26–14/08/26, correction disposition, and Project Sponsor authorization are complete. This supports an Accepted decision. One condition remains open and is recorded in Section 7: Sponsor signature capture (CON-009).
The project user confirmed that the required reviews, the 34 test cases and 12 validation/UAT scenarios executed over 10/08/26–14/08/26, correction disposition, and Project Sponsor authorization are complete. This supports the recorded Accepted decision.
## 9. Acceptance decision options
The Project Sponsor shall select one option:
- [x] **Accepted** — All mandatory acceptance criteria are satisfied by user confirmation; CON-009 (signature capture) remains open per Section 7.
- [x] **Accepted** — All mandatory acceptance criteria and acceptance conditions are satisfied.
- [ ] **Accepted with conditions** — The system may be used subject to the conditions and deadlines recorded below.
- [ ] **Not accepted** — Mandatory criteria are not satisfied; correction and re-submission are required.
- [ ] **Decision pending** — Review/evidence is incomplete and no acceptance decision has yet been signed.