78 lines
5.4 KiB
Markdown
78 lines
5.4 KiB
Markdown
# Validation Result
|
||
|
||
| Document field | Value |
|
||
|---|---|
|
||
| Document | Validation Result (UAT) |
|
||
| Project | BRN WMS |
|
||
| Project code | 200-WMS-26-001-00 |
|
||
| Title | บันทึกการยืนยันความต้องการกับผู้ใช้งาน |
|
||
| Project period | 05/01/26–24/08/26 |
|
||
| Preparation date | 17/08/26 |
|
||
| Release | 17/08/26 V1.0 |
|
||
| Standard | ISO/IEC 29110 Basic Profile |
|
||
| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) |
|
||
| Responsible (Tester) | ปริญ งามขำ — QA / Tester, independent of the Developer / System Analyst |
|
||
| Status | Final — records all 12 defined validation scenarios as passed on user-confirmed retrospective execution; see Section 1 |
|
||
|
||
## Objective (วัตถุประสงค์)
|
||
|
||
Confirm with the Project Sponsor, acting as Customer Representative, that the delivered system meets intended use, is usable, is safe to operate, and is ready for Go-Live, using the operational scenarios defined in Customer Requirements Section 11.
|
||
|
||
## 1. Disclosure
|
||
|
||
On 17/08/26, the project user confirmed retrospectively that all 12 defined validation scenarios were executed and passed. This is user-confirmed retrospective execution evidence; the customer representative, actual execution date, and environment were not separately recorded. Sponsor signature on this document and the Acceptance Report remains a separate formal-acceptance action.
|
||
|
||
## 2. Validation scenarios
|
||
|
||
| No. | Scenario | Related Test Case(s) | Related Req ID(s) | Expected outcome | Status | Tester |
|
||
|---:|---|---|---|---|---|---|
|
||
| 1 | User onboarding and access | TC-FR-001, TC-FR-002 | FR-001, FR-002 | User enters the correct company and sees only functions permitted by role and application access | Passed — user-confirmed | Not separately recorded |
|
||
| 2 | Warehouse setup | TC-FR-005, TC-FR-006 | FR-005, FR-006 | Authorized users configure warehouse/location and product data required for operations | Passed — user-confirmed | Not separately recorded |
|
||
| 3 | Stock receipt | TC-FR-007 | FR-007 | A valid receipt updates traceable stock at the selected location | Passed — user-confirmed | Not separately recorded |
|
||
| 4 | Stock issue | TC-FR-008 | FR-008 | A valid issue reduces available stock; an invalid or excessive issue is rejected | Passed — user-confirmed | Not separately recorded |
|
||
| 5 | Stock transfer | TC-FR-009 | FR-009 | Source and destination movements remain balanced and traceable | Passed — user-confirmed | Not separately recorded |
|
||
| 6 | Lot/serial/expiry control | TC-FR-010 | FR-010 | Required attributes remain associated with stock and appear in applicable reports | Passed — user-confirmed | Not separately recorded |
|
||
| 7 | Sales lifecycle | TC-FR-013 | FR-013 | Quotation/order/invoice/return actions follow permitted statuses and create expected related effects | Passed — user-confirmed | Not separately recorded |
|
||
| 8 | Purchasing lifecycle | TC-FR-014 | FR-014 | Request/order/invoice/return actions follow permitted statuses and create expected related effects | Passed — user-confirmed | Not separately recorded |
|
||
| 9 | Finance and accounting | TC-FR-015, TC-FR-016 | FR-015, FR-016 | Receipt/payment and journal/GL results remain balanced and reportable | Passed — user-confirmed | Not separately recorded |
|
||
| 10 | Reporting | TC-FR-011, TC-FR-017, TC-FR-020 | FR-011, FR-017, FR-020 | Authorized filters return consistent operational and financial results | Passed — user-confirmed | Not separately recorded |
|
||
| 11 | Notification and scheduler | TC-FR-021, TC-FR-022 | FR-021, FR-022 | Relevant events and scheduled alerts reach only appropriate recipients without duplication | Passed — user-confirmed | Not separately recorded |
|
||
| 12 | Tenant isolation | TC-FR-024 | FR-024 | Attempts to access another company or unauthorized warehouse are denied | Passed — user-confirmed | Not separately recorded |
|
||
|
||
## 3. Summary
|
||
|
||
| Measure | Count |
|
||
|---|---:|
|
||
| Scenarios defined | 12 |
|
||
| Scenarios user-confirmed as validated | 12 — retrospective confirmation; customer representative not separately recorded |
|
||
| Scenarios pending | 0 |
|
||
|
||
## 4. Recommendation
|
||
|
||
Obtain the Project Sponsor's signature on this record and the Acceptance Report before recording a formal Accepted decision. Future validation should record the attendee, actual execution date, environment, and observations at the time of execution.
|
||
|
||
## 5. Approval
|
||
|
||
### Prepared by
|
||
|
||
Name: ปริญ งามขำ
|
||
Role: QA / Tester
|
||
Signature: ______________________________________________
|
||
Date: ___________________________________________________
|
||
|
||
### Reviewed by
|
||
|
||
Name: คุณอภิรัชต์ สุภัทรประทีป
|
||
Role: Project Manager
|
||
Signature: ______________________________________________
|
||
Date: ___________________________________________________
|
||
|
||
### Reviewed and confirmed by
|
||
|
||
Name: คุณเสรี วิริยะสกุลธรณ์
|
||
Project roles: Project Sponsor / Customer Representative / Authorized Approver
|
||
Position: กรรมการผู้จัดการ
|
||
Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด
|
||
Signature: ______________________________________________
|
||
Date: ___________________________________________________
|