SDLC docs feedback and additional adjustment
This commit is contained in:
@@ -10,19 +10,21 @@
|
||||
| Release | 17/08/26 V1.0 |
|
||||
| Standard | ISO/IEC 29110 Basic Profile |
|
||||
| Prepared by | Apirach Supattaratpateep — Project Manager |
|
||||
| Status | Final as a status report — **no training session has been conducted**; see Section 1 |
|
||||
| Status | Final as a training plan — a session is **scheduled but not yet conducted**; see Section 1 |
|
||||
|
||||
## 1. Training information
|
||||
|
||||
| Topic | Details |
|
||||
|---|---|
|
||||
| Training date | Not yet scheduled |
|
||||
| Location | Not yet determined |
|
||||
| Trainer | Thanakorn Sathitwitayakul (Developer); no dedicated trainer role is currently assigned |
|
||||
| Training date | Scheduled 21/08/26, within the project period ending 24/08/26; not yet conducted |
|
||||
| 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 | Not yet determined — expected to include Owner/Admin, Staff, and Viewer role representatives per company |
|
||||
| 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 |
|
||||
| Materials | Software User Documentation (work product 18) and Product Operation Guide (work product 19) |
|
||||
|
||||
## 3. Planned curriculum
|
||||
## 2. Planned curriculum
|
||||
|
||||
Derived from the Software User Documentation (work product 18):
|
||||
|
||||
@@ -39,15 +41,28 @@ Derived from the Software User Documentation (work product 18):
|
||||
| 9 | Notifications |
|
||||
| 10 | Reports (filter, view, print, export) |
|
||||
|
||||
## 4. Result
|
||||
## 3. Result
|
||||
|
||||
No result to report — training has not yet occurred. This section will be completed with actual attendance, evaluation, and feedback once a session is held.
|
||||
**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:
|
||||
|
||||
## 5. Recommendation
|
||||
| Field | To be recorded after the session |
|
||||
|---|---|
|
||||
| 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 |
|
||||
|
||||
Schedule training after Test Report execution (work product 16) and before the customer validation session (work product 22), so trained users can meaningfully participate in validation walkthroughs.
|
||||
Nothing in this section may be filled in before the session is delivered.
|
||||
|
||||
## 6. Approval
|
||||
## 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.
|
||||
|
||||
## 5. Approval
|
||||
|
||||
### Prepared by
|
||||
|
||||
|
||||
Reference in New Issue
Block a user