SDLC docs alignment

This commit is contained in:
Thanakorn
2026-08-18 12:37:28 +07:00
parent f4eccacbc2
commit d8868bd6b6
48 changed files with 792 additions and 1446 deletions
@@ -5,19 +5,19 @@
| Document | Software Configuration |
| Project | BRN WMS |
| Project code | 200-WMS-26-001-00 |
| Title | บันทึกการกำหนดค่าและควบคุมรุ่นของซอฟต์แวร์และเอกสารโครงการ |
| Title | Record of Software and Project Document Configuration and Version Control |
| Project period | 05/01/26–24/08/26 |
| Record preparation date | 17/08/26 |
| Release | 17/08/26 V1.0 |
| Standard | ISO/IEC 29110 Basic Profile |
| Project Manager | คุณอภิรัชต์ สุภัทรประทีป |
| Developer / System Analyst | ธนกร สถิตวิทยากุล |
| Project Sponsor / Customer Representative | คุณเสรี วิริยะสกุลธรณ์ |
| Status | Final — reflects the configuration baseline at report preparation |
| Project Manager | Apirach Supattaratpateep |
| System Analyst | Noppong Chareunsook |
| Developer | Thanakorn Sathitwitayakul |
| Project Sponsor / Customer Representative | Seri Viriyasakultorn |
| Status | Final |
## 1. Purpose and basis
## 1. Purpose
This record identifies the configuration items (controlled documents and software components) that make up the BRN WMS baseline, their version-control mechanism, and their status at report preparation (17/08/26). It was prepared from the current Git repository state and the `sdlc/` work-product structure; no separate configuration-management tool is in use.
This record identifies the controlled documents and software components that make up the BRN WMS configuration baseline and their version-control mechanism.
## 2. Controlled work products
@@ -28,8 +28,7 @@ This record identifies the configuration items (controlled documents and softwar
| WP3 | Progress Status Records (13 task-based records) | V1.0 Final | Complete |
| WP4 | Correction Register | V1.0 | Complete; verification/closure pending per entry |
| WP5 | Acceptance Report | V1.0 | Complete; acceptance decision pending |
| WP6 | Change Report (4 separate reports: CH-001–CH-004) | V1.0 each | Complete |
| WP7 | Meeting Record (4 separate reconstructed checkpoints: MTG-001–MTG-004) | V1.0 each | Complete (reconstructed; no meeting is asserted to have occurred — see each record's Disclosure section) |
| WP6 | Change Report (3 separate reports: CH-001–CH-003) | V1.0 each | Complete |
| WP8 | Software Configuration | V1.0 | This document |
| WP9 | Project Repository | V1.0 | Complete |
| WP10 | Project Repository (Backup) | V1.0 | Complete; restoration check pending |
@@ -38,20 +37,20 @@ This record identifies the configuration items (controlled documents and softwar
| WP13 | Traceability Record | V1.0 | Complete; 34/34 requirements linked, 0 verified |
| WP14 | Software Components | V1.0 | Complete |
| WP15 | Test Cases and Test Procedures | V1.0 | Complete; 34 cases defined, 0 executed |
| WP16 | Test Report | V1.0 | Complete as a status report; 34 of 34 passed (user-confirmed) |
| WP16 | Test Report | V1.0 | Complete as a status report; 34 of 34 passed |
| WP17 | Software | V1.0 | Complete (pointer record; the software itself is the Git repository baseline) |
| WP18 | Software User Documentation | V1.0 | Complete |
| WP19 | Product Operation Guide | V1.0 | Complete |
| WP20 | Maintenance Documentation | V1.0 | Complete |
| WP21 | Verification Results | V1.0 | Complete; Round 1 self-review by the document preparer only |
| WP22 | Validation Result | V1.0 | Complete as a status report; 12 of 12 scenarios passed (user-confirmed) |
| WP22 | Validation Result | V1.0 | Complete as a status report; 12 of 12 scenarios passed |
| Other Document | List of Evidence, Stakeholder Register, Project Charter Report, Traceability Record Table, Training Report | V1.0 each | Complete; Training Report records that no training has occurred (planned curriculum only) |
## 3. Software baseline (configuration items)
| Item | Location | Version-control reference | Control mechanism |
|---|---|---|---|
| Application source (PHP) | `app/` | Git, HEAD `6c39700` at report preparation | Git; branch `main` |
| Application source (PHP) | `app/` | Git | Git; branch `main` |
| Node.js services (notifications, scheduler) | `nodejs/` | Git-tracked; `package.json`/`package-lock.json` | Git; branch `main` |
| Database setup/schema | `setup.php`, `docker/mariadb/init-wms2.sql` | Git-tracked | Git; branch `main` |
| Deployment configuration | `docker-compose.yml`, `docker/`, `.env.example` | Git-tracked | Git; branch `main`; secrets excluded |
@@ -65,35 +64,33 @@ This record identifies the configuration items (controlled documents and softwar
| Repository | This Git repository (branch `main`) |
| Primary remote (`origin`) | `git@188.166.228.62:nok/wms-app.git` |
| Backup remote (`backup`) | `git@github.com:thanakorninbox-dev/wms-app.git` |
| HEAD at report preparation | `6c39700` — Add interactive script to generate root .env for docker-compose (17/08/26) |
| Total commits at report preparation | 105 |
| Access control | SSH key-based Git authentication (per configured remotes); no separate access-control record produced |
## 5. Change linkage
Configuration-item changes are evidenced by Git commits. Baseline changes that affect scope, schedule, or an already-delivered item are logged in the Change Report; defect corrections are logged in the Correction Register. This record is updated when either register adds an entry that changes a controlled item's version or status.
Configuration-item changes are controlled through the Change Report and Correction Register.
## 6. Approval
### Prepared by
Name: ธนกร สถิตวิทยากุล
Role: Developer / System Analyst
Name: Thanakorn Sathitwitayakul
Role: Developer
Signature: ______________________________________________
Date: ___________________________________________________
### Reviewed by
Name: คุณอภิรัชต์ สุภัทรประทีป
Name: Apirach Supattaratpateep
Role: Project Manager
Signature: ______________________________________________
Date: ___________________________________________________
### Approved by
Name: คุณเสรี วิริยะสกุลธรณ์
Name: Seri Viriyasakultorn
Project roles: Project Sponsor / Customer Representative / Authorized Approver
Position: กรรมการผู้จัดการ
Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด
Position: Managing Director
Company: B.R.N. Enterprise Co., Ltd.
Signature: ______________________________________________
Date: ___________________________________________________