docs(sdlc): align V1.0 audit evidence
This commit is contained in:
+2
-2
@@ -21,7 +21,7 @@ Confirm with the Project Sponsor, acting as Customer Representative, that the de
|
||||
|
||||
All 12 defined validation scenarios were executed and passed over the validation window 10/08/26–14/08/26 by Seri Viriyasakultorn, acting as Customer Representative, on the customer production environment, and confirmed by the project user on 17/08/26. Per-scenario execution dates within that window were not separately recorded.
|
||||
|
||||
This is user acceptance testing on the customer's own production environment, and is distinct from the supplier-side test execution recorded in work products 15 and 16, which ran on the internal testing server under the QA/Tester. Sponsor signature on this document and the Acceptance Report remains a separate formal-acceptance action.
|
||||
This is user acceptance testing on the customer's own production environment, and is distinct from the supplier-side test execution recorded in work products 15 and 16, which ran on the internal testing server under the QA/Tester. Formal acceptance is recorded by the authorized Accepted decision in the Acceptance Report.
|
||||
|
||||
## 2. Validation scenarios
|
||||
|
||||
@@ -50,7 +50,7 @@ This is user acceptance testing on the customer's own production environment, an
|
||||
|
||||
## 4. Recommendation
|
||||
|
||||
Obtain the Project Sponsor's signature on this record and the Acceptance Report to complete the formal acceptance. Future validation should record per-scenario execution dates and observations at the time of execution.
|
||||
Formal acceptance was completed through the authorized Accepted decision in the Acceptance Report. Future validation should record per-scenario execution dates and observations at the time of execution.
|
||||
|
||||
## 5. Approval
|
||||
|
||||
|
||||
Reference in New Issue
Block a user