Files
wms-app/sdlc/1-PM Process (10 Work Product)/8.Software Configuration/200-WMS-26-001-00 Software Configuration 25690817 V1.0.md
T
2026-08-17 17:09:27 +07:00

6.0 KiB
Raw Blame History

Software Configuration

Document field Value
Document Software Configuration
Project BRN WMS
Project code 200-WMS-26-001-00
Title บันทึกการกำหนดค่าและควบคุมรุ่นของซอฟต์แวร์และเอกสารโครงการ
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

1. Purpose and basis

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.

2. Controlled work products

No. Work product Version Status
WP1 Statement of Work V1.0 Final Complete
WP2 Project Plan (Work Schedule, Software Project Plan, Customer Requirements) V1.0 Final Complete
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)
WP8 Software Configuration V1.0 This document
WP9 Project Repository V1.0 Complete
WP10 Project Repository (Backup) V1.0 Complete; restoration check pending
WP11 Software Requirements Specification (SRS) V1.0 Complete
WP12 Software Design V1.0 Complete
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)
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)
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
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
Environment secrets (.env, app/config.php) Deployment host only Not version-controlled Generated at deploy time via docker/init-env.sh; excluded by .gitignore
SDLC work products sdlc/ Git-tracked .md/.html; PDFs exported externally Git; PDF package at C:\Users\TL\Documents\200-WMS-26-001-00\

4. Version control and access

Field Value
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.

6. Approval

Prepared by

Name: ธนกร สถิตวิทยากุล
Role: Developer / System Analyst
Signature: ______________________________________________
Date: ___________________________________________________

Reviewed by

Name: คุณอภิรัชต์ สุภัทรประทีป
Role: Project Manager
Signature: ______________________________________________
Date: ___________________________________________________

Approved by

Name: คุณเสรี วิริยะสกุลธรณ์
Project roles: Project Sponsor / Customer Representative / Authorized Approver
Position: กรรมการผู้จัดการ
Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด
Signature: ______________________________________________
Date: ___________________________________________________