docs(sdlc): finalize ISO 29110 evidence package

2026-08-26 12:35:57 +07:00
parent c68a43449f
commit 5d93e87771
53 changed files with 195 additions and 27 deletions
@@ -19,10 +19,20 @@ Confirm with the Project Sponsor, acting as Customer Representative, that the de

 ## 1. Disclosure

-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.
+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, exact deployed commit identifiers, transaction/data identifiers, and detailed actual-result observations within that window were not separately retained.

 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.

+### 1.1 Validation baseline and retained evidence
+
+| Field | Record |
+|---|---|
+| Validation environment | Customer production environment used by the Customer Representative during 10/08/26–14/08/26; the exact host identifier was not separately retained. |
+| Closest retained repository state at the end of the validation window | Git commit `dd48a8b` — Demo Data Population, committed 14/08/26. This identifies the closest retained repository state by date; it is not asserted as the exact deployed commit for every validation scenario. |
+| Delivered software baseline | Git commit `6c39700`, committed 17/08/26. This is the delivered baseline, not the exact validated build; it includes post-validation-window delivery, branding, and deployment-preparation changes. |
+| Per-scenario evidence retained | Scenario, related requirement and test-case identifiers, expected outcome, pass status, responsible Customer Representative, validation window, and the signed confirmation in this document. |
+| Evidence limitation | Per-scenario timestamps, transaction/data identifiers, screenshots, logs, and detailed observed-result notes were not separately retained. No such details should be reconstructed or backdated. |
+
 ## 2. Validation scenarios

 | No. | Scenario | Related Test Case(s) | Related Req ID(s) | Expected outcome | Status | Tester |
@@ -48,11 +58,15 @@ This is user acceptance testing on the customer's own production environment, an
 | Scenarios executed and validated | 12 — executed 10/08/26–14/08/26 by the Customer Representative |
 | Scenarios pending | 0 |

-## 4. Recommendation
+## 4. Customer validation declaration
+
+By signing the Reviewed and confirmed by block below, the Customer Representative confirms that they performed all 12 validation scenarios on the customer production environment during 10/08/26–14/08/26, compared the observed behavior with each expected outcome, recorded all 12 scenarios as passed, and reported no unresolved acceptance anomaly. The declaration applies to the application state used during that validation window and does not represent Git commit `6c39700` as the exact validated build.
+
+## 5. Recommendation

 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
+## 6. Approval

 ### Prepared by