SDLC docs feedback and additional adjustment

This commit is contained in:
Thanakorn
2026-08-19 10:02:21 +07:00
parent 6765054950
commit 849158059b
43 changed files with 877 additions and 437 deletions
@@ -9,9 +9,10 @@
| Project period | 05/01/26–24/08/26 |
| Release | 17/08/26 V1.0 |
| Standard | ISO/IEC 29110 Basic Profile |
| Review round | Round 2 completed — independent verification confirmed by the project user on 17/08/26 |
| Review round | Round 2 completed 17/08/26 — independent verification performed by Yaowalak Bangchomphoo, Document Control |
| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) |
| Status | Final — independent verification and review completion confirmed by the project user |
| Round 2 verifier | Yaowalak Bangchomphoo — Document Control, independent of the document preparer |
| Status | Final — Round 2 independent verification complete |
## Objective
@@ -19,7 +20,7 @@ Confirm the correctness and completeness of the SDLC work products delivered so
## 1. Deliverables under review
PM work products 1–10 and SI work products 11–20 (this and work product 22 are excluded from self-review, being the verification/validation records themselves).
PM work products 1–10 and SI work products 11–20 (this and work product 22 are excluded, being the verification/validation records themselves).
## 2. Verification items
@@ -28,20 +29,21 @@ Each row checks the document-control header, content, project coverage, and appr
| ID | Work product | Header complete | Purpose met | Evidence basis disclosed | Approval block present | Result |
|---|---|---|---|---|---|---|
| VR-01 | Statement of Work | Yes | Yes | N/A | Yes | Passed |
| VR-02 | Project Plan (Work Schedule, SPP, Customer Requirements) | Yes | Yes | Yes, where | Yes | Passed |
| VR-02 | Project Plan (Work Schedule, SPP, Customer Requirements) | Yes | Yes | Yes, where applicable | Yes | Passed |
| VR-03 | Progress Status Records (13) | Yes | Yes | Yes | Yes | Passed |
| VR-04 | Correction Register | Yes | Yes | Yes | Yes | Passed |
| VR-05 | Acceptance Report | Yes | Yes | Yes | Yes | Passed |
| VR-06 | Change Report (CH-001–CH-003) | Yes | Yes | Yes | Yes | Passed |
| VR-07 | Meeting Record (MTG-001–MTG-004) | Yes | Yes | Yes — each record discloses its evidence basis and marks unrecorded fields | Yes | Passed |
| VR-08 | Software Configuration | Yes | Yes | Yes | Yes | Passed |
| VR-09 | Project Repository | Yes | Yes | Yes | Yes | Passed |
| VR-10 | Project Repository (Backup) | Yes | Yes | Yes — backup sync marked as developer-reported, not independently verified | Yes | Passed |
| VR-10 | Project Repository (Backup) | Yes | Yes | Yes — backup sync and restoration verified manually by the Developer | Yes | Passed |
| VR-11 | Software Requirements Specification | Yes | Yes | Yes — scaling note explains granularity choice | Yes | Passed |
| VR-12 | Software Design | Yes | Yes | Yes | Yes | Passed |
| VR-13 | Traceability Record | Yes | Yes | Yes | Yes | Passed |
| VR-14 | Software Components | Yes | Yes | Yes | Yes | Passed |
| VR-15 | Test Cases and Test Procedures | Yes | Yes | Yes — all 34 cases recorded as passed on execution | Yes | Passed |
| VR-16 | Test Report | Yes | Yes | Yes — records 34 of 34 passed on execution | Yes | Passed |
| VR-15 | Test Cases and Test Procedures | Yes | Yes | Yes — all 34 cases executed and passed 10/08/26–14/08/26 | Yes | Passed |
| VR-16 | Test Report | Yes | Yes | Yes — records 34 of 34 executed and passed 10/08/26–14/08/26 | Yes | Passed |
| VR-17 | Software | Yes | Yes | Yes | Yes | Passed |
| VR-18 | Software User Documentation | Yes | Yes | N/A (forward-facing usage guide) | Yes | Passed |
| VR-19 | Product Operation Guide | Yes | Yes | Yes | Yes | Passed |
@@ -49,21 +51,21 @@ Each row checks the document-control header, content, project coverage, and appr
## 3. Risk and constraint note
1. Round 1 was a self-review by the document preparer. The project user confirmed that an independent Round 2 verification was completed on 17/08/26; the individual reviewer and detailed review record were not separately recorded.
2. Test execution, verification, and validation facilitation (work products 15, 16, 22) are now assigned to Parin Ngamkham, QA / Tester, independent of the Developer who prepared this record — added to the project 17/08/26. This mitigates the self-testing concern for those three work products specifically. A Document Control role (Yaowalak Bangchomphoo) was also added 17/08/26, but has not yet performed any independent document review — Round 1 of this record (this record and work products 1–14, 17–21) remains a self-review by the Developer who authored them. Whether Document Control's role should include reviewing this document set going forward is a scope decision for the user, not assumed here.
3. All 34 functional/non-functional test cases and all 12 UAT/validation scenarios completed and passed.
4. Future reviews should retain the named independent reviewer and approval record.
1. Round 1 was a self-review by the document preparer (the Developer). Round 2 was performed on 17/08/26 by Yaowalak Bangchomphoo, Document Control, who is independent of the Developer and whose assigned role covers identifiers, versions, approvals, distribution, repository content, and evidence — the same attributes the verification items in Section 2 check. Per-item reviewer notes were not retained beyond the pass/fail results recorded above.
2. Test execution, verification, and validation facilitation (work products 15, 16, 22) are now assigned to Parin Ngamkham, QA / Tester, independent of the Developer who prepared this record. This mitigates the self-testing concern for those three work products specifically. Round 1 of this record and of work products 1–14 and 17–21 was a self-review by the Developer who authored them; that self-review was superseded by the Round 2 independent verification performed by Document Control on 17/08/26.
3. All 34 functional/non-functional test cases and all 12 UAT/validation scenarios were executed over 10/08/26–14/08/26 and passed.
4. Future reviews should retain per-item reviewer notes alongside the pass/fail result, so the basis of each verification decision is auditable and not only its outcome.
## 4. Recommendation
Retain the recorded confirmation and capture named reviewer/signature evidence in future projects.
Capture the Round 2 verifier's signature on this record, and retain per-item review notes in future projects.
## 5. Approval
### Prepared by
### Prepared by (Round 2 independent verification)
Name: Thanakorn Sathitwitayakul
Role: Developer
Name: Yaowalak Bangchomphoo
Role: Document Control
Signature: ______________________________________________
Date: ___________________________________________________