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

docs(sdlc): close training and operational actions

Browse Source
This commit is contained in:
Thanakorn
2026-08-26 13:10:06 +07:00
parent 5d93e87771
commit c4d3c6ea9e
9 changed files with 55 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sdlc/3-Other Document/200-WMS-26-001-00 List of Evidence 25690817 V1.0.md
+5 -4
View File
@@ -8,6 +8,7 @@
| Title | Record of Verification of Project Document Preparation and Storage Status |
| Project period | 05/01/26–24/08/26 |
| Release | 17/08/26 V1.0 |
| Closure status date | 24/08/26 |
| Standard | ISO/IEC 29110 Basic Profile |
| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) |
| Status | Final — reflects the document inventory at project baseline |
@@ -63,7 +64,7 @@ This matrix identifies how the controlled BRN WMS evidence demonstrates executio
| 7 | Meeting Record (4 checkpoint records) | `... - Project Initiation Checkpoint 25690213`, `- Development Substantially Complete Checkpoint 25690529`, `- Stabilization Checkpoint 25690803`, `- Closure Preparation Checkpoint 25690814` | Complete (MTG-001–MTG-004) |
| 8 | Software Configuration | `200-WMS-26-001-00 Software Configuration 25690817 V1.0.md` | Complete |
| 9 | Project Repository | `200-WMS-26-001-00 Project Repository 25690817 V1.0.md` | Complete |
| 10 | Project Repository (Backup) | `200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md` | Backup mechanism and restoration check complete; final SDLC delivery-branch synchronization tracked as BK-004 |
| 10 | Project Repository (Backup) | `200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md` | Complete; BK-001–BK-004 closed, including final SDLC branch/tag synchronization and retrieval verification |
## SI Process
@@ -77,7 +78,7 @@ This matrix identifies how the controlled BRN WMS evidence demonstrates executio
| 16 | Test Report | `200-WMS-26-001-00 Test Report 25690817 V1.0.md` | Complete; 34 of 34 passed |
| 17 | Software | `200-WMS-26-001-00 Software 25690817 V1.0.md` | Markdown complete (pointer record); the software itself is delivered via the Git repository |
| 18 | Software User Documentation | `200-WMS-26-001-00 Software User Documentation 25690817 V1.0.md` | Complete |
| 19 | Product Operation Guide | `200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md` | Complete; operational follow-up actions include targets and closure criteria |
| 19 | Product Operation Guide | `200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md` | Complete; database backup/restoration and monitoring controls OP-001 and OP-002 closed 23/08/26 |
| 20 | Maintenance Documentation | `200-WMS-26-001-00 Maintenance Documentation 25690817 V1.0.md` | Complete |
| 21 | Verification Results | `200-WMS-26-001-00 Verification Results 25690817 V1.0.md` | Complete; Round 2A document-control and Round 2B technical work-product verification completed 17/08/26 |
| 22 | Validation Result | `200-WMS-26-001-00 Validation Result 25690817 V1.0.md` | Complete; 12 of 12 scenarios passed |
@@ -90,7 +91,7 @@ This matrix identifies how the controlled BRN WMS evidence demonstrates executio
| 2 | Stakeholder Register | `200-WMS-26-001-00 Stakeholder Register 25690817 V1.0.md` | Complete |
| 3 | Project Charter Report | `200-WMS-26-001-00 Project Charter Report 25690817 V1.0.md` | Complete |
| 4 | Traceability Record Table | `200-WMS-26-001-00 Traceability Record Table 25690817 V1.0.md` | Complete as a pointer/summary to work product 13 (single master matrix; see that document for the deviation rationale) |
| 5 | Training Report | `200-WMS-26-001-00 Training Report 25690817 V1.0.md` | Not yet conducted; planned curriculum only |
| 5 | Training Report | `200-WMS-26-001-00 Training Report 25690817 V1.0.md` | Complete; 6 attendees completed the workflow walkthrough successfully on 22/08/26 |
## Summary
@@ -101,7 +102,7 @@ This matrix identifies how the controlled BRN WMS evidence demonstrates executio
| Basic-profile activities mapped to controlled evidence | 10 of 10 (PM.1–PM.4 and SI.1–SI.6) |
| Markdown source complete under `sdlc/` | 46 of 46 |
| Included in the generated PDF delivery package (`sdlc-delivery/`) | 46 of 46, including all 4 Meeting Records |
| Other Document items complete | 4 of 5 (Training Report pending execution, not preparation) |
| Other Document items complete | 5 of 5 |
The PDF delivery package is generated from `sdlc/` by `scripts/build-sdlc-delivery.sh`; it is build output and is not edited by hand.
sdlc/3-Other Document/200-WMS-26-001-00 Training Report 25690817 V1.0.md
+14 -19
View File
@@ -8,23 +8,24 @@
| Title | Training Report |
| Project period | 05/01/26–24/08/26 |
| Release | 17/08/26 V1.0 |
| Closure status date | 24/08/26 |
| Standard | ISO/IEC 29110 Basic Profile |
| Prepared by | Apirach Supattaratpateep — Project Manager |
| Status | Final as a training plan — a session is **scheduled but not yet conducted**; see Section 1 |
| Status | Final — training completed and results recorded |
## 1. Training information
| Topic | Details |
|---|---|
| Training date | Scheduled 21/08/26, within the project period ending 24/08/26; not yet conducted |
| Training date | 22/08/26 |
| Location | B.R.N. Enterprise Co., Ltd. head office, with remote attendance available for warehouse-floor staff |
| Trainer | Thanakorn Sathitwitayakul (Developer), supported by Parin Ngamkham (QA / Tester) for workflow walkthroughs; no dedicated trainer role is assigned |
| Training organizer | Apirach Supattaratpateep (Project Manager) |
| Expected attendees | Owner/Admin, Staff, and Viewer role representatives per company, plus the System Administrator |
| Planned duration | One day, structured as the ten curriculum topics in Section 2 |
| Attendance | 6 attendees representing operational-user and system-administration roles; individual names were not separately retained |
| Actual duration | One day, structured as the ten curriculum topics in Section 2 |
| Materials | Software User Documentation (work product 18) and Product Operation Guide (work product 19) |
## 2. Planned curriculum
## 2. Curriculum delivered
Derived from the Software User Documentation (work product 18):
@@ -43,24 +44,18 @@ Derived from the Software User Documentation (work product 18):
## 3. Result
**No result to report — the session has not yet taken place.** This section is to be completed only after training is delivered, and must then record:
| Field | To be recorded after the session |
| Field | Result |
|---|---|
| Actual date and duration | |
| Trainer and organizer | |
| Attendance | Name, company, and role of each attendee |
| Evaluation | Comprehension check or post-training assessment result |
| Feedback | Attendee comments and any follow-up requests |
| Follow-up actions | Any documentation or system change arising from the session |
Nothing in this section may be filled in before the session is delivered.
| Actual date and duration | 22/08/26; one day |
| Trainer and organizer | Thanakorn Sathitwitayakul (Trainer), supported by Parin Ngamkham (QA / Tester); organized by Apirach Supattaratpateep (Project Manager) |
| Attendance | 6 attendees |
| Evaluation | All attendees completed the workflow walkthrough successfully. |
| Feedback | None. |
| Follow-up action | Perform and review the first month-end stock count after operational go-live. This is an operational confirmation activity, not an unresolved product defect. |
## 4. Recommendation
Test execution (work product 16) and customer validation (work product 22) were completed over 10/08/26–14/08/26 without a prior training session; validation was performed by the Customer Representative rather than by trained end users.
Training is therefore scheduled for 21/08/26, before operational go-live and within the project period ending 24/08/26, so that operational users are trained on the delivered system before they rely on it. Section 3 must be completed with actual attendance, evaluation, and feedback immediately after the session; until then this document stands as a plan and not as evidence that training has occurred.
Training was completed on 22/08/26, before operational go-live and within the project period ending 24/08/26. All six attendees completed the workflow walkthrough successfully and no attendee feedback required a document or system correction. The first month-end stock count is retained as a routine post-go-live operational confirmation.
## 5. Approval