5.0 KiB
5.0 KiB
Software Configuration
| Document field | Value |
|---|---|
| Document | Software Configuration |
| Project | BRN WMS |
| Project code | 200-WMS-26-001-00 |
| Title | Record of Software and Project Document Configuration and Version Control |
| Project period | 05/01/26–24/08/26 |
| Release | 17/08/26 V1.0 |
| Standard | ISO/IEC 29110 Basic Profile |
| Project Manager | Apirach Supattaratpateep |
| System Analyst | Noppong Chareunsook |
| Developer | Thanakorn Sathitwitayakul |
| Project Sponsor / Customer Representative | Seri Viriyasakultorn |
| Status | Final |
1. Purpose
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
| No. | Work product | Version | Status |
|---|---|---|---|
| WP1 | Statement of Work | V1.0 Final | Complete |
| WP2 | Project Plan (Work Schedule V1.1, Software Project Plan V1.1, Customer Requirements V1.0) | V1.1 / V1.0 Final | Complete; Work Schedule and Software Project Plan re-issued 17/08/26 |
| WP3 | Progress Status Records (13 task-based records) | V1.0 Final | Complete |
| WP4 | Correction Register | V1.0 | Complete; 28 of 28 verified against linked test cases; formal closure awaits signature |
| WP5 | Acceptance Report | V1.0 | Complete; decision Accepted; Sponsor signature capture outstanding |
| WP6 | Change Report (3 separate reports: CH-001–CH-003) | V1.0 each | Complete |
| WP7 | Meeting Record (4 checkpoint records: MTG-001–MTG-004) | 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 performed |
| WP11 | Software Requirements Specification (SRS) | V1.0 | Complete |
| WP12 | Software Design | V1.0 | Complete |
| WP13 | Traceability Record | V1.0 | Complete; 34/34 requirements linked and verified |
| WP14 | Software Components | V1.0 | Complete |
| WP15 | Test Cases and Test Procedures | V1.0 | Complete; 34 cases defined, 34 executed 10/08/26–14/08/26 |
| WP16 | Test Report | V1.0 | Complete; 34 of 34 executed and passed 10/08/26–14/08/26 |
| 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 2 independent verification by Document Control 17/08/26 |
| WP22 | Validation Result | V1.0 | Complete; 12 of 12 scenarios executed and passed 10/08/26–14/08/26 |
| 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 | 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 |
Git; branch main |
| SDLC delivery package | sdlc-delivery/ |
Generated from sdlc/, not hand-edited |
scripts/build-sdlc-delivery.sh |
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 |
| Access control | SSH key-based Git authentication (per configured remotes); no separate access-control record produced |
5. Change linkage
Configuration-item changes are controlled through the Change Report and Correction Register.
6. Approval
Prepared by
Name: Thanakorn Sathitwitayakul
Role: Developer
Signature: ______________________________________________
Date: ___________________________________________________
Reviewed by
Name: Apirach Supattaratpateep
Role: Project Manager
Signature: ______________________________________________
Date: ___________________________________________________
Approved by
Name: Seri Viriyasakultorn
Project roles: Project Sponsor / Customer Representative / Authorized Approver
Position: Managing Director
Company: B.R.N. Enterprise Co., Ltd.
Signature: ______________________________________________
Date: ___________________________________________________