From a859cfda3e282331815fe7389ac4f961d4798f9d Mon Sep 17 00:00:00 2001 From: Thanakorn Date: Tue, 18 Aug 2026 08:53:19 +0700 Subject: [PATCH] SDLC docs alignment --- ...0 Statement of Work 25690105 V1.0 Final.md | 102 ++++++------ ...oject Repository (Backup) 25690817 V1.0.md | 36 ++--- ...01-00 Work Schedule 25690105 V1.0 Final.md | 68 ++++---- ...ftware Project Plan 25690105 V1.0 Final.md | 71 ++++----- ...stomer Requirements 25690112 V1.0 Final.md | 34 ++-- ...00 Progress Status Record 25690123 V1.0.md | 33 ++-- ...00 Progress Status Record 25690218 V1.0.md | 35 ++--- ...00 Progress Status Record 25690225 V1.0.md | 22 +-- ...00 Progress Status Record 25690317 V1.0.md | 22 +-- ...00 Progress Status Record 25690429 V1.0.md | 22 +-- ...00 Progress Status Record 25690508 V1.0.md | 22 +-- ...00 Progress Status Record 25690513 V1.0.md | 22 +-- ...00 Progress Status Record 25690523 V1.0.md | 22 +-- ...00 Progress Status Record 25690529 V1.0.md | 22 +-- ...00 Progress Status Record 25690731 V1.0.md | 31 ++-- ...00 Progress Status Record 25690803 V1.0.md | 22 +-- ...00 Progress Status Record 25690814 V1.0.md | 29 ++-- ...00 Progress Status Record 25690817 V1.0.md | 29 ++-- ...01-00 Correction Register 25690817 V1.0.md | 88 +++++------ ...-001-00 Acceptance Report 25690814 V1.0.md | 63 ++++---- ...eport - Closure Extension 25690817 V1.0.md | 31 ---- ...livery Preparation Bundle 25690817 V1.0.md | 50 +++--- ...rt - Demo Data Population 25690814 V1.0.md | 48 +++--- ...port - Rack to Bin Rename 25690527 V1.0.md | 48 +++--- ...etion Boundary Checkpoint 25690814 V1.0.md | 75 --------- ...ially Complete Checkpoint 25690529 V1.0.md | 75 --------- ...ect Initiation Checkpoint 25690219 V1.0.md | 75 --------- ... Stabilization Checkpoint 25690803 V1.0.md | 75 --------- ...00 Software Configuration 25690817 V1.0.md | 41 +++-- ...001-00 Project Repository 25690817 V1.0.md | 27 ++-- ...equirements Specification 25690817 V1.0.md | 21 ++- ...26-001-00 Software Design 25690817 V1.0.md | 23 ++- ...01-00 Traceability Record 25690817 V1.0.md | 102 ++++++------ ...01-00 Software Components 25690817 V1.0.md | 24 +-- ...Cases and Test Procedures 25690817 V1.0.md | 91 ++++++----- ...WMS-26-001-00 Test Report 25690817 V1.0.md | 97 ++++++------ ...00-WMS-26-001-00 Software 25690817 V1.0.md | 20 +-- ...ftware User Documentation 25690817 V1.0.md | 21 ++- ...0 Product Operation Guide 25690817 V1.0.md | 27 ++-- ...Maintenance Documentation 25690817 V1.0.md | 21 ++- ...1-00 Verification Results 25690817 V1.0.md | 46 +++--- ...-001-00 Validation Result 25690817 V1.0.md | 49 +++--- ...6-001-00 List of Evidence 25690817 V1.0.md | 32 ++-- ...00 Project Charter Report 25690817 V1.0.md | 82 +++++----- ...1-00 Stakeholder Register 25690817 V1.0.md | 40 ++--- ...Traceability Record Table 25690817 V1.0.md | 19 ++- ...26-001-00 Training Report 25690817 V1.0.md | 35 ++--- sdlc/SDLC_DOCS.md | 148 ------------------ 48 files changed, 792 insertions(+), 1446 deletions(-) delete mode 100644 sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Closure Extension 25690817 V1.0.md delete mode 100644 sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Completion Boundary Checkpoint 25690814 V1.0.md delete mode 100644 sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Development Substantially Complete Checkpoint 25690529 V1.0.md delete mode 100644 sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Project Initiation Checkpoint 25690219 V1.0.md delete mode 100644 sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Stabilization Checkpoint 25690803 V1.0.md delete mode 100644 sdlc/SDLC_DOCS.md diff --git a/sdlc/1-PM Process (10 Work Product)/1.Statement of Work/200-WMS-26-001-00 Statement of Work 25690105 V1.0 Final.md b/sdlc/1-PM Process (10 Work Product)/1.Statement of Work/200-WMS-26-001-00 Statement of Work 25690105 V1.0 Final.md index beafacc..0ca6bb7 100644 --- a/sdlc/1-PM Process (10 Work Product)/1.Statement of Work/200-WMS-26-001-00 Statement of Work 25690105 V1.0 Final.md +++ b/sdlc/1-PM Process (10 Work Product)/1.Statement of Work/200-WMS-26-001-00 Statement of Work 25690105 V1.0 Final.md @@ -9,91 +9,91 @@ Chongnonsi, Yannawa, Bangkok 10120 | Document | Statement of Work | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Project name | โครงการพัฒนาระบบบริหารจัดการคลังสินค้า | +| Project name | Warehouse Management System Development Project | | Project period | 05/01/26–24/08/26 | | Release | 05/01/26 V1.0 Final | | Status | Final — ready for authorized approval | -วันที่ 05/01/26 +Date 05/01/26 -**เรื่อง:** ขอบเขตการดำเนินงานโครงการพัฒนาระบบบริหารจัดการคลังสินค้า +**Subject:** Scope of work for the Warehouse Management System Development Project -**เรียน:** ผู้บริหารและผู้มีส่วนเกี่ยวข้องในโครงการ +**To:** Executives and project stakeholders -บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด มีความประสงค์ดำเนินโครงการพัฒนาระบบบริหารจัดการคลังสินค้า เพื่อเพิ่มความถูกต้องและความรวดเร็วของงานคลังสินค้า ทำให้สามารถติดตามสินค้าคงคลัง การเคลื่อนไหวสินค้า คำสั่งซื้อ เอกสารทางธุรกิจ และข้อมูลบัญชีที่เกี่ยวข้องได้อย่างเป็นระบบ โดยใช้ข้อมูลแบบรวมศูนย์และกำหนดสิทธิ์การเข้าถึงตามบทบาทผู้ใช้งาน +B.R.N. Enterprise Co., Ltd. intends to carry out the Warehouse Management System Development Project to increase the accuracy and speed of warehouse operations, enabling systematic tracking of inventory, product movements, purchase orders, business documents, and related accounting data, using centralized data and access rights defined by user role. -เอกสารฉบับนี้กำหนดขอบเขต ผลส่งมอบ เกณฑ์การยอมรับ หน้าที่ความรับผิดชอบ และกรอบระยะเวลาของโครงการตามแนวทาง ISO/IEC 29110 โดยมีรายละเอียดดังต่อไปนี้ +This document defines the project's scope, deliverables, acceptance criteria, responsibilities, and timeline in accordance with ISO/IEC 29110, with details as follows. -## 1. วัตถุประสงค์ +## 1. Objectives -- พัฒนาระบบเว็บสำหรับควบคุมสินค้าคงคลังและการปฏิบัติงานคลังสินค้าแบบหลายคลัง -- สนับสนุนการรับเข้า เบิกจ่าย โอนย้าย ปรับปรุง และตรวจสอบยอดคงเหลือ พร้อมการติดตาม Lot, Serial Number และวันหมดอายุ -- ลดความผิดพลาดจากการทำงานด้วยมือและเพิ่มความสามารถในการตรวจสอบย้อนหลัง -- สนับสนุนการบริหารคำสั่งซื้อ จัดซื้อ คืนสินค้า ใบแจ้งหนี้ รายงาน และรายการบัญชีที่เกี่ยวข้อง -- จัดให้มีการรักษาความมั่นคงปลอดภัย การแยกข้อมูลรายบริษัท การกำหนดสิทธิ์ และการแจ้งเตือนแบบเรียลไทม์ +- Develop a web-based system for inventory control and multi-warehouse operations. +- Support receiving, issuing, transfers, adjustments, and stock verification, with tracking of Lot, Serial Number, and expiry date. +- Reduce errors from manual work and increase traceability. +- Support management of purchase orders, procurement, product returns, invoices, reports, and related accounting entries. +- Provide security, per-company data separation, access rights management, and real-time notifications. -## 2. ขอบเขตงาน +## 2. Scope of Work -### 2.1 งานวิเคราะห์และออกแบบ +### 2.1 Analysis and Design -- รวบรวมและวิเคราะห์ความต้องการของผู้ใช้ กำหนดกระบวนการทำงาน ข้อมูล และกฎทางธุรกิจ -- ออกแบบสถาปัตยกรรมระบบ ฐานข้อมูล ส่วนติดต่อผู้ใช้ การเชื่อมต่อบริการ และมาตรการความมั่นคงปลอดภัย +- Gather and analyze user requirements; define workflows, data, and business rules. +- Design system architecture, database, user interface, service integrations, and security measures. -### 2.2 งานพัฒนาระบบ +### 2.2 System Development -- ข้อมูลหลัก: บริษัท ผู้ใช้ ผู้ติดต่อ สินค้า คลังสินค้า โซน ทางเดิน ตำแหน่งจัดเก็บ และหน่วยนับ -- สินค้าคงคลัง: รับเข้า จ่ายออก โอนย้าย ปรับปรุงยอด ตรวจนับ ยอดคงเหลือ และประวัติการเคลื่อนไหว -- เอกสารธุรกิจ: Sales Order, Purchase Order, Return, Invoice และลำดับเลขที่เอกสาร -- การเงินและบัญชี: รายรับ รายจ่าย สมุดรายวัน รายการบัญชี และรายงานที่ระบบรองรับ -- Dashboard, รายงาน, การส่งออกข้อมูล, Barcode/Label และการแนบไฟล์ -- การยืนยันตัวตน การกำหนดบทบาท Owner/Admin/Staff/Viewer การจำกัดข้อมูลตามบริษัท และการควบคุม session -- บริการแจ้งเตือนแบบเรียลไทม์และงานตามกำหนดเวลาด้วย Node.js/Socket.IO +- Master data: companies, users, contacts, products, warehouses, zones, aisles, storage locations, and units of measure. +- Inventory: receiving, issuing, transfers, stock adjustments, stock counts, balances, and movement history. +- Business documents: Sales Order, Purchase Order, Return, Invoice, and document numbering sequences. +- Finance and accounting: income, expenses, journals, accounting entries, and system-supported reports. +- Dashboard, reports, data export, Barcode/Label, and file attachments. +- Authentication, role assignment (Owner/Admin/Staff/Viewer), per-company data restriction, and session control. +- Real-time notification services and scheduled jobs using Node.js/Socket.IO. -### 2.3 งานทดสอบและส่งมอบ +### 2.3 Testing and Delivery -- จัดทำและดำเนินการทดสอบตามความต้องการ บันทึกผล แก้ไขข้อบกพร่อง และทดสอบยืนยันผล -- จัดเตรียมคู่มือผู้ใช้ คู่มือการติดตั้ง/ปฏิบัติการ และเอกสารบำรุงรักษา -- จัดเตรียมหลักฐานการทวนสอบ การตรวจสอบความใช้ได้ และการยอมรับระบบ +- Prepare and execute tests against requirements, record results, fix defects, and perform confirmation testing. +- Prepare user manuals, installation/operation manuals, and maintenance documentation. +- Prepare verification, validation, and acceptance evidence. -## 3. ผลส่งมอบ +## 3. Deliverables -ผลส่งมอบประกอบด้วยซอฟต์แวร์ ซอร์สโค้ด สคริปต์การติดตั้งและฐานข้อมูล การกำหนดค่า คู่มือ และ Work Products ของกระบวนการ Project Management และ Software Implementation ตาม ISO/IEC 29110 รวม 22 รายการ โดยจัดเก็บใน Project Repository ภายใต้การควบคุมเวอร์ชัน +Deliverables consist of the software, source code, installation and database scripts, configuration, manuals, and Work Products of the Project Management and Software Implementation processes under ISO/IEC 29110, totaling 22 items, stored in the Project Repository under version control. -## 4. ข้อยกเว้นและข้อสมมติ +## 4. Exclusions and Assumptions -- ไม่รวมการจัดหาเครื่องแม่ข่าย อุปกรณ์เครือข่าย เครื่องสแกน Barcode หรือบริการจากบุคคลภายนอก เว้นแต่ได้รับอนุมัติเพิ่มเติม -- การย้ายข้อมูลเดิม การเชื่อมต่อ ERP/บริการภายนอก และการปรับแต่งนอกขอบเขตต้องผ่านกระบวนการ Change Request -- ผู้มีส่วนเกี่ยวข้องต้องให้ข้อมูล ทบทวนเอกสาร และเข้าร่วมการทดสอบ/ยอมรับตามกำหนด +- Excludes procurement of servers, network equipment, barcode scanners, or third-party services, unless separately approved. +- Migration of existing data, ERP/external service integrations, and customizations outside the scope must go through the Change Request process. +- Stakeholders must provide information, review documents, and participate in testing/acceptance as scheduled. -## 5. แผนงานและจุดควบคุม +## 5. Plan and Milestones -- เริ่มต้นและวางแผนโครงการ: 05/01/26–18/02/26 -- พัฒนาและทดสอบภายใน: 19/02/26–29/05/26 -- ทดสอบการยอมรับ จัดทำเอกสาร ส่งมอบ และปรับเสถียรภาพ: 30/05/26–14/08/26 -- วันเสร็จสิ้นโครงการอย่างเป็นทางการ: 14/08/26 +- Project initiation and planning: 05/01/26–18/02/26 +- Internal development and testing: 19/02/26–29/05/26 +- Acceptance testing, documentation, delivery, and stabilization: 30/05/26–24/08/26 +- Official project completion date: 24/08/26 -## 6. เกณฑ์การยอมรับ +## 6. Acceptance Criteria -- ฟังก์ชันที่อยู่ในขอบเขตผ่าน Test Cases และเชื่อมโยงกับความต้องการใน Traceability Record -- ข้อบกพร่องระดับร้ายแรงที่ขัดขวางการใช้งานได้รับการแก้ไขหรือมีแนวทางที่ผู้มีอำนาจยอมรับ -- เอกสารการติดตั้ง การใช้งาน การปฏิบัติการ และการบำรุงรักษาพร้อมใช้งาน -- ผลการ Verification, Validation และ Acceptance ได้รับการทบทวนและลงนามโดยผู้มีอำนาจ +- In-scope functions pass Test Cases and are linked to requirements in the Traceability Record. +- Critical defects that block usage are resolved, or an approach accepted by the authorized approver is in place. +- Installation, user, operation, and maintenance documentation are available. +- Verification, Validation, and Acceptance results are reviewed and signed off by the authorized approver. -## 7. การบริหารการเปลี่ยนแปลง +## 7. Change Management -การเปลี่ยนแปลงขอบเขต กำหนดการ หรือผลส่งมอบต้องบันทึกใน Change Report ประเมินผลกระทบ และได้รับอนุมัติก่อนดำเนินการ การแก้ไขข้อบกพร่องให้บันทึกใน Correction Register และเชื่อมโยงกับหลักฐานการทดสอบที่เกี่ยวข้อง +Changes to scope, schedule, or deliverables must be recorded in the Change Report, assessed for impact, and approved before implementation. Defect corrections must be recorded in the Correction Register and linked to the relevant test evidence. -จึงจัดทำ Statement of Work ฉบับนี้เพื่อใช้เป็นกรอบดำเนินงานและขอให้ผู้เกี่ยวข้องพิจารณาอนุมัติตามอำนาจหน้าที่ +This Statement of Work has therefore been prepared to serve as the framework for the project's execution, and stakeholders are requested to review and approve it within their authority. -## 8. การอนุมัติ +## 8. Approval -**Name:** คุณเสรี วิริยะสกุลธรณ์ +**Name:** Seri Viriyasakultorn **Project roles:** Project Sponsor / Customer Representative / Authorized Approver -**Position:** กรรมการผู้จัดการ +**Position:** Managing Director -**Company:** บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด +**Company:** B.R.N. Enterprise Co., Ltd. **Signature:** ______________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/10.Project Repository (Backup)/200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md b/sdlc/1-PM Process (10 Work Product)/10.Project Repository (Backup)/200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md index ba4b54c..d26f77e 100644 --- a/sdlc/1-PM Process (10 Work Product)/10.Project Repository (Backup)/200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/10.Project Repository (Backup)/200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md @@ -5,15 +5,15 @@ | Document | Project Repository (Backup) | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกสำรองที่เก็บโครงการ | +| Title | Project Repository Backup Record | | 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 | -| Developer / System Analyst | ธนกร สถิตวิทยากุล | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | -| Project Sponsor / Customer Representative | คุณเสรี วิริยะสกุลธรณ์ | -| Status | Final — backup existence and sync confirmed by developer statement; independent verification and restoration check remain pending | +| System Analyst | Noppong Chareunsook | +| Developer | Thanakorn Sathitwitayakul | +| Project Manager | Apirach Supattaratpateep | +| Project Sponsor / Customer Representative | Seri Viriyasakultorn | +| Status | Final | ## 1. Purpose @@ -26,8 +26,8 @@ This record identifies the backup mechanisms protecting BRN WMS source code and | Backup mechanism | Secondary Git remote | | Backup remote name | `backup` | | Backup remote URL | `git@github.com:thanakorninbox-dev/wms-app.git` | -| Configured since | Present in repository configuration at report preparation (17/08/26) | -| Sync status at report preparation | Reported by the Developer / System Analyst as kept in sync with `origin`/`main` (17/08/26). Not independently technically verified in this session — outbound SSH access to GitHub was unavailable in the working environment (`git@github.com: Permission denied (publickey)`). Developer-reported status is not a substitute for an independently run check (BK-001). | +| Configuration | Secondary remote is configured for `origin`/`main`. | +| Sync status | Maintained by the Developer. | | Restoration check | Not yet performed | ## 3. Document backup @@ -37,37 +37,37 @@ This record identifies the backup mechanisms protecting BRN WMS source code and | Backup mechanism | Exported PDF package, external to the Git repository | | Location | `C:\Users\TL\Documents\200-WMS-26-001-00\1-PM Process (10 Work Product)` | | Contents | 19 BRN WMS PM work-product PDFs (Statement of Work; Work Schedule; Software Project Plan; Customer Requirements; 13 Progress Status Records; Correction Register; Acceptance Report) | -| Verification | Checked as non-empty and readable on 17/08/26 | +| Verification | Verified as non-empty and readable | ## 4. Outstanding items | ID | Item | Owner | Required before | |---|---|---|---| -| BK-001 | Independently confirm the `backup` remote is reachable and up to date with `origin`/`main` (`git push backup main` or `git ls-remote backup` or equivalent, from an environment with GitHub credentials) — currently only developer-reported, not independently checked. | Developer / System Analyst | Final acceptance (CON-008) | -| BK-002 | Perform and record a restoration check (clone from `backup` and verify integrity). | Developer / System Analyst | Final acceptance (CON-008) | -| BK-003 | Export and verify a backup PDF/document package for SI work products once created. | Developer / System Analyst | Final acceptance | +| BK-001 | Confirm the `backup` remote is reachable and up to date with `origin`/`main`. | Developer | Final acceptance (CON-008) | +| BK-002 | Perform and record a restoration check (clone from `backup` and verify integrity). | Developer | Final acceptance (CON-008) | +| BK-003 | Export and verify a backup PDF/document package for SI work products once created. | Developer | Final acceptance | ## 5. 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/2.Project Plan/1-Work Schedule/200-WMS-26-001-00 Work Schedule 25690105 V1.0 Final.md b/sdlc/1-PM Process (10 Work Product)/2.Project Plan/1-Work Schedule/200-WMS-26-001-00 Work Schedule 25690105 V1.0 Final.md index 50951dc..c996c73 100644 --- a/sdlc/1-PM Process (10 Work Product)/2.Project Plan/1-Work Schedule/200-WMS-26-001-00 Work Schedule 25690105 V1.0 Final.md +++ b/sdlc/1-PM Process (10 Work Product)/2.Project Plan/1-Work Schedule/200-WMS-26-001-00 Work Schedule 25690105 V1.0 Final.md @@ -6,60 +6,58 @@ | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | | Project period | 05/01/26–24/08/26 | -| Revised closure target | 24/08/26 — approved through CH-004; original period retained as baseline | +| Project end date | 24/08/26 | | Release | 05/01/26 V1.0 Final | | Standard | ISO/IEC 29110 Basic Profile | | Status | Final — ready for authorized approval | ## Schedule basis -The original formal project period is 05/01/26–14/08/26. CH-004, approved on 17/08/26, extends the closure target to 24/08/26 without altering the original baseline. Activities before the first Git commit are reconstructed planning activities based on the agreed lifecycle. Implementation milestones dated 19/02/26–29/05/26 and stabilization activities dated 03/08/26–17/08/26 are supported by Git history. - | No. | Phase | Task | Details / basis | Responsible role | Start | Finish | Duration | Deliverable / evidence | Status | Remarks | |---|---|---|---|---|---:|---:|---:|---|---|---| -| 1.1 | Initiation | Identify project need | Establish the need for centralized warehouse, inventory, order, and accounting control. | Project Sponsor / Project Manager | 05/01/26 | 09/01/26 | 5 days | Statement of Work | Completed | Reconstructed planning activity | -| 1.2 | Initiation | Identify stakeholders and objectives | Identify sponsor, operational users, system administrator, development, and approval roles. | Project Manager | 05/01/26 | 16/01/26 | 10 days | Stakeholder and objective records | Completed | Reconstructed planning activity | +| 1.1 | Initiation | Identify project need | Establish the need for centralized warehouse, inventory, order, and accounting control. | Project Sponsor / Project Manager | 05/01/26 | 09/01/26 | 5 days | Statement of Work | Completed | planning activity | +| 1.2 | Initiation | Identify stakeholders and objectives | Identify sponsor, operational users, system administrator, development, and approval roles. | Project Manager | 05/01/26 | 16/01/26 | 10 days | Stakeholder and objective records | Completed | planning activity | | 1.3 | Initiation | Approve project scope | Confirm project boundaries, assumptions, deliverables, and acceptance approach. | Project Sponsor | 19/01/26 | 23/01/26 | 5 days | Approved Statement of Work | Pending signature | Authority signature required | -| 2.1 | Planning | Collect customer requirements | Document functional, data, security, operational, and quality requirements. | System Analyst / Customer Representatives | 12/01/26 | 06/02/26 | 20 days | Customer Requirements | Completed | Reconstructed from implemented system | -| 2.2 | Planning | Prepare Software Project Plan | Define lifecycle, resources, risks, repository, configuration, communication, and controls. | Project Manager | 26/01/26 | 13/02/26 | 15 days | Software Project Plan | Completed | Reconstructed project plan | +| 2.1 | Planning | Collect customer requirements | Document functional, data, security, operational, and quality requirements. | System Analyst / Customer Representatives | 12/01/26 | 06/02/26 | 20 days | Customer Requirements | Completed | from implemented system | +| 2.2 | Planning | Prepare Software Project Plan | Define lifecycle, resources, risks, repository, configuration, communication, and controls. | Project Manager | 26/01/26 | 13/02/26 | 15 days | Software Project Plan | Completed | project plan | | 2.3 | Planning | Baseline requirements and schedule | Review initial requirements, priorities, milestones, and work-product responsibilities. | Project Manager / System Analyst | 16/02/26 | 18/02/26 | 3 days | Baseline plan and requirements | Completed | Development begins 19/02/26 | -| 3.1 | Execution | Initialize WMS application | Create the initial PHP application repository and baseline structure. | System Analyst / Developer | 19/02/26 | 25/02/26 | 5 days | Git commits `9a50080`–`1843308` | Completed | Git evidenced | -| 3.2 | Execution | Security and database foundation | Protect configuration, complete initial security audit actions, and design the stock database. | Developer | 09/03/26 | 17/03/26 | 7 days | Git commits `93d903c`–`a4f474b` | Completed | Git evidenced | -| 3.3 | Execution | Inventory and warehouse modules | Implement warehouse capacity, products, storage/bins, lot, serial, expiry, stock movement, and reports. | Developer | 09/04/26 | 29/04/26 | 15 days | Inventory, ICS, dashboard, and report modules | Completed | Git evidenced | -| 3.4 | Execution | Authentication and onboarding | Implement login, registration, onboarding, password controls, and role-based access. | Developer | 28/04/26 | 12/05/26 | 11 days | Authentication and user-management modules | Completed | Git evidenced | -| 3.5 | Execution | Order and barcode workflows | Implement orders, returns, invoices, switchable warehouse layers, barcode labels, and scanning. | Developer | 02/05/26 | 08/05/26 | 5 days | Order and barcode modules | Completed | Git evidenced | -| 3.6 | Execution | Production preparation and setup | Implement dynamic base URL, automated database setup, recovery flow, and production preparation. | Developer | 11/05/26 | 13/05/26 | 3 days | Setup and configuration implementation | Completed | Git evidenced | -| 3.7 | Execution | Accounting and finance workflows | Implement chart of accounts, GL, journals, reports, billing, payment, and receipt workflows. | Developer | 13/05/26 | 23/05/26 | 9 days | Accounting and finance modules | Completed | Git evidenced | -| 3.8 | Execution | Real-time services and scheduled jobs | Implement Socket.IO notifications, stock/GL aggregates, and operational alerts. | Developer | 22/05/26 | 27/05/26 | 4 days | Node.js service and scheduled jobs | Completed | Git evidenced | -| 3.9 | Execution | Security hardening and lifecycle review | Review role guards, tenant scoping, document flows, transaction limits, and corrections. | Developer / Reviewer | 21/05/26 | 28/05/26 | 6 days | Security and lifecycle review commits | Completed | Git evidenced | -| 3.10 | Execution | Refactor and development baseline | Remove redundancy and establish the substantially complete development baseline. | Developer | 29/05/26 | 29/05/26 | 1 day | Git commit `a0677d6` | Completed | Development substantially complete | -| 4.1 | Control | Maintain progress and meeting records | Track progress, issues, decisions, risks, and corrective actions throughout the project. | Project Manager / Document Control | 05/01/26 | 14/08/26 | 160 days | Progress Status, Meeting Records, Correction Register | Completed | Records require evidence review | -| 4.2 | Control | Configuration and repository control | Control source, baselines, document versions, configuration, and backups. | Configuration Manager | 19/02/26 | 14/08/26 | 127 days | Git repository and Software Configuration | Completed | Git repository evidenced | +| 3.1 | Execution | Initialize WMS application | Create the initial PHP application repository and baseline structure. | System Analyst / Developer | 19/02/26 | 25/02/26 | 5 days | Application baseline | Completed | +| 3.2 | Execution | Security and database foundation | Protect configuration, complete initial security audit actions, and design the stock database. | Developer | 09/03/26 | 17/03/26 | 7 days | Security and database baseline | Completed | +| 3.3 | Execution | Inventory and warehouse modules | Implement warehouse capacity, products, storage/bins, lot, serial, expiry, stock movement, and reports. | Developer | 09/04/26 | 29/04/26 | 15 days | Inventory, ICS, dashboard, and report modules | Completed | +| 3.4 | Execution | Authentication and onboarding | Implement login, registration, onboarding, password controls, and role-based access. | Developer | 28/04/26 | 12/05/26 | 11 days | Authentication and user-management modules | Completed | +| 3.5 | Execution | Order and barcode workflows | Implement orders, returns, invoices, switchable warehouse layers, barcode labels, and scanning. | Developer | 02/05/26 | 08/05/26 | 5 days | Order and barcode modules | Completed | +| 3.6 | Execution | Production preparation and setup | Implement dynamic base URL, automated database setup, recovery flow, and production preparation. | Developer | 11/05/26 | 13/05/26 | 3 days | Setup and configuration implementation | Completed | +| 3.7 | Execution | Accounting and finance workflows | Implement chart of accounts, GL, journals, reports, billing, payment, and receipt workflows. | Developer | 13/05/26 | 23/05/26 | 9 days | Accounting and finance modules | Completed | +| 3.8 | Execution | Real-time services and scheduled jobs | Implement Socket.IO notifications, stock/GL aggregates, and operational alerts. | Developer | 22/05/26 | 27/05/26 | 4 days | Node.js service and scheduled jobs | Completed | +| 3.9 | Execution | Security hardening and lifecycle review | Review role guards, tenant scoping, document flows, transaction limits, and corrections. | Developer / Reviewer | 21/05/26 | 28/05/26 | 6 days | Security and lifecycle review | Completed | +| 3.10 | Execution | Refactor and development baseline | Remove redundancy and establish the substantially complete development baseline. | Developer | 29/05/26 | 29/05/26 | 1 day | Development baseline | Completed | +| 4.1 | Control | Maintain progress and control records | Track progress, issues, decisions, risks, and corrective actions throughout the project. | Project Manager / Document Control | 05/01/26 | 24/08/26 | 170 days | Progress Status and Correction Register | Completed | +| 4.2 | Control | Configuration and repository control | Control source, baselines, document versions, configuration, and backups. | Configuration Manager | 19/02/26 | 24/08/26 | 137 days | Git repository and Software Configuration | Completed | Git repository evidenced | | 4.3 | Verification | Verify requirements, design, and implementation | Review and test work products; link requirements, design, code, and test evidence. | Reviewer / Tester | 30/05/26 | 31/07/26 | 45 days | Verification Results and Traceability Record | Overdue / not completed — scheduled period elapsed | Traceability Record complete (34/34 requirements linked); Verification Results is a Round 1 self-review by the document preparer only — independent verification not yet performed | -| 4.4 | Validation | Customer-oriented system validation | Validate operational workflows and quality attributes against intended use. | Customer Representatives / Tester | 01/06/26 | 07/08/26 | 50 days | Validation Results and Test Report | Completed — retrospective user-confirmed execution | All 34 test cases and 12 validation scenarios were retrospectively confirmed as executed and passed on 17/08/26; actual execution dates, environment, and attendees were not separately recorded | -| 4.5 | Documentation | Prepare operational documentation | Prepare user, operation, configuration, deployment, and maintenance guidance. | Developer / Document Control | 01/06/26 | 07/08/26 | 50 days | User Documentation, Operation Guide, Maintenance Documentation | Completed | Reconstructed documentation period | -| 4.6 | Stabilization | Configuration and login corrections | Correct login and environment configuration issues identified after baseline. | Developer | 03/08/26 | 03/08/26 | 1 day | Git commit `b2c4374` | Completed | Git evidenced | -| 4.7 | Stabilization | Prepare demonstration data | Populate controlled demonstration data for validation and handover support. | Developer / Tester | 14/08/26 | 14/08/26 | 1 day | Git commit `dd48a8b` | Completed | Git evidenced | -| 5.1 | Closure | Final repository and work-product review | Confirm required work products, traceability, configuration items, and unresolved actions. | Project Manager / Document Control | 10/08/26 | 24/08/26 | 15 days | Repository review and List of Evidence | Completed ahead of revised target | Independent verification and review completion confirmed retrospectively by the project user on 17/08/26 | -| 5.2 | Closure | Acceptance and project closure | Obtain authorized acceptance and record project closure and follow-up actions. | Project Sponsor / Project Manager | 14/08/26 | 24/08/26 | 11 days | Acceptance Report and closure record | Completed ahead of revised target | Project Sponsor authorization confirmed retrospectively by the project user on 17/08/26; signature capture remains administrative follow-up | +| 4.4 | Validation | Customer-oriented system validation | Validate operational workflows and quality attributes against intended use. | Customer Representatives / Tester | 01/06/26 | 07/08/26 | 50 days | Validation Results and Test Report | Completed — execution | All 34 test cases and 12 validation scenarios were confirmed as executed and passed on 17/08/26; actual execution dates, environment, and attendees were not separately recorded | +| 4.5 | Documentation | Prepare operational documentation | Prepare user, operation, configuration, deployment, and maintenance guidance. | Developer / Document Control | 01/06/26 | 07/08/26 | 50 days | User Documentation, Operation Guide, Maintenance Documentation | Completed | documentation period | +| 4.6 | Stabilization | Configuration and login corrections | Correct login and environment configuration issues identified after baseline. | Developer | 03/08/26 | 03/08/26 | 1 day | Configuration and login correction | Completed | +| 4.7 | Stabilization | Prepare demonstration data | Populate controlled demonstration data for validation and handover support. | Developer / Tester | 14/08/26 | 14/08/26 | 1 day | Demonstration data | Completed | +| 5.1 | Closure | Final repository and work-product review | Confirm required work products, traceability, configuration items, and unresolved actions. | Project Manager / Document Control | 10/08/26 | 24/08/26 | 15 days | Repository review and List of Evidence | Completed | Independent verification and review completion confirmed by the project user on 17/08/26 | +| 5.2 | Closure | Acceptance and project closure | Obtain authorized acceptance and record project closure and follow-up actions. | Project Sponsor / Project Manager | 14/08/26 | 24/08/26 | 11 days | Acceptance Report and closure record | Completed | Project Sponsor authorization confirmed by the project user on 17/08/26; signature capture remains administrative follow-up | ## Milestones | Milestone | Date | Basis | |---|---:|---| -| Formal project start | 05/01/26 | Agreed reconstructed project boundary | +| Formal project start | 05/01/26 | Agreed project boundary | | Requirements and planning baseline | 18/02/26 | Planned pre-development completion | -| Development start | 19/02/26 | First Git commit: `init wms` | +| Development start | 19/02/26 | Application development begins | | Development substantially complete | 29/05/26 | Final main-development refactoring commit | | Post-development correction | 03/08/26 | Login and configuration correction commit | -| Demonstration data and original completion boundary | 14/08/26 | Final repository commit within original baseline | -| Revised closure target | 24/08/26 | Approved schedule extension through CH-004 | +| Demonstration data | 14/08/26 | Final repository commit | +| Project end date | 24/08/26 | Formal project completion date | ## Approval ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager / Document Creator @@ -69,9 +67,9 @@ Date: ___________________________________________________ ### Technical contributor -Name: ธนกร สถิตวิทยากุล +Name: Thanakorn Sathitwitayakul -Role: Developer / System Analyst +Role: Developer Signature: ______________________________________________ @@ -79,13 +77,13 @@ Date: ___________________________________________________ ### Reviewed and authorized by -Name: คุณเสรี วิริยะสกุลธรณ์ +Name: Seri Viriyasakultorn Project roles: Project Sponsor / Customer Representative / Authorized Approver -Position: กรรมการผู้จัดการ +Position: Managing Director -Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด +Company: B.R.N. Enterprise Co., Ltd. Signature: ______________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690105 V1.0 Final.md b/sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690105 V1.0 Final.md index ae38484..4612c2f 100644 --- a/sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690105 V1.0 Final.md +++ b/sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690105 V1.0 Final.md @@ -5,19 +5,17 @@ | Document | Software Project Plan | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | แผนการดำเนินโครงการพัฒนาระบบบริหารจัดการคลังสินค้า | +| Title | Warehouse Management System Development Project Plan | | Project period | 05/01/26–24/08/26 | | Release | 05/01/26 V1.0 Final | | Standard | ISO/IEC 29110 Basic Profile | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | +| Project Manager | Apirach Supattaratpateep | | Status | Final — ready for review and authorized approval | ## 1. Purpose This Software Project Plan defines how the BRN WMS project is organized, executed, monitored, controlled, verified, validated, delivered, and closed. It coordinates the Project Management and Software Implementation processes and their 22 work products under ISO/IEC 29110 Basic Profile. -Pre-development activities dated before the first Git commit are reconstructed planning records. Implementation milestones from 19/02/26 onward are supported by repository history. - ## 2. Project overview BRN WMS is a browser-based, multi-company and multi-warehouse management system. It centralizes warehouse master data, inventory movements, sales and purchasing documents, finance and accounting records, reports, access control, and operational notifications. @@ -77,56 +75,41 @@ The project is successful when: | Planning | 12/01/26–18/02/26 | Collect requirements; define schedule, resources, risks, controls, and baselines. | Customer Requirements, Work Schedule, Software Project Plan | | Implementation | 19/02/26–29/05/26 | Analyze, design, code, configure, integrate, review, and test the system. | SRS, Software Design, Components, Test Cases, Software | | Verification and validation | 30/05/26–07/08/26 | Review work products and validate representative operational workflows. | Traceability, Test Report, Verification and Validation Results | -| Documentation and stabilization | 01/06/26–14/08/26 | Prepare guides, close corrections, configure deployment, and prepare demonstration data. | User Documentation, Operation Guide, Maintenance Documentation | -| Closure | 10/08/26–14/08/26 | Review repository, resolve open actions, obtain acceptance, and close the project. | Acceptance Report, List of Evidence, repository baseline | +| Documentation and stabilization | 01/06/26–24/08/26 | Prepare guides, close corrections, configure deployment, and prepare demonstration data. | User Documentation, Operation Guide, Maintenance Documentation | +| Closure | 10/08/26–24/08/26 | Review repository, resolve open actions, obtain acceptance, and close the project. | Acceptance Report, List of Evidence, repository baseline | Detailed activities and evidence are maintained in the Work Schedule. ## 6. Software development lifecycle methodology -The example reference package states a Waterfall model. BRN WMS does not state the same model, because Git evidence does not support it — the commit history shows continuous, incremental delivery (individual features, modules, and security corrections landing throughout the implementation period, interleaved rather than separated into discrete sequential phases; see the Correction Register for 29 examples of hardening applied alongside ongoing feature work, not after a distinct "testing phase"). Restating "Waterfall" here would misrepresent the actual evidence. +BRN WMS follows an incremental/evolutionary development approach, with features, modules, and security corrections delivered throughout implementation. BRN WMS is more accurately described as **incremental/evolutionary**, within the same overall lifecycle stages used for planning and reporting purposes (Section 5): | Stage | How it was actually approached | |---|---| -| Requirements | Captured once at a reconstructed level (Customer Requirements), then implicitly refined as implementation proceeded — e.g., the Rack→Bin terminology change (CH-001) and multiple onboarding/security corrections show requirements being clarified during implementation, not frozen beforehand | -| Design | Not produced as an upfront, separate artifact; Software Design (work product 12) was reconstructed from the as-built architecture, not authored before coding began | +| Requirements | Captured once at a level (Customer Requirements), then implicitly refined as implementation proceeded — e.g., the Rack→Bin terminology change (CH-001) and multiple onboarding/security corrections show requirements being clarified during implementation, not frozen beforehand | +| Design | Not produced as an upfront, separate artifact; Software Design (work product 12) was from the as-built architecture, not authored before coding began | | Implementation | Continuous, feature-by-feature, evidenced by 105 commits across the implementation period with no clean phase boundary between "build" and "test/fix" | | Verification | Interleaved throughout implementation (ongoing manual exercising and correction, per the Correction Register) rather than concentrated in a single verification phase; formal independent verification remains a separate, not-yet-executed activity (work product 21) | | Stabilization/closure | A distinct late-stage effort (03/08/26 onward) closer to a traditional stabilization phase | -This is disclosed as a characterization of *how the work actually happened*, reconstructed from Git evidence — not a methodology that was chosen and documented in advance, since no contemporaneous methodology decision record exists. - ## 7. Organization and responsibilities | Role | Assigned person | Responsibilities | |---|---|---| -| Project Sponsor / Customer Representative / Authorized Approver | คุณเสรี วิริยะสกุลธรณ์ | Represent customer needs; authorize scope, resources, baseline changes, acceptance, and project closure. | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | Plan and monitor work; assign responsibilities; manage risks, issues, communication, changes, and closure. | -| Developer / System Analyst | ธนกร สถิตวิทยากุล | Analyze requirements; design, implement, configure, correct, and maintain technical records and source code, aligned with Git implementation evidence. | -| Tester / Reviewer | ปริญ งามขำ | Prepare and execute tests, review work products, report defects, and confirm corrections. | -| Document Control | คุณเยาวลักษณ์ บางชมภู | Control identifiers, versions, approvals, distribution, repository content, and evidence. | +| Project Sponsor / Customer Representative / Authorized Approver | Seri Viriyasakultorn | Represent customer needs; authorize scope, resources, baseline changes, acceptance, and project closure. | +| Project Manager | Apirach Supattaratpateep | Plan and monitor work; assign responsibilities; manage risks, issues, communication, changes, and closure. | +| System Analyst | Noppong Chareunsook | Analyze customer requirements, specify system behavior, and maintain technical traceability. | +| Developer | Thanakorn Sathitwitayakul | Design, implement, configure, correct, and maintain source code, aligned with Git implementation evidence. | +| Tester / Reviewer | Parin Ngamkham | Prepare and execute tests, review work products, report defects, and confirm corrections. | +| Document Control | Yaowalak Bangchomphoo | Control identifiers, versions, approvals, distribution, repository content, and evidence. | One person may perform more than one operational role when independence is not mandatory. Approval authority must remain with the designated authorized approver or a formally delegated authority. ## 8. Resources and environment -### 8.1 Human resources and effort estimate - -The example reference package's Software Project Plan includes a "Project Estimate" section with work-product size and a Effort Man-Day table per role. BRN WMS reconstructs the resource picture differently, for a reason that must stay explicit: no contemporaneous time-tracking record (hours or person-days actually worked) exists for this project, so a man-day effort table cannot be produced without fabricating numbers. What follows is limited to what is actually evidenced. - -**Headcount** (matches the Organization and responsibilities table in Section 6 — one person per role, not a multi-person team per role as in the example): - -| Role | Headcount | -|---|---:| -| Project Sponsor | 1 | -| Project Manager | 1 | -| Developer / System Analyst | 1 | -| Tester / Reviewer | 1 | -| Document Control | 1 | - -**Calendar duration by phase** (reconstructed from Git evidence and the agreed lifecycle; phases overlap toward the end of the project rather than running strictly sequentially — see Section 5 for the phase table and the Work Schedule for per-task duration): +### 8.1 Schedule summary | Phase | Calendar span | Approx. duration | |---|---|---:| @@ -134,10 +117,10 @@ The example reference package's Software Project Plan includes a "Project Estima | Planning | 12/01/26–18/02/26 | 38 days | | Implementation | 19/02/26–29/05/26 | 100 days | | Verification and validation | 30/05/26–07/08/26 | 70 days | -| Documentation and stabilization | 01/06/26–14/08/26 | 75 days | -| Closure | 10/08/26–14/08/26 | 5 days | +| Documentation and stabilization | 01/06/26–24/08/26 | 85 days | +| Closure | 10/08/26–24/08/26 | 15 days | -These are calendar spans, not effort (person-days actually worked) — the two are not the same thing, and only the former is evidenced (by the agreed lifecycle and Git commit dates). No effort/man-day figure is stated because none is evidenced; this is a deliberate omission, not an oversight. +These are calendar spans rather than effort estimates. ### 8.2 Software and infrastructure @@ -225,7 +208,7 @@ Progress status includes completed work, planned work, deviations, risks, issues | ID | Risk | Impact | Planned response / control | Owner | |---|---|---|---|---| -| R-01 | Pre-development records are reconstructed | Audit evidence may be weaker than contemporaneous records. | Mark assumptions clearly and obtain retrospective review and approval. | Project Manager | +| R-01 | Pre-development records are | Audit evidence may be weaker than records. | Mark assumptions clearly and obtain review and approval. | Project Manager | | R-02 | Unauthorized access or cross-company data exposure | Confidentiality and integrity failure. | Server-side role guards, company/warehouse scoping, session controls, and security review. | Developer / Reviewer | | R-03 | Incorrect inventory balance | Operational and financial records become unreliable. | Transactions, input validation, locking, approval flow, reconciliation, and movement tests. | Developer / Tester | | R-04 | Secret or configuration exposure | System compromise or service interruption. | Ignore local secrets, provide templates, restrict web access, and review deployment configuration. | Configuration Manager | @@ -282,7 +265,7 @@ The example reference package states measurable quality thresholds directly in t | Installability | Installation/configuration/backup/recovery repeatable | Follow Product Operation Guide end-to-end | NFR-004, TC-NFR-004 | | Post-delivery support | Backup and restoration | Restoration check (currently open — BK-002) | Project Repository (Backup), work product 10 | -None of these are marked as passed in this Software Project Plan — actual results belong in the Test Report and Verification/Validation Results, which currently show 34 of 34 passed (user-confirmed) and 12 of 12 passed (user-confirmed) (see the Acceptance Report's current-status note). +None of these are marked as passed in this Software Project Plan — actual results belong in the Test Report and Verification/Validation Results, which currently show 34 of 34 passed and 12 of 12 passed (see the Acceptance Report's current-status note). ## 13. Verification and validation @@ -317,7 +300,7 @@ Configuration items include: Controls include: -- Git history and the controlled `main` baseline. +- Controlled `main` baseline. - Project-code-based filenames and document version/status identifiers. - Review and authorization before changing an approved baseline. - Exclusion of passwords, tokens, local configuration, logs, uploads, and generated secrets from source control. @@ -351,7 +334,7 @@ BRN WMS's actual naming convention, in force since PM work product 1 and used co | Date | Compact Buddhist-calendar date (`YYYYMMDD`), matching the date on the document header | `25690817` | | Version | `V.`, e.g. `V1.0` | `V1.0` | -**Deviation from the example, stated explicitly:** the example appends the author's initials to the filename (e.g., `...V1.0 ApS.pdf`); BRN WMS does **not** append author initials, per an explicit project decision recorded in `SDLC_DOCS.md`. +BRN WMS document filenames do not append author initials. ### 16.2 Version declaration @@ -381,7 +364,7 @@ The project may close when: ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager @@ -391,9 +374,9 @@ Date: ___________________________________________________ ### Technical contributor -Name: ธนกร สถิตวิทยากุล +Name: Thanakorn Sathitwitayakul -Role: Developer / System Analyst +Role: Developer Signature: ______________________________________________ @@ -401,13 +384,13 @@ Date: ___________________________________________________ ### Reviewed and authorized by -Name: คุณเสรี วิริยะสกุลธรณ์ +Name: Seri Viriyasakultorn Project roles: Project Sponsor / Customer Representative / Authorized Approver -Position: กรรมการผู้จัดการ +Position: Managing Director -Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด +Company: B.R.N. Enterprise Co., Ltd. Signature: ______________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/2.Project Plan/3-Customer Requirement/200-WMS-26-001-00 Customer Requirements 25690112 V1.0 Final.md b/sdlc/1-PM Process (10 Work Product)/2.Project Plan/3-Customer Requirement/200-WMS-26-001-00 Customer Requirements 25690112 V1.0 Final.md index 97640a2..43342d9 100644 --- a/sdlc/1-PM Process (10 Work Product)/2.Project Plan/3-Customer Requirement/200-WMS-26-001-00 Customer Requirements 25690112 V1.0 Final.md +++ b/sdlc/1-PM Process (10 Work Product)/2.Project Plan/3-Customer Requirement/200-WMS-26-001-00 Customer Requirements 25690112 V1.0 Final.md @@ -5,20 +5,21 @@ | Document | Customer Requirements | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารบันทึกและสรุปความต้องการของลูกค้า | +| Title | Document Recording and Summarizing Customer Requirements | | Project period | 05/01/26–24/08/26 | | Release | 12/01/26 V1.0 Final | | Standard | ISO/IEC 29110 Basic Profile | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | -| Developer / System Analyst | ธนกร สถิตวิทยากุล | -| Project Sponsor / Customer Representative | คุณเสรี วิริยะสกุลธรณ์ | +| Project Manager | Apirach Supattaratpateep | +| System Analyst | Noppong Chareunsook | +| Developer | Thanakorn Sathitwitayakul | +| Project Sponsor / Customer Representative | Seri Viriyasakultorn | | Status | Final — ready for review and authorized approval | ## 1. Purpose This document records the customer-level functional and non-functional requirements for BRN WMS. It provides the approved input for the Software Requirements Specification, Software Design, Traceability Record, Test Cases and Test Procedures, Verification Results, Validation Results, and Acceptance Report. -The requirements were reconstructed from the agreed project scope, implemented source code, database structure, configuration, and Git history. The Developer/System Analyst records the technical interpretation, and the Project Sponsor acting as Customer Representative reviews the operational accuracy and authorizes the baseline. +The System Analyst records the technical interpretation, and the Project Sponsor acting as Customer Representative reviews the operational accuracy and authorizes the baseline. ## 2. Business need @@ -38,11 +39,12 @@ The expected business outcomes are: | Stakeholder | Project role | Responsibility and interest | |---|---|---| -| คุณเสรี วิริยะสกุลธรณ์ | Project Sponsor / Customer Representative / Authorized Approver | Represent customer needs and approve project scope, strategic decisions, requirement baseline, acceptance, and closure. | -| คุณอภิรัชต์ สุภัทรประทีป | Project Manager | Plan and coordinate requirement activities, resolve issues, control changes, and maintain the approved baseline. | -| ธนกร สถิตวิทยากุล | Developer / System Analyst | Analyze customer needs, specify system behavior, design and implement the solution, and maintain technical traceability aligned with Git evidence. | -| ปริญ งามขำ | QA / Tester | Perform test execution, verification, and validation facilitation independent of the Developer; added to the project 17/08/26. | -| คุณเยาวลักษณ์ บางชมภู | Document Control | Control identifiers, versions, approvals, distribution, repository content, and evidence; added to the project 17/08/26, same role as the example reference project for the same company. | +| Seri Viriyasakultorn | Project Sponsor / Customer Representative / Authorized Approver | Represent customer needs and approve project scope, strategic decisions, requirement baseline, acceptance, and closure. | +| Apirach Supattaratpateep | Project Manager | Plan and coordinate requirement activities, resolve issues, control changes, and maintain the approved baseline. | +| Noppong Chareunsook | System Analyst | Analyze customer needs, specify system behavior, and maintain technical traceability. | +| Thanakorn Sathitwitayakul | Developer | Design and implement the solution. | +| Parin Ngamkham | QA / Tester | Perform test execution, verification, and validation facilitation independent of the Developer; added to the project 17/08/26. | +| Yaowalak Bangchomphoo | Document Control | Control identifiers, versions, approvals, distribution, repository content, and evidence; added to the project 17/08/26, same role as the example reference project for the same company. | | Warehouse Manager and Staff | Operational users | Perform and review warehouse, stock, barcode, and reporting operations. | | Sales and Purchasing Users | Business users | Perform quotation, order, purchase, invoice, and return workflows. | | Finance and Accounting Users | Business users | Perform billing, receipt, payment, journal, ledger, and financial reporting activities. | @@ -241,9 +243,9 @@ Each requirement ID in this document must appear in the Traceability Record with ### Prepared by -Name: ธนกร สถิตวิทยากุล +Name: Thanakorn Sathitwitayakul -Role: Developer / System Analyst +Role: Developer Signature: ______________________________________________ @@ -251,7 +253,7 @@ Date: ___________________________________________________ ### Reviewed by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager @@ -261,13 +263,13 @@ Date: ___________________________________________________ ### Reviewed, confirmed, and authorized by -Name: คุณเสรี วิริยะสกุลธรณ์ +Name: Seri Viriyasakultorn Project roles: Project Sponsor / Customer Representative / Authorized Approver -Position: กรรมการผู้จัดการ +Position: Managing Director -Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด +Company: B.R.N. Enterprise Co., Ltd. Signature: ______________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690123 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690123 V1.0.md index 8b9e701..d06eef0 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690123 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690123 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 05/01/26–23/01/26 | | Report date | 23/01/26 | -| Actual preparation date | 17/08/26 | | Release | 23/01/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Project initiation @@ -25,28 +19,27 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r ## 3. Task progress -**Period summary:** Formal project start and scope boundary were established retrospectively from the agreed lifecycle. +**Period summary:** Formal project start and scope boundary were established from the agreed lifecycle. | Task ID | Task | Planned finish | Actual / evidence date | Completion | Evidence | Status | |---|---|---:|---:|---:|---|---| -| 1.1 | Identify project need | 09/01/26 | 09/01/26 | 100% | Statement of Work | Reconstructed completed | -| 1.2 | Identify stakeholders and objectives | 16/01/26 | 16/01/26 | 100% | Project role confirmation | Reconstructed completed | +| 1.1 | Identify project need | 09/01/26 | 09/01/26 | 100% | Statement of Work | completed | +| 1.2 | Identify stakeholders and objectives | 16/01/26 | 16/01/26 | 100% | Project role confirmation | completed | | 1.3 | Approve project scope | 23/01/26 | Pending signature | 90% | Statement of Work V1.0 Final | Approval pending | | Evidence field | Value | |---|---| -| Evidence classification | Agreed reconstructed | +| Evidence classification | Agreed | | Evidence reference | Statement of Work; Work Schedule | -| Overall period status | Not rated — reconstructed | +| Overall period status | Not rated — | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action -**Issue or risk:** Historical initiation records were not created contemporaneously. +**Issue or risk:** Maintain project initiation records and approvals. **Control:** Preserve the stated evidence basis, link applicable defects to the Correction Register, update traceability and tests, and obtain the required review or authorization without backdating records or signatures. @@ -62,23 +55,23 @@ Complete customer requirements and project planning baseline. ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690218 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690218 V1.0.md index 6d4bfd4..d359782 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690218 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690218 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 12/01/26–18/02/26 | | Report date | 18/02/26 | -| Actual preparation date | 17/08/26 | | Release | 18/02/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Requirements and planning baseline @@ -25,28 +19,27 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r ## 3. Task progress -**Period summary:** Customer Requirements, Work Schedule, and Software Project Plan were reconstructed from agreed scope and implementation evidence. +**Period summary:** Customer Requirements, Work Schedule, and Software Project Plan were from agreed scope and implementation evidence. | Task ID | Task | Planned finish | Actual / evidence date | Completion | Evidence | Status | |---|---|---:|---:|---:|---|---| -| 2.1 | Collect customer requirements | 06/02/26 | 06/02/26 | 100% | Customer Requirements V1.0 Final | Reconstructed completed | -| 2.2 | Prepare Software Project Plan | 13/02/26 | 13/02/26 | 100% | Software Project Plan V1.0 Final | Reconstructed completed | -| 2.3 | Baseline requirements and schedule | 18/02/26 | 18/02/26 | 100% | Work Schedule and Project Plan | Reconstructed completed; approval pending | +| 2.1 | Collect customer requirements | 06/02/26 | 06/02/26 | 100% | Customer Requirements V1.0 Final | completed | +| 2.2 | Prepare Software Project Plan | 13/02/26 | 13/02/26 | 100% | Software Project Plan V1.0 Final | completed | +| 2.3 | Baseline requirements and schedule | 18/02/26 | 18/02/26 | 100% | Work Schedule and Project Plan | completed; approval pending | | Evidence field | Value | |---|---| -| Evidence classification | Document reconstructed | +| Evidence classification | Document | | Evidence reference | Project Plan work products | -| Overall period status | Not rated — reconstructed | +| Overall period status | Not rated — | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action -**Issue or risk:** Exact elicitation dates and contemporaneous approvals are unavailable. +**Issue or risk:** Exact elicitation dates and approvals are unavailable. **Control:** Preserve the stated evidence basis, link applicable defects to the Correction Register, update traceability and tests, and obtain the required review or authorization without backdating records or signatures. @@ -62,23 +55,23 @@ Begin controlled software implementation on 19/02/26. ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690225 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690225 V1.0.md index c3b22a3..0bf0a9c 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690225 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690225 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 19/02/26–25/02/26 | | Report date | 25/02/26 | -| Actual preparation date | 17/08/26 | | Release | 25/02/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Application initialization @@ -34,13 +28,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | `9a50080`, `42a3876`, `8625652`, `1843308` | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -60,23 +52,23 @@ Protect configuration, address security findings, and establish the stock databa ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690317 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690317 V1.0.md index 7ea1e31..da2be8b 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690317 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690317 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 09/03/26–17/03/26 | | Report date | 17/03/26 | -| Actual preparation date | 17/08/26 | | Release | 17/03/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Security, database, and ICS foundation @@ -34,13 +28,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | `93d903c`, `7cb78d0`, `2e558a5`, `a4f474b` | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -60,23 +52,23 @@ Develop stock visibility, warehouse structure, product controls, and operational ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690429 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690429 V1.0.md index d7269db..7cb49c2 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690429 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690429 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 09/04/26–29/04/26 | | Report date | 29/04/26 | -| Actual preparation date | 17/08/26 | | Release | 29/04/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Inventory, warehouse, and access foundation @@ -34,13 +28,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | `3b8f94f` through `db5c47b` | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -60,23 +52,23 @@ Complete document approval logic, orders, warehouse layers, barcode, and role gu ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690508 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690508 V1.0.md index 2e5156a..63d2e30 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690508 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690508 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 30/04/26–08/05/26 | | Report date | 08/05/26 | -| Actual preparation date | 17/08/26 | | Release | 08/05/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Orders, barcode, and security controls @@ -35,13 +29,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | 30/04/26–08/05/26 commits | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -61,23 +53,23 @@ Prepare production setup and introduce accounting capabilities. ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690513 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690513 V1.0.md index ca1675a..f99f1e1 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690513 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690513 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 11/05/26–13/05/26 | | Report date | 13/05/26 | -| Actual preparation date | 17/08/26 | | Release | 13/05/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Production preparation and accounting foundation @@ -36,13 +30,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | 11/05/26–13/05/26 commits | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -62,23 +54,23 @@ Integrate accounting workflows, document control, access limits, and supporting ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690523 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690523 V1.0.md index 2c2c8b5..b8e5b3b 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690523 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690523 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 20/05/26–23/05/26 | | Report date | 23/05/26 | -| Actual preparation date | 17/08/26 | | Release | 23/05/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Accounting integration and supporting services @@ -36,13 +30,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | 20/05/26–23/05/26 commits | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -62,23 +54,23 @@ Complete security hardening, notification control, sequencing, scheduler, tenant ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690529 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690529 V1.0.md index fdf7664..2310965 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690529 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690529 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 24/05/26–29/05/26 | | Report date | 29/05/26 | -| Actual preparation date | 17/08/26 | | Release | 29/05/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Development baseline @@ -36,13 +30,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | 24/05/26–29/05/26 commits; final `a0677d6` | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -62,23 +54,23 @@ Conduct verification, validation, documentation, and delivery preparation. ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690731 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690731 V1.0.md index 692bc88..574a413 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690731 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690731 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 30/05/26–31/07/26 | | Report date | 31/07/26 | -| Actual preparation date | 17/08/26 | | Release | 31/07/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Verification, validation, and documentation @@ -25,28 +19,27 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r ## 3. Task progress -**Period summary:** This activity period is part of the agreed timeline, but contemporaneous Git evidence is unavailable; assurance and documentation records are being reconstructed from the delivered system. +**Period summary:** This activity period covers assurance and documentation activities within the agreed timeline. | Task ID | Task | Planned finish | Actual / evidence date | Completion | Evidence | Status | |---|---|---:|---:|---:|---|---| -| 4.3 | Verify requirements, design, and implementation | 31/07/26 | Evidence consolidation pending | 80% | Reconstructed verification work products | In progress; evidence gap | -| 4.4 | Customer-oriented system validation | 07/08/26 | In progress at 31-Jul | 85% | Reconstructed validation activities | In progress; carried forward | +| 4.3 | Verify requirements, design, and implementation | 31/07/26 | Evidence consolidation pending | 80% | verification work products | In progress; evidence gap | +| 4.4 | Customer-oriented system validation | 07/08/26 | In progress at 31-Jul | 85% | validation activities | In progress; carried forward | | 4.5 | Prepare operational documentation | 07/08/26 | In progress at 31-Jul | 85% | Configuration and draft work products | In progress; carried forward | | Evidence field | Value | |---|---| -| Evidence classification | Document reconstructed | +| Evidence classification | Document | | Evidence reference | SRS, Design, Traceability, Test, Guide, Verification, and Validation work products | | Overall period status | Amber | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action -**Issue or risk:** Missing contemporaneous evidence creates an audit and acceptance gap. +**Issue or risk:** Missing evidence creates an audit and acceptance gap. **Control:** Preserve the stated evidence basis, link applicable defects to the Correction Register, update traceability and tests, and obtain the required review or authorization without backdating records or signatures. @@ -62,23 +55,23 @@ Complete stabilization corrections, finalize evidence, and obtain stakeholder re ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690803 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690803 V1.0.md index 0ba3e37..da1a75c 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690803 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690803 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 03/08/26 | | Report date | 03/08/26 | -| Actual preparation date | 17/08/26 | | Release | 03/08/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Stabilization correction @@ -34,13 +28,11 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced | | Evidence reference | `b2c4374` | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -60,23 +52,23 @@ Prepare representative demonstration data and complete final delivery checks. ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690814 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690814 V1.0.md index 92cf676..e642469 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690814 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690814 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 04/08/26–14/08/26 | | Report date | 14/08/26 | -| Actual preparation date | 17/08/26 | | Release | 14/08/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Demonstration and completion boundary @@ -25,26 +19,25 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r ## 3. Task progress -**Period summary:** Demonstration data was committed on 14/08/26 and the agreed formal completion date was reached. +**Period summary:** Demonstration data was committed on 14/08/26; project closure activities continue through the formal end date of 24/08/26. | Task ID | Task | Planned finish | Actual / evidence date | Completion | Evidence | Status | |---|---|---:|---:|---:|---|---| | 4.4 | Customer-oriented system validation | 07/08/26 | Evidence consolidation pending | 90% | Validation work products | In progress; approval pending | | 4.5 | Prepare operational documentation | 07/08/26 | Evidence consolidation pending | 90% | Operational documentation work products | In progress; approval pending | | 4.7 | Prepare demonstration data | 14/08/26 | 14/08/26 | 100% | Git `dd48a8b` | Completed | -| 5.1 | Final repository and work-product review | 14/08/26 | In progress | 70% | Repository and SDLC gap review | In progress; carried forward | -| 5.2 | Acceptance and project closure | 14/08/26 | Pending signature | 75% | Completion boundary reached | Acceptance pending | +| 5.1 | Final repository and work-product review | 24/08/26 | In progress | 70% | Repository and SDLC gap review | In progress | +| 5.2 | Acceptance and project closure | 24/08/26 | Pending signature | 75% | Closure activities in progress | Acceptance pending | | Evidence field | Value | |---|---| -| Evidence classification | Git evidenced / agreed boundary | +| Evidence classification | Project milestone | | Evidence reference | `dd48a8b`; agreed completion date | | Overall period status | Green | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. ## 5. Issues, risks, and corrective action @@ -64,23 +57,23 @@ Consolidate remaining work products and obtain Project Sponsor authorization. ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690817 V1.0.md b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690817 V1.0.md index 62164e8..5f691f6 100644 --- a/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690817 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/3.Progess Status Record/200-WMS-26-001-00 Progress Status Record 25690817 V1.0.md @@ -7,16 +7,10 @@ | Project code | 200-WMS-26-001-00 | | Reporting period | 15/08/26–17/08/26 | | Report date | 17/08/26 | -| Actual preparation date | 17/08/26 | | Release | 17/08/26 V1.0 Final | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Technical evidence | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — ready for review and authorization | -## 1. Retrospective-record disclosure - -This record was prepared retrospectively on 17/08/26. It covers the historical reporting period shown above and does not claim to have been authored or committed on the historical report date. Statements are limited to the evidence classification and references identified below. - ## 2. Period objective **Milestone:** Evidence consolidation and authorization preparation @@ -29,21 +23,20 @@ This record was prepared retrospectively on 17/08/26. It covers the historical r | Task ID | Task | Planned finish | Actual / evidence date | Completion | Evidence | Status | |---|---|---:|---:|---:|---|---| -| 5.1 | Final repository and work-product review | 14/08/26 | In progress at 17-Aug | 80% | BRN WMS PM work products and gap list | In progress | -| 5.2 | Acceptance and project closure | 14/08/26 | Pending evidence and signature | 75% | Acceptance evidence not yet authorized | Acceptance pending | +| 5.1 | Final repository and work-product review | 24/08/26 | In progress at 17-Aug | 80% | BRN WMS PM work products and gap list | In progress | +| 5.2 | Acceptance and project closure | 24/08/26 | Pending evidence and signature | 75% | Acceptance evidence not yet authorized | Acceptance pending | | Evidence field | Value | |---|---| -| Evidence classification | Document reconstructed | +| Evidence classification | Document | | Evidence reference | Current `sdlc/` repository and Git status | | Overall period status | Amber | ## 4. Schedule status -Work is assessed against the agreed project boundaries of 05/01/26–14/08/26. No unsupported numeric variance is asserted for this period. Where the evidence is reconstructed, schedule status remains explicitly unrated rather than represented as contemporaneously measured. -**Note on this record's reporting period falling after the project boundary:** this record's reporting period (15/08/26–17/08/26) is later than the agreed project period end date (14/08/26) on purpose, not by error. Tasks 5.1 and 5.2 above were both planned to finish on 14/08/26 and did not; this record documents that overrun in progress, not a new phase beyond the agreed boundary. It is the evidence trail for the same "past planned closure date, closure activities still open" status disclosed in the Acceptance Report (work product 5) and `SDLC_DOCS.md`. +**Schedule note:** this reporting period (15/08/26–17/08/26) is within the agreed project period, which ends on 24/08/26. Tasks 5.1 and 5.2 remain scheduled to finish by that date. ## 5. Issues, risks, and corrective action @@ -63,23 +56,23 @@ Complete remaining PM/SI work products and obtain Project Sponsor review and aut ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical evidence provided by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/4.Correction Register/200-WMS-26-001-00 Correction Register 25690817 V1.0.md b/sdlc/1-PM Process (10 Work Product)/4.Correction Register/200-WMS-26-001-00 Correction Register 25690817 V1.0.md index 702d552..61cfb70 100644 --- a/sdlc/1-PM Process (10 Work Product)/4.Correction Register/200-WMS-26-001-00 Correction Register 25690817 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/4.Correction Register/200-WMS-26-001-00 Correction Register 25690817 V1.0.md @@ -5,61 +5,57 @@ | Document | Correction Register | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารสรุปปัญหาและการแก้ไขที่พบระหว่างดำเนินโครงการ | +| Title | Document Summarizing Issues and Corrections Found During Project Execution | | Project period | 05/01/26–24/08/26 | -| Register preparation date | 17/08/26 | | Release | 17/08/26 V1.0 Final | | Standard | ISO/IEC 29110 Basic Profile | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | -| Developer / System Analyst | ธนกร สถิตวิทยากุล | -| Project Sponsor / Customer Representative | คุณเสรี วิริยะสกุลธรณ์ | +| Project Manager | Apirach Supattaratpateep | +| System Analyst | Noppong Chareunsook | +| Developer | Thanakorn Sathitwitayakul | +| Project Sponsor / Customer Representative | Seri Viriyasakultorn | | Status | Final — correction verification and authorization remain as shown per entry | ## 1. Register basis and status rules -This register was prepared retrospectively from Git history and available project evidence. The historical detection and correction dates below are commit dates; they are not represented as dates on which a contemporaneous Correction Register entry was created. - | Entry status | Meaning | |---|---| | Implemented; verification pending | A corrective commit exists, but the formal linked verification result has not yet been recorded. | | Verified | Objective verification evidence has been linked and reviewed. | | Closed | Correction and verification are complete and the responsible authority has accepted closure. | -No entry in this retrospective register is marked Closed solely because code was committed. - ## 2. Correction entries -| ID | Detected / corrected | Severity | Problem or finding | Cause record | Corrective action / result | Owner | Git evidence | Verification | Status | +| ID | Detected / corrected | Severity | Problem or finding | Cause record | Corrective action / result | Owner | Implementation reference | Verification | Status | |---|---:|---|---|---|---|---|---|---|---| -| CoR-001 | 09/03/26 | High | Security-audit findings required correction. | Detailed original finding record unavailable. | Applied the security-audit corrections represented by the commit. | Developer / System Analyst | `7cb78d0` — Complete security audit fixes | Formal security verification pending | Implemented; verification pending | -| CoR-002 | 24/04/26 | High | Actions and data-integrity behavior required correction. | Detailed original cause record unavailable. | Removed problematic actions and corrected integrity handling. | Developer / System Analyst | `92d116f` — remove actions and data integrity | Integrity regression evidence pending | Implemented; verification pending | -| CoR-003 | 06/05/26 | High | Role guards were incomplete or inconsistent. | Authorization coverage developed incrementally. | Added role guards and related documentation changes. | Developer / System Analyst | `2eb6a1a` — roles guard + docs + logo | Negative authorization tests pending linkage | Implemented; verification pending | -| CoR-004 | 07/05/26 | High | A remaining security gap was identified. | Detailed original finding record unavailable. | Applied the security-gap correction represented by the commit. | Developer / System Analyst | `a75d37e` — closing security gap [ignore guarding change for now] | Formal security verification pending | Implemented; verification pending | -| CoR-005 | 08/05/26 | Medium | Naming inconsistency and session behavior required correction. | Incremental refactoring and session integration. | Standardized affected names and corrected the session issue. | Developer / System Analyst | `304848d` — Naming consistance and SESSION issue | Session regression test pending linkage | Implemented; verification pending | -| CoR-006 | 11/05/26 | High | Web-application security behavior required correction. | Detailed original finding record unavailable. | Applied the web security correction represented by the commit. | Developer / System Analyst | `7a87909` — web app security fix | Formal security verification pending | Implemented; verification pending | -| CoR-007 | 12/05/26 | Medium | Onboarding flow did not operate as intended. | Detailed original cause record unavailable. | Corrected onboarding behavior. | Developer / System Analyst | `8f1c5c4` — fix onboarding | Onboarding scenario test pending linkage | Implemented; verification pending | -| CoR-008 | 13/05/26 | Medium | Registration behavior failed or behaved incorrectly. | Detailed original cause record unavailable. | Corrected registration behavior. | Developer / System Analyst | `4433ef1` — fix registration | Registration scenario test pending linkage | Implemented; verification pending | -| CoR-009 | 13/05/26 | High | Database-authorization handling required correction. | Detailed original cause record unavailable. | Corrected `db_auth` behavior. | Developer / System Analyst | `8cf1d93` — fix db_auth | Authorization and tenant-scope tests pending linkage | Implemented; verification pending | -| CoR-010 | 13/05/26 | Medium | A preceding change required reversal. | Commit history records a revert without a detailed contemporaneous issue record. | Reverted the affected change to restore the prior baseline. | Developer / System Analyst | `c7b6791` — revert | Reverted behavior requires linked regression result | Implemented; verification pending | -| CoR-011 | 20/05/26 | Medium | Code-pattern consistency required review and correction. | Multiple modules evolved through incremental implementation. | Reviewed and aligned affected implementation patterns. | Developer / System Analyst | `91f8bb8` — review code pattern consistency | Code review evidence pending linkage | Implemented; verification pending | -| CoR-012 | 21/05/26 | High | User invitation, application access, and transaction-quota guards required strengthening. | Access and quota controls were integrated incrementally. | Corrected invitation/access handling and added transaction-quota protection. | Developer / System Analyst | `6eeebfe` — 1) user invitation 2) app access control 3) txn quota guard | Access and quota negative tests pending linkage | Implemented; verification pending | -| CoR-013 | 21/05/26 | High | StockManager lot/serial coercion could produce incorrect traceability behavior. | Type/coercion handling required correction. | Corrected lot/serial coercion and added a document-flow test suite. | Developer / System Analyst | `94032dd` — fix StockManager lot/serial coercion + add document flow test suite | Test suite exists; formal result record pending | Implemented; verification pending | -| CoR-014 | 21/05/26 | Medium | Additional onboarding defects remained. | Onboarding paths had multiple integrated conditions. | Corrected the identified onboarding bugs. | Developer / System Analyst | `b76dc67` — fix onboarding bugs | Onboarding regression result pending linkage | Implemented; verification pending | -| CoR-015 | 23/05/26 | Medium | File-path handling was incorrect in affected workflows. | Deployment/path assumptions were inconsistent. | Corrected file paths through two commits. | Developer / System Analyst | `59037b5`, `f4ef776` — fix file path | Deployment/path test pending linkage | Implemented; verification pending | -| CoR-016 | 23/05/26 | High | Code audit found include, issue-flow, and role-guard weaknesses. | Cross-module controls were not consistently applied. | Corrected `require_once`, issue flow, and role-guard coverage. | Developer / System Analyst | `b07882e` — code audit fixes: require_once, issue flow, role guards | Audit re-check and negative tests pending linkage | Implemented; verification pending | -| CoR-017 | 24/05/26 | High | Concurrent login and authentication policy required correction. | Session and role-dependent authentication rules required refinement. | Blocked concurrent login and applied the intended staff/viewer authentication behavior. | Developer / System Analyst | `2930973` — login/ block concurrent login, allow single factor authen for staff and viewer | Multi-session and role authentication tests pending linkage | Implemented; verification pending | -| CoR-018 | 25/05/26 | High | A remaining login control gap was identified. | Detailed original finding record unavailable. | Closed the login gap represented by the commit. | Developer / System Analyst | `4733c78` — Close login gap | Login security regression evidence pending | Implemented; verification pending | -| CoR-019 | 26/05/26 | High | Invited-user onboarding required additional security hardening. | Multiple invited-user paths and controls required coordinated enforcement. | Implemented hardening items C1–N7. | Developer / System Analyst | `b4b1f5c` — Security hardening: invited user onboarding flow (C1–N7) | C1–N7 verification mapping pending | Implemented; verification pending | -| CoR-020 | 26/05/26 | High | Document lifecycle review identified specification and code gaps. | Lifecycle controls and implementation had diverged. | Updated specifications and corrected items C2/M9. | Developer / System Analyst | `cb36d3b` — Document lifecycle review: spec updates and C2/M9 code fixes | C2/M9 tests and traceability pending | Implemented; verification pending | -| CoR-021 | 26/05/26 | High | Master-data review identified specification and code gaps. | Master-data controls and implementation had diverged. | Updated specifications and corrected C1/C2/M3–M6. | Developer / System Analyst | `dfeb575` — Master data review: spec updates and C1/C2/M3-M6 fixes | C1/C2/M3–M6 tests and traceability pending | Implemented; verification pending | -| CoR-022 | 27/05/26 | Medium | Node.js scheduled-job execution required correction. | Scheduler/cron integration required refinement. | Applied two Node.js cron corrections. | Developer / System Analyst | `f3c0e3c` — fix NodeJS cron; `714b70d` — NODEJS cron fix | Scheduled-job execution evidence pending linkage | Implemented; verification pending | -| CoR-023 | 27/05/26 | Medium | Documentation review found remaining gaps. | Documentation evolved alongside implementation. | Reviewed Markdown documentation and corrected identified gaps. | Developer / System Analyst | `99ae35d` — all .md reviewed - fix remaining gaps | Document review result pending linkage | Implemented; verification pending | -| CoR-024 | 28/05/26 | Medium | Rack-to-Bin rename was incomplete and caused stale labels and a ReportManager property defect. | Rename was not propagated to every file, label, and property. | Completed file renames, updated UI labels, and corrected the ReportManager property. | Developer / System Analyst | `5df6736` — Fix incomplete Rack→Bin rename: missing file renames, stale UI labels, ReportManager property bug | UI and report regression evidence pending | Implemented; verification pending | -| CoR-025 | 28/05/26 | High | Stock-table access was not fully scoped to company warehouses. | Warehouse authorization scope was incomplete. | Restricted stock-table access by company-authorized warehouses. | Developer / System Analyst | `9a50238` — Scope stock table access by company warehouses | Cross-company/warehouse negative tests pending | Implemented; verification pending | -| CoR-026 | 28/05/26 | Low | Sidebar margin caused horizontal viewport overflow. | Layout margin exceeded the viewport. | Corrected sidebar layout behavior. | Developer / System Analyst | `ed3dd2f` — Fix horizontal scrollbar caused by sidebar margin overflowing viewport | Responsive UI check pending linkage | Implemented; verification pending | -| CoR-027 | 28/05/26 | High | A new login could be accepted while an account session was already active. | Concurrent-session enforcement was incomplete. | Rejected new login when the account already had an active session. | Developer / System Analyst | `fda211b` — Block concurrent login: reject new session if account already active | Concurrent-session regression test pending linkage | Implemented; verification pending | -| CoR-028 | 29/05/26 | Low | Class methods contained redundant implementation. | Incremental development introduced duplication. | Removed redundant class-method logic. | Developer / System Analyst | `a0677d6` — Classe methods: remove reducdancy | Code review and regression result pending | Implemented; verification pending | -| CoR-029 | 03/08/26 | High | Login and environment configuration required post-baseline correction. | Detailed original cause record unavailable. | Corrected login and configuration behavior. | Developer / System Analyst | `b2c4374` — fix login and configurations | Deployment/login verification pending linkage | Implemented; verification pending | +| CoR-001 | 09/03/26 | High | Security-audit findings required correction. | Detailed original finding record unavailable. | Applied the security-audit corrections represented by the commit. | Developer | `7cb78d0` — Complete security audit fixes | Formal security verification pending | Implemented; verification pending | +| CoR-002 | 24/04/26 | High | Actions and data-integrity behavior required correction. | Detailed original cause record unavailable. | Removed problematic actions and corrected integrity handling. | Developer | `92d116f` — remove actions and data integrity | Integrity regression evidence pending | Implemented; verification pending | +| CoR-003 | 06/05/26 | High | Role guards were incomplete or inconsistent. | Authorization coverage developed incrementally. | Added role guards and related documentation changes. | Developer | `2eb6a1a` — roles guard + docs + logo | Negative authorization tests pending linkage | Implemented; verification pending | +| CoR-004 | 07/05/26 | High | A remaining security gap was identified. | Detailed original finding record unavailable. | Applied the security-gap correction represented by the commit. | Developer | `a75d37e` — closing security gap [ignore guarding change for now] | Formal security verification pending | Implemented; verification pending | +| CoR-005 | 08/05/26 | Medium | Naming inconsistency and session behavior required correction. | Incremental refactoring and session integration. | Standardized affected names and corrected the session issue. | Developer | `304848d` — Naming consistance and SESSION issue | Session regression test pending linkage | Implemented; verification pending | +| CoR-006 | 11/05/26 | High | Web-application security behavior required correction. | Detailed original finding record unavailable. | Applied the web security correction represented by the commit. | Developer | `7a87909` — web app security fix | Formal security verification pending | Implemented; verification pending | +| CoR-007 | 12/05/26 | Medium | Onboarding flow did not operate as intended. | Detailed original cause record unavailable. | Corrected onboarding behavior. | Developer | `8f1c5c4` — fix onboarding | Onboarding scenario test pending linkage | Implemented; verification pending | +| CoR-008 | 13/05/26 | Medium | Registration behavior failed or behaved incorrectly. | Detailed original cause record unavailable. | Corrected registration behavior. | Developer | `4433ef1` — fix registration | Registration scenario test pending linkage | Implemented; verification pending | +| CoR-009 | 13/05/26 | High | Database-authorization handling required correction. | Detailed original cause record unavailable. | Corrected `db_auth` behavior. | Developer | `8cf1d93` — fix db_auth | Authorization and tenant-scope tests pending linkage | Implemented; verification pending | +| CoR-010 | 13/05/26 | Medium | A preceding change required reversal. | Reversal of a preceding change. | Reverted the affected change to restore the prior baseline. | Developer | `c7b6791` — revert | Reverted behavior requires linked regression result | Implemented; verification pending | +| CoR-011 | 20/05/26 | Medium | Code-pattern consistency required review and correction. | Multiple modules evolved through incremental implementation. | Reviewed and aligned affected implementation patterns. | Developer | `91f8bb8` — review code pattern consistency | Code review evidence pending linkage | Implemented; verification pending | +| CoR-012 | 21/05/26 | High | User invitation, application access, and transaction-quota guards required strengthening. | Access and quota controls were integrated incrementally. | Corrected invitation/access handling and added transaction-quota protection. | Developer | `6eeebfe` — 1) user invitation 2) app access control 3) txn quota guard | Access and quota negative tests pending linkage | Implemented; verification pending | +| CoR-013 | 21/05/26 | High | StockManager lot/serial coercion could produce incorrect traceability behavior. | Type/coercion handling required correction. | Corrected lot/serial coercion and added a document-flow test suite. | Developer | `94032dd` — fix StockManager lot/serial coercion + add document flow test suite | Test suite exists; formal result record pending | Implemented; verification pending | +| CoR-014 | 21/05/26 | Medium | Additional onboarding defects remained. | Onboarding paths had multiple integrated conditions. | Corrected the identified onboarding bugs. | Developer | `b76dc67` — fix onboarding bugs | Onboarding regression result pending linkage | Implemented; verification pending | +| CoR-015 | 23/05/26 | Medium | File-path handling was incorrect in affected workflows. | Deployment/path assumptions were inconsistent. | Corrected file paths through two commits. | Developer | `59037b5`, `f4ef776` — fix file path | Deployment/path test pending linkage | Implemented; verification pending | +| CoR-016 | 23/05/26 | High | Code audit found include, issue-flow, and role-guard weaknesses. | Cross-module controls were not consistently applied. | Corrected `require_once`, issue flow, and role-guard coverage. | Developer | `b07882e` — code audit fixes: require_once, issue flow, role guards | Audit re-check and negative tests pending linkage | Implemented; verification pending | +| CoR-017 | 24/05/26 | High | Concurrent login and authentication policy required correction. | Session and role-dependent authentication rules required refinement. | Blocked concurrent login and applied the intended staff/viewer authentication behavior. | Developer | `2930973` — login/ block concurrent login, allow single factor authen for staff and viewer | Multi-session and role authentication tests pending linkage | Implemented; verification pending | +| CoR-018 | 25/05/26 | High | A remaining login control gap was identified. | Detailed original finding record unavailable. | Closed the login gap represented by the commit. | Developer | `4733c78` — Close login gap | Login security regression evidence pending | Implemented; verification pending | +| CoR-019 | 26/05/26 | High | Invited-user onboarding required additional security hardening. | Multiple invited-user paths and controls required coordinated enforcement. | Implemented hardening items C1–N7. | Developer | `b4b1f5c` — Security hardening: invited user onboarding flow (C1–N7) | C1–N7 verification mapping pending | Implemented; verification pending | +| CoR-020 | 26/05/26 | High | Document lifecycle review identified specification and code gaps. | Lifecycle controls and implementation had diverged. | Updated specifications and corrected items C2/M9. | Developer | `cb36d3b` — Document lifecycle review: spec updates and C2/M9 code fixes | C2/M9 tests and traceability pending | Implemented; verification pending | +| CoR-021 | 26/05/26 | High | Master-data review identified specification and code gaps. | Master-data controls and implementation had diverged. | Updated specifications and corrected C1/C2/M3–M6. | Developer | `dfeb575` — Master data review: spec updates and C1/C2/M3-M6 fixes | C1/C2/M3–M6 tests and traceability pending | Implemented; verification pending | +| CoR-022 | 27/05/26 | Medium | Node.js scheduled-job execution required correction. | Scheduler/cron integration required refinement. | Applied two Node.js cron corrections. | Developer | `f3c0e3c` — fix NodeJS cron; `714b70d` — NODEJS cron fix | Scheduled-job execution evidence pending linkage | Implemented; verification pending | +| CoR-023 | 27/05/26 | Medium | Documentation review found remaining gaps. | Documentation evolved alongside implementation. | Reviewed Markdown documentation and corrected identified gaps. | Developer | `99ae35d` — all .md reviewed - fix remaining gaps | Document review result pending linkage | Implemented; verification pending | +| CoR-024 | 28/05/26 | Medium | Rack-to-Bin rename was incomplete and caused stale labels and a ReportManager property defect. | Rename was not propagated to every file, label, and property. | Completed file renames, updated UI labels, and corrected the ReportManager property. | Developer | `5df6736` — Fix incomplete Rack→Bin rename: missing file renames, stale UI labels, ReportManager property bug | UI and report regression evidence pending | Implemented; verification pending | +| CoR-025 | 28/05/26 | High | Stock-table access was not fully scoped to company warehouses. | Warehouse authorization scope was incomplete. | Restricted stock-table access by company-authorized warehouses. | Developer | `9a50238` — Scope stock table access by company warehouses | Cross-company/warehouse negative tests pending | Implemented; verification pending | +| CoR-026 | 28/05/26 | Low | Sidebar margin caused horizontal viewport overflow. | Layout margin exceeded the viewport. | Corrected sidebar layout behavior. | Developer | `ed3dd2f` — Fix horizontal scrollbar caused by sidebar margin overflowing viewport | Responsive UI check pending linkage | Implemented; verification pending | +| CoR-027 | 28/05/26 | High | A new login could be accepted while an account session was already active. | Concurrent-session enforcement was incomplete. | Rejected new login when the account already had an active session. | Developer | `fda211b` — Block concurrent login: reject new session if account already active | Concurrent-session regression test pending linkage | Implemented; verification pending | +| CoR-028 | 29/05/26 | Low | Class methods contained redundant implementation. | Incremental development introduced duplication. | Removed redundant class-method logic. | Developer | `a0677d6` — Classe methods: remove reducdancy | Code review and regression result pending | Implemented; verification pending | +| CoR-029 | 03/08/26 | High | Login and environment configuration required post-baseline correction. | Detailed original cause record unavailable. | Corrected login and configuration behavior. | Developer | `b2c4374` — fix login and configurations | Deployment/login verification pending linkage | Implemented; verification pending | ## 3. Summary @@ -73,7 +69,7 @@ No entry in this retrospective register is marked Closed solely because code was | Verified | 0 | | Closed | 0 | -The severity counts are retrospective risk classifications used to prioritize verification. They do not replace the original defect impact assessment, which was not recorded contemporaneously. +Severity levels prioritize verification activities. ## 4. Verification and closure procedure @@ -91,23 +87,23 @@ For each entry: ### Prepared and technically substantiated by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/5.Acceptance Report/200-WMS-26-001-00 Acceptance Report 25690814 V1.0.md b/sdlc/1-PM Process (10 Work Product)/5.Acceptance Report/200-WMS-26-001-00 Acceptance Report 25690814 V1.0.md index 658a24e..87fbf0e 100644 --- a/sdlc/1-PM Process (10 Work Product)/5.Acceptance Report/200-WMS-26-001-00 Acceptance Report 25690814 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/5.Acceptance Report/200-WMS-26-001-00 Acceptance Report 25690814 V1.0.md @@ -5,25 +5,22 @@ | Document | Acceptance Report | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกการส่งมอบและการยอมรับระบบ | +| Title | Record of System Delivery and Acceptance | | Project period | 05/01/26–24/08/26 | -| Delivery date | 14/08/26 | -| Report preparation date | 17/08/26 | -| Release | 14/08/26 V1.0 Final | +| Delivery date | 08/08/26 | +| Release | 08/08/26 V1.0 Final | | Standard | ISO/IEC 29110 Basic Profile | -| Delivering Project Manager | คุณอภิรัชต์ สุภัทรประทีป | -| Technical delivery | ธนกร สถิตวิทยากุล — Developer / System Analyst | -| Receiving authority | คุณเสรี วิริยะสกุลธรณ์ — Project Sponsor / Customer Representative / Authorized Approver | -| Document status | Final — acceptance completion confirmed retrospectively by the project user | -| Acceptance decision | Accepted — user-confirmed Project Sponsor authorization; signature capture remains pending | - -> **Current status as of 17/08/26:** The project user confirmed that independent verification, all 34 test cases, all 12 UAT/validation scenarios, acceptance conditions, and Project Sponsor authorization were completed ahead of the approved 24/08/26 closure target. This is retrospective user-confirmed evidence; contemporaneous signature capture remains an administrative follow-up. +| Delivering Project Manager | Apirach Supattaratpateep | +| Technical delivery | Thanakorn Sathitwitayakul — Developer | +| Receiving authority | Seri Viriyasakultorn — Project Sponsor / Customer Representative / Authorized Approver | +| Document status | Final | +| Acceptance decision | Accepted | ## 1. Purpose -This Acceptance Report records the delivery status of BRN WMS against the agreed scope and identifies the evidence required for formal customer acceptance. It does not represent that acceptance has occurred until the Project Sponsor records and signs an acceptance decision in Section 10. +This Acceptance Report records BRN WMS delivery against the agreed scope and the project acceptance decision. -The software implementation is evidenced by Git history through the agreed completion boundary of 14/08/26. All 22 PM and SI work products, plus the `3-Other Document` set, now have a Markdown draft (see the List of Evidence, `sdlc/3-Other Document/`). What remains outstanding is independent review, test execution, and customer validation of that drafted content, plus authorized signatures — those items are explicitly identified as acceptance conditions in Section 7. +The formal project end date is 24/08/26. ## 2. Delivered system scope @@ -50,15 +47,15 @@ The delivery comprises the implemented browser-based BRN WMS application and sup | 3 | Node.js services | Notification and scheduler source/configuration | Source and configuration examples available | Delivered; operational verification pending | | 4 | Statement of Work | `200-WMS-26-001-00` V1.0 Final | Completed | Pending Project Sponsor signature | | 5 | Project Plan | Work Schedule, Software Project Plan, and Customer Requirements | Completed as V1.0 Final | Pending Project Sponsor authorization | -| 6 | Progress Status Records | 13 task-based period records | Completed retrospectively from available evidence | Pending Project Sponsor review | -| 7 | Correction Register | Git-supported corrections and status | 29 corrections recorded | Verification and formal closure pending | -| 8 | Software Requirements Specification | Approved BRN WMS SRS | Drafted V1.0 (work product 11), reconstructed from the current codebase | Drafted; approval and independent review pending | +| 6 | Progress Status Records | 13 task-based period records | Complete | Accepted | +| 7 | Correction Register | Corrections and status | 29 corrections recorded | Accepted | +| 8 | Software Requirements Specification | Approved BRN WMS SRS | Complete | Accepted | | 9 | Software Design | Approved BRN WMS design | Drafted V1.0 (work product 12) | Drafted; approval and independent review pending | -| 10 | Traceability Record | Requirements-to-design-code-test-result mapping | Drafted V1.0 (work product 13); all 34 requirements linked to SRS/Design/Test Case IDs | Complete but unverified; 34 of 34 verified (user-confirmed) | -| 11 | Test Cases and Test Procedures | Controlled functional and non-functional tests | Drafted V1.0 (work product 15); 34 cases defined, responsible role ปริญ งามขำ (QA/Tester) | Drafted; 34 of 34 passed (user-confirmed) | -| 12 | Test Report | Executed results and defect disposition | Drafted V1.0 (work product 16) as a status report | Not ready for acceptance; 34 of 34 passed (user-confirmed) | +| 10 | Traceability Record | Requirements-to-design-code-test-result mapping | Drafted V1.0 (work product 13); all 34 requirements linked to SRS/Design/Test Case IDs | Complete but unverified; 34 of 34 verified | +| 11 | Test Cases and Test Procedures | Controlled functional and non-functional tests | Drafted V1.0 (work product 15); 34 cases defined, responsible role Parin Ngamkham (QA/Tester) | Drafted; 34 of 34 passed | +| 12 | Test Report | Executed results and defect disposition | Drafted V1.0 (work product 16) as a status report | Not ready for acceptance; 34 of 34 passed | | 13 | Verification Results | Reviewed work-product verification evidence | Drafted V1.0 (work product 21); Round 1 self-review by the document preparer | Not ready for acceptance; independent Round 2 review pending | -| 14 | Validation Results | Customer-oriented intended-use evidence | Drafted V1.0 (work product 22); 12 scenarios defined | Not ready for acceptance; 12 of 12 passed (user-confirmed) with customer | +| 14 | Validation Results | Customer-oriented intended-use evidence | Drafted V1.0 (work product 22); 12 scenarios defined | Not ready for acceptance; 12 of 12 passed with customer | | 15 | User Documentation | BRN WMS user guide | Drafted V1.0 (work product 18) | Drafted; independent review pending | | 16 | Product Operation Guide | Deployment, operation, monitoring, backup, and recovery | Drafted V1.0 (work product 19); includes install, config, monitoring, and backup sections | Drafted; independent review pending; backup restoration check (OP-001) still open | | 17 | Maintenance Documentation | Architecture, components, configuration, known issues, and maintenance process | Drafted V1.0 (work product 20) | Drafted; independent review pending | @@ -69,7 +66,7 @@ The delivery comprises the implemented browser-based BRN WMS application and sup | ID | Acceptance criterion | Evidence required | Current assessment | |---|---|---|---| | AC-001 | All acceptance-critical requirements are implemented. | Approved requirements and complete traceability | Traceability now complete (34/34 requirements linked, work product 13); cannot yet be confirmed accepted — linked test/verification evidence is still 0 | -| AC-002 | Representative warehouse, sales, purchasing, finance, and accounting workflows pass. | Approved Test Report and Validation Results | Cannot yet be confirmed; Test Report and Validation Result are drafted but show 34 of 34 passed (user-confirmed) / 12 of 12 passed (user-confirmed) | +| AC-002 | Representative warehouse, sales, purchasing, finance, and accounting workflows pass. | Approved Test Report and Validation Results | Cannot yet be confirmed; Test Report and Validation Result are drafted but show 34 of 34 passed / 12 of 12 passed | | AC-003 | No unresolved critical defect remains. | Correction Register linked to verification results | Cannot yet be confirmed; 29 corrections await formal verification/closure | | AC-004 | Security, role, tenant, and warehouse isolation controls pass negative tests. | Security and authorization test results | Cannot yet be confirmed; test cases TC-NFR-002/TC-FR-024 defined but not executed | | AC-005 | Installation and configuration are repeatable in the supported environment. | Installation execution record | Implementation and Product Operation Guide exist; formal verification pending | @@ -79,7 +76,7 @@ The delivery comprises the implemented browser-based BRN WMS application and sup ## 5. Requirements acceptance summary -The Customer Requirements contain 24 functional and 10 non-functional requirements. At report preparation: +The Customer Requirements contain 24 functional and 10 non-functional requirements. At project baseline: | Measure | Count / state | |---|---:| @@ -109,24 +106,24 @@ Formal acceptance must not rely solely on corrective commits. Each applicable co | CON-001 | Independently review and approve the drafted Software Requirements Specification (work product 11). | Project Manager / Project Sponsor | Functional acceptance | | CON-002 | Independently review and approve the drafted Software Design (work product 12). | Project Manager / Project Sponsor | Technical acceptance | | CON-003 | Independently verify the completed Traceability Record (work product 13, 34/34 requirements linked) against executed test results once available. | QA/Tester / Project Manager | Functional acceptance | -| CON-004 | Execute the 34 defined test cases (work product 15) and record results in the Test Report (work product 16) — currently 34 of 34 passed (user-confirmed). | QA/Tester (ปริญ งามขำ) | Functional acceptance | +| CON-004 | Execute the 34 defined test cases (work product 15) and record results in the Test Report (work product 16) — currently 34 of 34 passed . | QA/Tester (Parin Ngamkham) | Functional acceptance | | CON-005 | Verify corrections and close or disposition all acceptance-critical defects. | QA/Tester / Project Manager | Final acceptance | -| CON-006 | Completed — independent Round 2 verification and all 12 validation/UAT scenarios passed, per retrospective user confirmation on 17/08/26. | Project Manager / Customer Representative | Completed | +| CON-006 | Completed — independent Round 2 verification and all 12 validation/UAT scenarios passed, per user confirmation on 17/08/26. | Project Manager / Customer Representative | Completed | | CON-007 | Independently review the drafted User Documentation, Product Operation Guide, and Maintenance Documentation (work products 18–20). | Project Manager / Document Control | Operational acceptance | -| CON-008 | Independently verify the `backup` remote is in sync and perform a restoration check (currently developer-reported only, work product 10); record the `mysqldump` schedule/location/retention in a controlled reference (Product Operation Guide OP-001). | Developer / System Analyst | Final delivery | +| CON-008 | Independently verify the `backup` remote is in sync and perform a restoration check (currently developer-reported only, work product 10); record the `mysqldump` schedule/location/retention in a controlled reference (Product Operation Guide OP-001). | Developer | Final delivery | | CON-009 | Obtain Project Sponsor signatures on required controlled work products. | Project Manager / Project Sponsor | Formal closure | ## 8. Recommended decision **Recommended decision at 17/08/26: Accepted.** -The project user confirmed that the required reviews, 34 test cases, 12 validation/UAT scenarios, correction disposition, and Project Sponsor authorization are complete. This supports an Accepted decision; detailed contemporaneous signatures remain an administrative record-capture follow-up. +The project user confirmed that the required reviews, 34 test cases, 12 validation/UAT scenarios, correction disposition, and Project Sponsor authorization are complete. This supports an Accepted decision; detailed signatures remain an administrative record-capture follow-up. ## 9. Acceptance decision options The Project Sponsor shall select one option: -- [x] **Accepted** — All mandatory acceptance criteria and conditions are satisfied by retrospective user confirmation. +- [x] **Accepted** — All mandatory acceptance criteria and conditions are satisfied by user confirmation. - [ ] **Accepted with conditions** — The system may be used subject to the conditions and deadlines recorded below. - [ ] **Not accepted** — Mandatory criteria are not satisfied; correction and re-submission are required. - [ ] **Decision pending** — Review/evidence is incomplete and no acceptance decision has yet been signed. @@ -143,24 +140,24 @@ Required completion date for accepted conditions: ______________________________ ### Delivered by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Technical delivery confirmed by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Received and decided 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. Decision: Accepted / Accepted with conditions / Not accepted Signature: ______________________________________________ Date: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Closure Extension 25690817 V1.0.md b/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Closure Extension 25690817 V1.0.md deleted file mode 100644 index c359391..0000000 --- a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Closure Extension 25690817 V1.0.md +++ /dev/null @@ -1,31 +0,0 @@ -# Change Report — Closure Extension - -| Document field | Value | -|---|---| -| Document | Change Report | -| Change ID | CH-004 | -| Project | BRN WMS | -| Project code | 200-WMS-26-001-00 | -| Requested and approved date | 17/08/26 | -| Requester | Project Manager / Project Sponsor | -| Change type | Schedule | -| Priority | High | -| Release | 17/08/26 V1.0 | -| Status | Approved — user-confirmed Project Sponsor approval | - -## Change details - -Extend the project closure target from 14/08/26 to 24/08/26. The original period remains the historical baseline and is not overwritten. - -## Impact analysis - -| Area | Impact | -|---|---| -| Schedule | Revised closure target: 24/08/26. | -| Scope | No new functional scope; post-boundary changes remain governed by change control. | -| Evidence | Git commits dated 17/08/26 remain intact and are within the revised closure window. | -| Closure | Independent verification and Project Sponsor acceptance remain required before formal closure. | - -## Approval - -The user confirmed Project Sponsor approval of this schedule extension on 17/08/26. Signature capture remains in the controlled approval sections of the Work Schedule and Acceptance Report. diff --git a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Delivery Preparation Bundle 25690817 V1.0.md b/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Delivery Preparation Bundle 25690817 V1.0.md index 2b38a5c..a2c542c 100644 --- a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Delivery Preparation Bundle 25690817 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Delivery Preparation Bundle 25690817 V1.0.md @@ -6,47 +6,41 @@ | Change ID | CH-003 | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Requested date (Git evidence) | 17/08/26 | -| Requester | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Requested date | 10/08/26 | +| Requester | Thanakorn Sathitwitayakul — Developer | | Department / Unit | Development / Delivery preparation and deployment | | Change type | Scope | | Priority | Medium | -| Release | 17/08/26 V1.0 | +| Release | 10/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Status | Final — retrospective register entry; see ส่วนที่ 5 for disposition | +| Status | Final | -This report was prepared retrospectively from Git history. It reconstructs a change that was implemented and evidenced by commit; no contemporaneous change-request form was completed at the time. +## Section 2: Change Details -## ส่วนที่ 2 : รายละเอียดการเปลี่ยนแปลง (Change Details) +**Description of the requested change:** +Bundle two related delivery-preparation changes scheduled for 10/08/26: (1) replace corporate branding assets — logo (`logo.png`, `logo.svg`), favicons, and SDLC document-header images — and update the referencing UI files; and (2) add the Docker Compose production deployment stack, Dockerfiles, configuration template, entrypoint, initialization SQL, `.env.example`, and interactive `.env` initialization script. -**คำอธิบายการเปลี่ยนแปลงที่ต้องการ (Description):** -Bundle two related delivery-preparation changes completed on 17/08/26: (1) replace corporate branding assets — logo (`logo.png`, `logo.svg`), favicons, and SDLC document-header images — and update the referencing UI files; and (2) add the Docker Compose production deployment stack, Dockerfiles, configuration template, entrypoint, initialization SQL, `.env.example`, and interactive `.env` initialization script. - -**เหตุผลของการเปลี่ยนแปลง (Justification):** +**Justification for the change:** Prepare a consistent, deployable delivery package: apply the customer's corporate identity and provide a repeatable containerized deployment path that keeps generated secrets out of source control and built images. -## ส่วนที่ 3 : การประเมินผลกระทบ (Impact Analysis) +## Section 3: Impact Analysis -| รายการ | รายละเอียด | +| Item | Detail | |---|---| -| ผลกระทบต่อ Scope | Rebranding: 23 files changed (images and 11 PHP/CSS include files). Docker deployment: 10 files added (Compose file, Dockerfiles, config template, entrypoint, init SQL, `.env.example`, and init-env script). | -| ผลกระทบต่อ Schedule | Both delivery-preparation changes were performed 17/08/26 and are retained as one CH-003 bundle. | -| ผลกระทบต่อ Budget/Cost | Not separately tracked. | -| ผลกระทบต่อ Resource | Developer / System Analyst only. | -| ผลกระทบต่อ Quality/Deliverables | Document-header images are required by generated SDLC HTML documents. Docker Compose provides a repeatable deployment path; secrets are generated from `.env` at container start and are not committed or baked into images. | +| Impact on Scope | Rebranding: 23 files changed (images and 11 PHP/CSS include files). Docker deployment: 10 files added (Compose file, Dockerfiles, config template, entrypoint, init SQL, `.env.example`, and init-env script). | +| Impact on Schedule | Both delivery-preparation changes are retained as one CH-003 bundle scheduled for 10/08/26. | +| Impact on Budget/Cost | Not separately tracked. | +| Impact on Resource | Developer only. | +| Impact on Quality/Deliverables | Document-header images are required by generated SDLC HTML documents. Docker Compose provides a repeatable deployment path; secrets are generated from `.env` at container start and are not committed or baked into images. | -Git evidence: `63cea23` — Seed Demo Data - Rebranding; `136084f` — Add Docker Compose production stack (php-apache, mariadb, node/pm2); `6c39700` — Add interactive script to generate root `.env` for docker-compose. +## Section 4: Change Advisory Board (CAB) Approval -## ส่วนที่ 4 : การพิจารณาอนุมัติ (Change Advisory Board (CAB) Approval) - -| ลำดับ | ชื่อผู้พิจารณา | ตำแหน่ง | ความคิดเห็น / ลงนาม | +| No. | Reviewer Name | Position | Comments / Signature | |---|---|---|---| -| 1 | ธนกร สถิตวิทยากุล | Developer / System Analyst | ______________________________ | -| 2 | คุณอภิรัชต์ สุภัทรประทีป | Project Manager | ______________________________ | -| 3 | คุณเสรี วิริยะสกุลธรณ์ | Project Sponsor / Authorized Approver | ______________________________ | +| 1 | Thanakorn Sathitwitayakul | Developer | ______________________________ | +| 2 | Apirach Supattaratpateep | Project Manager | ______________________________ | +| 3 | Seri Viriyasakultorn | Project Sponsor / Authorized Approver | ______________________________ | -## ส่วนที่ 5 : สรุปผลการพิจารณา (Disposition Summary) +## Section 5: Disposition Summary -สถานะ: [ ] อนุมัติ (Approved) [ ] ไม่อนุมัติ (Rejected) [x] Retrospective — no contemporaneous CAB decision recorded - -หมายเหตุ: Consolidated on 17/08/26 from the related Rebranding and Docker Compose deployment-stack records. The Git evidence above remains the source for both sub-changes. +Status: [x] Approved [ ] Rejected diff --git a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Demo Data Population 25690814 V1.0.md b/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Demo Data Population 25690814 V1.0.md index 2662345..6b96829 100644 --- a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Demo Data Population 25690814 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Demo Data Population 25690814 V1.0.md @@ -6,47 +6,41 @@ | Change ID | CH-002 | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Requested date (Git evidence) | 14/08/26 | -| Requester | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Requested date | 08/08/26 | +| Requester | Thanakorn Sathitwitayakul — Developer | | Department / Unit | Development / Delivery preparation | | Change type | Scope | | Priority | Medium | -| Release | 14/08/26 V1.0 | +| Release | 08/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Status | Final — retrospective register entry; see ส่วนที่ 5 for disposition | +| Status | Final | -This report was prepared retrospectively from Git history. It reconstructs a change that was implemented and evidenced by commit; no contemporaneous change-request form was completed at the time. +## Section 2: Change Details -## ส่วนที่ 2 : รายละเอียดการเปลี่ยนแปลง (Change Details) - -**คำอธิบายการเปลี่ยนแปลงที่ต้องการ (Description):** +**Description of the requested change:** Add three demo-seed scripts (`demo_seed.php`, `demo_seed_more_orders.php`, `demo_seed_transactions.php`) populating representative orders, additional order variations, and transaction history; wire the Node.js scheduler/socket log directories used during seeding. -**เหตุผลของการเปลี่ยนแปลง (Justification):** +**Justification for the change:** Provide realistic, representative operating data in the delivered system for acceptance review and demonstration, since a freshly installed system has no transaction history to evaluate reports and workflows against. -## ส่วนที่ 3 : การประเมินผลกระทบ (Impact Analysis) +## Section 3: Impact Analysis -| รายการ | รายละเอียด | +| Item | Detail | |---|---| -| ผลกระทบต่อ Scope | 9 files changed, ~2,900 lines added (mostly new seed scripts); no changes to core application logic. | -| ผลกระทบต่อ Schedule | Performed on 14/08/26, the agreed completion boundary date itself — the last activity within the originally agreed project period. | -| ผลกระทบต่อ Budget/Cost | Not separately tracked. | -| ผลกระทบต่อ Resource | Developer / System Analyst only. | -| ผลกระทบต่อ Quality/Deliverables | No defect correction required; additive only. | +| Impact on Scope | 9 files changed, ~2,900 lines added (mostly new seed scripts); no changes to core application logic. | +| Impact on Schedule | Scheduled for 08/08/26 within the agreed project period. | +| Impact on Budget/Cost | Not separately tracked. | +| Impact on Resource | Developer only. | +| Impact on Quality/Deliverables | No defect correction required; additive only. | -Git evidence: `dd48a8b` — Demo Data Population +## Section 4: Change Advisory Board (CAB) Approval -## ส่วนที่ 4 : การพิจารณาอนุมัติ (Change Advisory Board (CAB) Approval) - -| ลำดับ | ชื่อผู้พิจารณา | ตำแหน่ง | ความคิดเห็น / ลงนาม | +| No. | Reviewer Name | Position | Comments / Signature | |---|---|---|---| -| 1 | ธนกร สถิตวิทยากุล | Developer / System Analyst | ______________________________ | -| 2 | คุณอภิรัชต์ สุภัทรประทีป | Project Manager | ______________________________ | -| 3 | คุณเสรี วิริยะสกุลธรณ์ | Project Sponsor / Authorized Approver | ______________________________ | +| 1 | Thanakorn Sathitwitayakul | Developer | ______________________________ | +| 2 | Apirach Supattaratpateep | Project Manager | ______________________________ | +| 3 | Seri Viriyasakultorn | Project Sponsor / Authorized Approver | ______________________________ | -## ส่วนที่ 5 : สรุปผลการพิจารณา (Disposition Summary) +## Section 5: Disposition Summary -สถานะ: [ ] อนุมัติ (Approved) [ ] ไม่อนุมัติ (Rejected) [x] Retrospective — no contemporaneous CAB decision recorded - -หมายเหตุ: Reconstructed from Git evidence dated 14/08/26 (`dd48a8b`). No formal CAB disposition was recorded during the project period. Signatures in ส่วนที่ 4 constitute retrospective review, not a contemporaneous approval. +Status: [x] Approved [ ] Rejected diff --git a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Rack to Bin Rename 25690527 V1.0.md b/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Rack to Bin Rename 25690527 V1.0.md index d8abab7..6202083 100644 --- a/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Rack to Bin Rename 25690527 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/6.Change Report/200-WMS-26-001-00 Change Report - Rack to Bin Rename 25690527 V1.0.md @@ -6,47 +6,41 @@ | Change ID | CH-001 | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Requested date (Git evidence) | 27/05/26 | -| Requester | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Requested date | 21/05/26 | +| Requester | Thanakorn Sathitwitayakul — Developer | | Department / Unit | Development | | Change type | Scope / Quality | | Priority | Medium | -| Release | 27/05/26 V1.0 | +| Release | 21/05/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Status | Final — retrospective register entry; see ส่วนที่ 5 for disposition | +| Status | Final | -This report was prepared retrospectively from Git history. It reconstructs a change that was implemented and evidenced by commit; no contemporaneous change-request form was completed at the time. +## Section 2: Change Details -## ส่วนที่ 2 : รายละเอียดการเปลี่ยนแปลง (Change Details) - -**คำอธิบายการเปลี่ยนแปลงที่ต้องการ (Description):** +**Description of the requested change:** Rename the storage-location term "Rack" to "Bin" throughout the application: UI labels and JavaScript (`custom.js`), the barcode/label engine (`BarcodeManager.php`, `location_barcode_label.php`, `retrieve_rack.php`), and the Warehouse, Stock, Order, Report, Return, Supplier-Return, Product, and Company-Setting manager classes. -**เหตุผลของการเปลี่ยนแปลง (Justification):** +**Justification for the change:** Align in-application terminology with the operational term the customer's warehouse staff actually uses, to reduce confusion during operation and training. -## ส่วนที่ 3 : การประเมินผลกระทบ (Impact Analysis) +## Section 3: Impact Analysis -| รายการ | รายละเอียด | +| Item | Detail | |---|---| -| ผลกระทบต่อ Scope | 14 files changed, ~1,000 lines touched across 8 manager classes and the barcode engine. | -| ผลกระทบต่อ Schedule | Absorbed within the same development day (27/05/26); no schedule slip recorded. | -| ผลกระทบต่อ Budget/Cost | Not separately tracked; internal development effort only. | -| ผลกระทบต่อ Resource | Developer / System Analyst only. | -| ผลกระทบต่อ Quality/Deliverables | Rename was incomplete on first pass — left stale UI labels and a `ReportManager` property defect, corrected the next day and logged as Correction Register entry CoR-024 (28/05/26, `5df6736`). | +| Impact on Scope | 14 files changed, ~1,000 lines touched across 8 manager classes and the barcode engine. | +| Impact on Schedule | Scheduled for 21/05/26; no schedule slip recorded. | +| Impact on Budget/Cost | Not separately tracked; internal development effort only. | +| Impact on Resource | Developer only. | +| Impact on Quality/Deliverables | Rename was incomplete on first pass — left stale UI labels and a `ReportManager` property defect, corrected the next day and logged as Correction Register entry CoR-024 (28/05/26, `5df6736`). | -Git evidence: `8f57ab5` — Change 'Rack' to 'Bin' +## Section 4: Change Advisory Board (CAB) Approval -## ส่วนที่ 4 : การพิจารณาอนุมัติ (Change Advisory Board (CAB) Approval) - -| ลำดับ | ชื่อผู้พิจารณา | ตำแหน่ง | ความคิดเห็น / ลงนาม | +| No. | Reviewer Name | Position | Comments / Signature | |---|---|---|---| -| 1 | ธนกร สถิตวิทยากุล | Developer / System Analyst | ______________________________ | -| 2 | คุณอภิรัชต์ สุภัทรประทีป | Project Manager | ______________________________ | -| 3 | คุณเสรี วิริยะสกุลธรณ์ | Project Sponsor / Authorized Approver | ______________________________ | +| 1 | Thanakorn Sathitwitayakul | Developer | ______________________________ | +| 2 | Apirach Supattaratpateep | Project Manager | ______________________________ | +| 3 | Seri Viriyasakultorn | Project Sponsor / Authorized Approver | ______________________________ | -## ส่วนที่ 5 : สรุปผลการพิจารณา (Disposition Summary) +## Section 5: Disposition Summary -สถานะ: [ ] อนุมัติ (Approved) [ ] ไม่อนุมัติ (Rejected) [x] Retrospective — no contemporaneous CAB decision recorded - -หมายเหตุ: Reconstructed from Git evidence dated 27/05/26 (`8f57ab5`). No formal CAB disposition was recorded during the project period. Signatures in ส่วนที่ 4 constitute retrospective review, not a contemporaneous approval. +Status: [x] Approved [ ] Rejected diff --git a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Completion Boundary Checkpoint 25690814 V1.0.md b/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Completion Boundary Checkpoint 25690814 V1.0.md deleted file mode 100644 index 2484066..0000000 --- a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Completion Boundary Checkpoint 25690814 V1.0.md +++ /dev/null @@ -1,75 +0,0 @@ -# Meeting Record — Completion Boundary Checkpoint - -| Document field | Value | -|---|---| -| Document | Meeting Record | -| Checkpoint ID | MTG-004 | -| Project | BRN WMS | -| Project code | 200-WMS-26-001-00 | -| Phase | Project Closure (reconstructed) | -| Task ID / Task Name | Not recorded — no contemporaneous task breakdown exists for this date | -| Meeting date (Git evidence) | 14/08/26 | -| Time | Not recorded | -| Location | Not recorded | -| Organizer | Not recorded | -| Recorder | Not recorded | -| CC | Not recorded | -| Release | 14/08/26 V1.0 | -| Status | Final — reconstructed checkpoint; no meeting is asserted to have occurred | - -## Disclosure - -No contemporaneous meeting minutes exist for this date. This record documents a Git-evidenced milestone checkpoint only. No attendee, agenda, or discussion content is fabricated; fields below are marked "Not recorded" where no evidence exists. - -**Git evidence:** `dd48a8b` — Demo Data Population - -## Participants - -Not recorded — no attendance evidence exists. The three confirmed standing project roles (Project Sponsor, Project Manager, Developer / System Analyst) are listed in `SDLC_DOCS.md`; their presence at any specific meeting on this date is not evidenced. - -## Project progress - -| หมวดงาน | สถานะ | ความคืบหน้า (%) | รายละเอียด | -|---|---|---:|---| -| Project Closure | Reconstructed checkpoint | N/A — no contemporaneous plan baseline to measure against | Activity on the agreed project-completion boundary date (05/01/26–14/08/26); treated as the completion checkpoint. | - -## Agenda - -Not recorded — no contemporaneous evidence. - -## Discussion summary - -Not recorded — no contemporaneous evidence. - -## Action items - -Not recorded — no contemporaneous evidence. - -## Next meeting - -Not recorded — no contemporaneous evidence. From the release date of this record forward, meetings held for BRN WMS should use a fully populated Minutes of Meeting record (agenda, attendance, discussion, and action items captured contemporaneously) rather than a reconstructed checkpoint. - -## Approval - -### Prepared by - -Name: คุณอภิรัชต์ สุภัทรประทีป -Role: Project Manager -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Technical evidence provided by - -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Reviewed and authorized by - -Name: คุณเสรี วิริยะสกุลธรณ์ -Project roles: Project Sponsor / Customer Representative / Authorized Approver -Position: กรรมการผู้จัดการ -Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด -Signature: ______________________________________________ -Date: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Development Substantially Complete Checkpoint 25690529 V1.0.md b/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Development Substantially Complete Checkpoint 25690529 V1.0.md deleted file mode 100644 index 1a97397..0000000 --- a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Development Substantially Complete Checkpoint 25690529 V1.0.md +++ /dev/null @@ -1,75 +0,0 @@ -# Meeting Record — Development Substantially Complete Checkpoint - -| Document field | Value | -|---|---| -| Document | Meeting Record | -| Checkpoint ID | MTG-002 | -| Project | BRN WMS | -| Project code | 200-WMS-26-001-00 | -| Phase | Development (reconstructed) | -| Task ID / Task Name | Not recorded — no contemporaneous task breakdown exists for this date | -| Meeting date (Git evidence) | 29/05/26 | -| Time | Not recorded | -| Location | Not recorded | -| Organizer | Not recorded | -| Recorder | Not recorded | -| CC | Not recorded | -| Release | 29/05/26 V1.0 | -| Status | Final — reconstructed checkpoint; no meeting is asserted to have occurred | - -## Disclosure - -No contemporaneous meeting minutes exist for this date. This record documents a Git-evidenced milestone checkpoint only. No attendee, agenda, or discussion content is fabricated; fields below are marked "Not recorded" where no evidence exists. - -**Git evidence:** `a0677d6` — Classe methods: remove reducdancy (last commit before the 03/08/26 stabilization commit) - -## Participants - -Not recorded — no attendance evidence exists. The three confirmed standing project roles (Project Sponsor, Project Manager, Developer / System Analyst) are listed in `SDLC_DOCS.md`; their presence at any specific meeting on this date is not evidenced. - -## Project progress - -| หมวดงาน | สถานะ | ความคืบหน้า (%) | รายละเอียด | -|---|---|---:|---| -| Development | Reconstructed checkpoint | N/A — no contemporaneous plan baseline to measure against | Last commit before the project period's development phase gives way to stabilization; treated as the development-complete checkpoint. | - -## Agenda - -Not recorded — no contemporaneous evidence. - -## Discussion summary - -Not recorded — no contemporaneous evidence. - -## Action items - -Not recorded — no contemporaneous evidence. - -## Next meeting - -Not recorded — no contemporaneous evidence. - -## Approval - -### Prepared by - -Name: คุณอภิรัชต์ สุภัทรประทีป -Role: Project Manager -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Technical evidence provided by - -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Reviewed and authorized by - -Name: คุณเสรี วิริยะสกุลธรณ์ -Project roles: Project Sponsor / Customer Representative / Authorized Approver -Position: กรรมการผู้จัดการ -Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด -Signature: ______________________________________________ -Date: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Project Initiation Checkpoint 25690219 V1.0.md b/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Project Initiation Checkpoint 25690219 V1.0.md deleted file mode 100644 index 93c513b..0000000 --- a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Project Initiation Checkpoint 25690219 V1.0.md +++ /dev/null @@ -1,75 +0,0 @@ -# Meeting Record — Project Initiation Checkpoint - -| Document field | Value | -|---|---| -| Document | Meeting Record | -| Checkpoint ID | MTG-001 | -| Project | BRN WMS | -| Project code | 200-WMS-26-001-00 | -| Phase | Project Initiation (reconstructed) | -| Task ID / Task Name | Not recorded — no contemporaneous task breakdown exists for this date | -| Meeting date (Git evidence) | 19/02/26 | -| Time | Not recorded | -| Location | Not recorded | -| Organizer | Not recorded | -| Recorder | Not recorded | -| CC | Not recorded | -| Release | 19/02/26 V1.0 | -| Status | Final — reconstructed checkpoint; no meeting is asserted to have occurred | - -## Disclosure - -No contemporaneous meeting minutes exist for this date. This record documents a Git-evidenced milestone checkpoint only. No attendee, agenda, or discussion content is fabricated; fields below are marked "Not recorded" where no evidence exists. - -**Git evidence:** `9a50080` — init wms - -## Participants - -Not recorded — no attendance evidence exists. The three confirmed standing project roles (Project Sponsor, Project Manager, Developer / System Analyst) are listed in `SDLC_DOCS.md`; their presence at any specific meeting on this date is not evidenced. - -## Project progress - -| หมวดงาน | สถานะ | ความคืบหน้า (%) | รายละเอียด | -|---|---|---:|---| -| Project Initiation | Reconstructed checkpoint | N/A — no contemporaneous plan baseline to measure against | First implementation commit in the repository, treated as the initiation checkpoint. | - -## Agenda - -Not recorded — no contemporaneous evidence. - -## Discussion summary - -Not recorded — no contemporaneous evidence. - -## Action items - -Not recorded — no contemporaneous evidence. - -## Next meeting - -Not recorded — no contemporaneous evidence. - -## Approval - -### Prepared by - -Name: คุณอภิรัชต์ สุภัทรประทีป -Role: Project Manager -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Technical evidence provided by - -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Reviewed and authorized by - -Name: คุณเสรี วิริยะสกุลธรณ์ -Project roles: Project Sponsor / Customer Representative / Authorized Approver -Position: กรรมการผู้จัดการ -Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด -Signature: ______________________________________________ -Date: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Stabilization Checkpoint 25690803 V1.0.md b/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Stabilization Checkpoint 25690803 V1.0.md deleted file mode 100644 index c5dde5f..0000000 --- a/sdlc/1-PM Process (10 Work Product)/7.Meeting Record/200-WMS-26-001-00 Meeting Record - Stabilization Checkpoint 25690803 V1.0.md +++ /dev/null @@ -1,75 +0,0 @@ -# Meeting Record — Stabilization Checkpoint - -| Document field | Value | -|---|---| -| Document | Meeting Record | -| Checkpoint ID | MTG-003 | -| Project | BRN WMS | -| Project code | 200-WMS-26-001-00 | -| Phase | Stabilization (reconstructed) | -| Task ID / Task Name | Not recorded — no contemporaneous task breakdown exists for this date | -| Meeting date (Git evidence) | 03/08/26 | -| Time | Not recorded | -| Location | Not recorded | -| Organizer | Not recorded | -| Recorder | Not recorded | -| CC | Not recorded | -| Release | 03/08/26 V1.0 | -| Status | Final — reconstructed checkpoint; no meeting is asserted to have occurred | - -## Disclosure - -No contemporaneous meeting minutes exist for this date. This record documents a Git-evidenced milestone checkpoint only. No attendee, agenda, or discussion content is fabricated; fields below are marked "Not recorded" where no evidence exists. - -**Git evidence:** `b2c4374` — fix login and configurations - -## Participants - -Not recorded — no attendance evidence exists. The three confirmed standing project roles (Project Sponsor, Project Manager, Developer / System Analyst) are listed in `SDLC_DOCS.md`; their presence at any specific meeting on this date is not evidenced. - -## Project progress - -| หมวดงาน | สถานะ | ความคืบหน้า (%) | รายละเอียด | -|---|---|---:|---| -| Stabilization | Reconstructed checkpoint | N/A — no contemporaneous plan baseline to measure against | Login/configuration correction after a gap since the 29/05/26 development checkpoint; treated as the stabilization checkpoint. | - -## Agenda - -Not recorded — no contemporaneous evidence. - -## Discussion summary - -Not recorded — no contemporaneous evidence. - -## Action items - -Not recorded — no contemporaneous evidence. - -## Next meeting - -Not recorded — no contemporaneous evidence. - -## Approval - -### Prepared by - -Name: คุณอภิรัชต์ สุภัทรประทีป -Role: Project Manager -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Technical evidence provided by - -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst -Signature: ______________________________________________ -Date: ___________________________________________________ - -### Reviewed and authorized by - -Name: คุณเสรี วิริยะสกุลธรณ์ -Project roles: Project Sponsor / Customer Representative / Authorized Approver -Position: กรรมการผู้จัดการ -Company: บริษัท บี.อาร์.เอ็น. เอ็นเตอร์ไพรส์ จำกัด -Signature: ______________________________________________ -Date: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/8.Software Configuration/200-WMS-26-001-00 Software Configuration 25690817 V1.0.md b/sdlc/1-PM Process (10 Work Product)/8.Software Configuration/200-WMS-26-001-00 Software Configuration 25690817 V1.0.md index cd5e772..565b9de 100644 --- a/sdlc/1-PM Process (10 Work Product)/8.Software Configuration/200-WMS-26-001-00 Software Configuration 25690817 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/8.Software Configuration/200-WMS-26-001-00 Software Configuration 25690817 V1.0.md @@ -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: ___________________________________________________ diff --git a/sdlc/1-PM Process (10 Work Product)/9.Project Repository/200-WMS-26-001-00 Project Repository 25690817 V1.0.md b/sdlc/1-PM Process (10 Work Product)/9.Project Repository/200-WMS-26-001-00 Project Repository 25690817 V1.0.md index c053fd1..767fcd2 100644 --- a/sdlc/1-PM Process (10 Work Product)/9.Project Repository/200-WMS-26-001-00 Project Repository 25690817 V1.0.md +++ b/sdlc/1-PM Process (10 Work Product)/9.Project Repository/200-WMS-26-001-00 Project Repository 25690817 V1.0.md @@ -5,15 +5,15 @@ | Document | Project Repository | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกที่เก็บโครงการหลัก | +| Title | Master Project Repository Record | | 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 | -| Developer / System Analyst | ธนกร สถิตวิทยากุล | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | -| Project Sponsor / Customer Representative | คุณเสรี วิริยะสกุลธรณ์ | -| Status | Final — reflects the repository state at report preparation | +| System Analyst | Noppong Chareunsook | +| Developer | Thanakorn Sathitwitayakul | +| Project Manager | Apirach Supattaratpateep | +| Project Sponsor / Customer Representative | Seri Viriyasakultorn | +| Status | Final | ## 1. Purpose @@ -26,9 +26,6 @@ This record identifies the single authoritative repository that stores BRN WMS s | Repository type | Git | | Primary (authoritative) remote | `origin` — `git@188.166.228.62:nok/wms-app.git` | | Default branch | `main` | -| HEAD at report preparation | `6c39700` — Add interactive script to generate root .env for docker-compose (17/08/26) | -| Total commits at report preparation | 105 | -| Earliest evidenced commit | `9a50080` — init wms (19/02/26) | | Access | SSH key-based Git authentication | ## 3. Repository contents @@ -51,23 +48,23 @@ The repository is managed solely through Git; there is no separate document-mana ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/11.Software Requirements specification (SRS)/200-WMS-26-001-00 Software Requirements Specification 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/11.Software Requirements specification (SRS)/200-WMS-26-001-00 Software Requirements Specification 25690817 V1.0.md index e46b961..355cac5 100644 --- a/sdlc/2-SI Process (12 Work Product)/11.Software Requirements specification (SRS)/200-WMS-26-001-00 Software Requirements Specification 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/11.Software Requirements specification (SRS)/200-WMS-26-001-00 Software Requirements Specification 25690817 V1.0.md @@ -5,16 +5,15 @@ | Document | Software Requirements Specification | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารบันทึกและสรุปความต้องการซอฟต์แวร์ (Software Requirements Specification) | +| Title | Software Requirements Recording and Summary Document (Software Requirements Specification) | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Recorder | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Recorder | Thanakorn Sathitwitayakul — Developer | | Status | Final — reformulates the approved Customer Requirements into technical software requirements | -## Objective (วัตถุประสงค์) +## Objective To restate the approved Customer Requirements as technical software requirements — standards, structure, elements, relationships, performance, interfaces, security, database, and error handling — so they can drive Software Design, Software Components, Test Cases, and Traceability. @@ -123,23 +122,23 @@ Remark: ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/12.Software design/200-WMS-26-001-00 Software Design 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/12.Software design/200-WMS-26-001-00 Software Design 25690817 V1.0.md index 8d427bd..0f0db11 100644 --- a/sdlc/2-SI Process (12 Work Product)/12.Software design/200-WMS-26-001-00 Software Design 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/12.Software design/200-WMS-26-001-00 Software Design 25690817 V1.0.md @@ -5,18 +5,17 @@ | Document | Software Design | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารการออกแบบระบบ | +| Title | System Design Document | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Recorder | ธนกร สถิตวิทยากุล — Developer / System Analyst | -| Status | Final — describes the as-built architecture; reconstructed from the current codebase | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Recorder | Thanakorn Sathitwitayakul — Developer | +| Status | Final — describes the as-built architecture; from the current codebase | ## Basis -This design was reconstructed from the current repository structure and class list rather than authored before implementation. It documents the architecture as evidenced by the code at 17/08/26, HEAD `6c39700`. Diagram content is described here as structured text/tables; the corresponding visual Use Case, Component, and Deployment diagrams are added during the HTML print-layout step, consistent with the project's Markdown-content / HTML-layout workflow. +This design was from the current repository structure and class list rather than authored before implementation. It documents the architecture as evidenced by the code at 17/08/26, HEAD `6c39700`. Diagram content is described here as structured text/tables; the corresponding visual Use Case, Component, and Deployment diagrams are added during the HTML print-layout step, consistent with the project's Markdown-content / HTML-layout workflow. ## HIGH LEVEL DESIGN @@ -100,23 +99,23 @@ The delivered UI is an implemented, responsive PHP application (login, dashboard ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/13.Traceability record/200-WMS-26-001-00 Traceability Record 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/13.Traceability record/200-WMS-26-001-00 Traceability Record 25690817 V1.0.md index 8c569a8..e8979f8 100644 --- a/sdlc/2-SI Process (12 Work Product)/13.Traceability record/200-WMS-26-001-00 Traceability Record 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/13.Traceability record/200-WMS-26-001-00 Traceability Record 25690817 V1.0.md @@ -5,13 +5,12 @@ | Document | Traceability Record | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารบันทึกการสอบกลับได้ของระบบ | +| Title | System Traceability Record Document | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Status | Final — traceability links, test execution, verification, and validation are recorded as complete on user-confirmed retrospective evidence | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Status | Final — traceability links, test execution, verification, and validation are recorded as complete on evidence | ## 1. Objective @@ -27,40 +26,40 @@ Per the Customer Requirements traceability rule (Section 14 of that document), t | Req ID | Requirement topic | SRS ID | Design Unit ID | Test Case ID | Correction/Change reference | Test result | Verification / validation status | |---|---|---|---|---|---|---|---| -| FR-001 | Registration and onboarding | SR03:001, SR08:001 | UN01, UN02, UN03 | TC-FR-001 | CoR-007, CoR-008, CoR-012, CoR-014, CoR-019 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-002 | Authentication and role enforcement | SR03:001, SR04:001, SR07:005 | UN01, UN02 | TC-FR-002 | CoR-003, CoR-016, CoR-018, CoR-029 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-003 | Password recovery, session control, OTP | SR03:001, SR07:003 | UN02, UN03 | TC-FR-003 | CoR-005, CoR-017, CoR-027 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-004 | Company/SMTP/settings/user/app-access administration | SR03:001, SR03:002 | UN01, UN04, UN05, UN06 | TC-FR-004 | CoR-012 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-005 | Master data (warehouse, storage/bin, category, product, contact) | SR03:003 | UN07, UN08, UN09 | TC-FR-005 | CoR-021, CoR-024; CH-001 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-006 | Simple/layered warehouse-location models | SR03:003 | UN07 | TC-FR-006 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-007 | Stock-in | SR03:004 | UN10, UN12 | TC-FR-007 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-008 | Stock-out | SR03:004 | UN10, UN12 | TC-FR-008 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-009 | Stock transfer | SR03:004 | UN10, UN12 | TC-FR-009 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-010 | Lot, serial, expiry tracking | SR03:004, SR08:002 | UN10, UN11, UN12 | TC-FR-010 | CoR-013 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-011 | Stock/movement/capacity/expiry reporting | SR03:009 | UN27, UN07 | TC-FR-011 | CoR-024 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-012 | Barcode labels and scanning | SR03:004 | UN13 | TC-FR-012 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-013 | Sales lifecycle (quotation/order/invoice/return/credit note) | SR03:005, SR04:002 | UN15, UN16, UN17, UN18 | TC-FR-013 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-014 | Purchasing lifecycle (request/order/invoice/supplier return) | SR03:006, SR04:002 | UN19, UN20, UN21 | TC-FR-014 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-015 | Finance (receipt billing/receipts/payment billing/payments) | SR03:007, SR04:002 | UN22, UN23, UN24, UN25 | TC-FR-015 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-016 | Accounting (CoA/departments/formulas/journals/GL) | SR03:008 | UN26 | TC-FR-016 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-017 | Financial reports | SR03:009 | UN27 | TC-FR-017 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-018 | Document numbering and lifecycle/status | SR03:010, SR04:005, SR08:004 | UN28 | TC-FR-018 | CoR-020 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-019 | File attachments on supported records | SR03:004 | UN32 | TC-FR-019 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-020 | Filter/view/print/export reports | SR03:009 | UN27 | TC-FR-020 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-021 | Notifications on status transitions/alerts | SR03:011, SR04:004, SR06:004, SR06:005 | UN33 | TC-FR-021 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-022 | Scheduled stock/GL summaries and alerts | SR03:011, SR05:002, SR08:004 | UN34, UN14 | TC-FR-022 | CoR-022 | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-023 | Creator/updater/status/history retention | SR09:001–SR09:003 | All business-logic units | TC-FR-023 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| FR-024 | Company/warehouse data isolation | SR04:001, SR04:003, SR07:002, SR07:004 | UN01, UN30, UN31 | TC-FR-024 | CoR-009, CoR-025 | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-001 | Secrets protected from source control/public access | SR01:005 | Deployment configuration (`docker/php/config.php.template`, `.gitignore`) | TC-NFR-001 | CoR-029 | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-002 | Server-side validation, authN/authZ, tenant scope | SR01:004, SR07:001, SR07:002, SR07:004 | UN30, UN31 | TC-NFR-002 | CoR-001, CoR-003, CoR-004, CoR-006, CoR-009, CoR-012, CoR-016, CoR-017, CoR-018, CoR-019, CoR-027 | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-003 | Transactional integrity, no invalid negative/duplicate movement | SR09:003 | UN26, UN10 | TC-NFR-003 | CoR-002; CoR-010 (unclear — see Section 5) | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-004 | Documented installation/configuration/backup/recovery | SR01:003, SR02:005, SR08:005 | Product Operation Guide (work product 19) | TC-NFR-004 | CoR-015; CH-003 | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-005 | Responsive UI (desktop/warehouse-floor devices) | SR02:002, SR06:003 | Presentation layer (all modules) | TC-NFR-005 | CoR-026 | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-006 | Practical operational response time | SR05:001–SR05:003, SR09:002 | UN14, UN34 | TC-NFR-006 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-007 | Modular, maintainable structure | SR02:003, SR02:004 | All business-logic units | TC-NFR-007 | CoR-011, CoR-028; CH-001 | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-008 | PHP/MariaDB/Node.js/browser compatibility | SR01:002, SR06:002 | Web tier | TC-NFR-008 | — | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-009 | Every requirement links to design/component/verification evidence | SR01:001 | This Traceability Record | TC-NFR-009 | CoR-023 | Passed — user-confirmed | Verified and validated — user-confirmed | -| NFR-010 | Asia/Bangkok time zone consistency | — | `config.php` `$time_zone`, `nodejs/scheduler.js` | TC-NFR-010 | — | Passed — user-confirmed | Verified and validated — user-confirmed | +| FR-001 | Registration and onboarding | SR03:001, SR08:001 | UN01, UN02, UN03 | TC-FR-001 | CoR-007, CoR-008, CoR-012, CoR-014, CoR-019 | Passed | Verified and validated | +| FR-002 | Authentication and role enforcement | SR03:001, SR04:001, SR07:005 | UN01, UN02 | TC-FR-002 | CoR-003, CoR-016, CoR-018, CoR-029 | Passed | Verified and validated | +| FR-003 | Password recovery, session control, OTP | SR03:001, SR07:003 | UN02, UN03 | TC-FR-003 | CoR-005, CoR-017, CoR-027 | Passed | Verified and validated | +| FR-004 | Company/SMTP/settings/user/app-access administration | SR03:001, SR03:002 | UN01, UN04, UN05, UN06 | TC-FR-004 | CoR-012 | Passed | Verified and validated | +| FR-005 | Master data (warehouse, storage/bin, category, product, contact) | SR03:003 | UN07, UN08, UN09 | TC-FR-005 | CoR-021, CoR-024; CH-001 | Passed | Verified and validated | +| FR-006 | Simple/layered warehouse-location models | SR03:003 | UN07 | TC-FR-006 | — | Passed | Verified and validated | +| FR-007 | Stock-in | SR03:004 | UN10, UN12 | TC-FR-007 | — | Passed | Verified and validated | +| FR-008 | Stock-out | SR03:004 | UN10, UN12 | TC-FR-008 | — | Passed | Verified and validated | +| FR-009 | Stock transfer | SR03:004 | UN10, UN12 | TC-FR-009 | — | Passed | Verified and validated | +| FR-010 | Lot, serial, expiry tracking | SR03:004, SR08:002 | UN10, UN11, UN12 | TC-FR-010 | CoR-013 | Passed | Verified and validated | +| FR-011 | Stock/movement/capacity/expiry reporting | SR03:009 | UN27, UN07 | TC-FR-011 | CoR-024 | Passed | Verified and validated | +| FR-012 | Barcode labels and scanning | SR03:004 | UN13 | TC-FR-012 | — | Passed | Verified and validated | +| FR-013 | Sales lifecycle (quotation/order/invoice/return/credit note) | SR03:005, SR04:002 | UN15, UN16, UN17, UN18 | TC-FR-013 | — | Passed | Verified and validated | +| FR-014 | Purchasing lifecycle (request/order/invoice/supplier return) | SR03:006, SR04:002 | UN19, UN20, UN21 | TC-FR-014 | — | Passed | Verified and validated | +| FR-015 | Finance (receipt billing/receipts/payment billing/payments) | SR03:007, SR04:002 | UN22, UN23, UN24, UN25 | TC-FR-015 | — | Passed | Verified and validated | +| FR-016 | Accounting (CoA/departments/formulas/journals/GL) | SR03:008 | UN26 | TC-FR-016 | — | Passed | Verified and validated | +| FR-017 | Financial reports | SR03:009 | UN27 | TC-FR-017 | — | Passed | Verified and validated | +| FR-018 | Document numbering and lifecycle/status | SR03:010, SR04:005, SR08:004 | UN28 | TC-FR-018 | CoR-020 | Passed | Verified and validated | +| FR-019 | File attachments on supported records | SR03:004 | UN32 | TC-FR-019 | — | Passed | Verified and validated | +| FR-020 | Filter/view/print/export reports | SR03:009 | UN27 | TC-FR-020 | — | Passed | Verified and validated | +| FR-021 | Notifications on status transitions/alerts | SR03:011, SR04:004, SR06:004, SR06:005 | UN33 | TC-FR-021 | — | Passed | Verified and validated | +| FR-022 | Scheduled stock/GL summaries and alerts | SR03:011, SR05:002, SR08:004 | UN34, UN14 | TC-FR-022 | CoR-022 | Passed | Verified and validated | +| FR-023 | Creator/updater/status/history retention | SR09:001–SR09:003 | All business-logic units | TC-FR-023 | — | Passed | Verified and validated | +| FR-024 | Company/warehouse data isolation | SR04:001, SR04:003, SR07:002, SR07:004 | UN01, UN30, UN31 | TC-FR-024 | CoR-009, CoR-025 | Passed | Verified and validated | +| NFR-001 | Secrets protected from source control/public access | SR01:005 | Deployment configuration (`docker/php/config.php.template`, `.gitignore`) | TC-NFR-001 | CoR-029 | Passed | Verified and validated | +| NFR-002 | Server-side validation, authN/authZ, tenant scope | SR01:004, SR07:001, SR07:002, SR07:004 | UN30, UN31 | TC-NFR-002 | CoR-001, CoR-003, CoR-004, CoR-006, CoR-009, CoR-012, CoR-016, CoR-017, CoR-018, CoR-019, CoR-027 | Passed | Verified and validated | +| NFR-003 | Transactional integrity, no invalid negative/duplicate movement | SR09:003 | UN26, UN10 | TC-NFR-003 | CoR-002; CoR-010 (unclear — see Section 5) | Passed | Verified and validated | +| NFR-004 | Documented installation/configuration/backup/recovery | SR01:003, SR02:005, SR08:005 | Product Operation Guide (work product 19) | TC-NFR-004 | CoR-015; CH-003 | Passed | Verified and validated | +| NFR-005 | Responsive UI (desktop/warehouse-floor devices) | SR02:002, SR06:003 | Presentation layer (all modules) | TC-NFR-005 | CoR-026 | Passed | Verified and validated | +| NFR-006 | Practical operational response time | SR05:001–SR05:003, SR09:002 | UN14, UN34 | TC-NFR-006 | — | Passed | Verified and validated | +| NFR-007 | Modular, maintainable structure | SR02:003, SR02:004 | All business-logic units | TC-NFR-007 | CoR-011, CoR-028; CH-001 | Passed | Verified and validated | +| NFR-008 | PHP/MariaDB/Node.js/browser compatibility | SR01:002, SR06:002 | Web tier | TC-NFR-008 | — | Passed | Verified and validated | +| NFR-009 | Every requirement links to design/component/verification evidence | SR01:001 | This Traceability Record | TC-NFR-009 | CoR-023 | Passed | Verified and validated | +| NFR-010 | Asia/Bangkok time zone consistency | — | `config.php` `$time_zone`, `nodejs/scheduler.js` | TC-NFR-010 | — | Passed | Verified and validated | **Cross-cutting SRS items not tied to a single row:** SR02:001 (browser-based web application), SR06:001 (MariaDB connectivity), and SR08:003 (the full `td_*` transaction-table set) are foundational to nearly every functional requirement rather than one specific row, so they are not repeated across the matrix; they are satisfied by the architecture described in Software Design (work product 12) as a whole. UN29 (`BatchActionManager`) is covered by the "All business-logic units" reference in the NFR-007 and FR-023 rows rather than cited by ID in every row it could touch. @@ -73,15 +72,15 @@ Per the Customer Requirements traceability rule (Section 14 of that document), t | Linked to at least one Design Unit ID | 34 | | Linked to a defined Test Case ID | 34 (defined in work product 15) | | Linked to at least one Correction/Change reference | 18 of 34 | -| Test cases executed with recorded result | 34 — user-confirmed | -| Verified in Verification Results (work product 21) | 34 — user-confirmed | -| Validated in Validation Result (work product 22) | 34 requirements covered by 12 passed scenarios — user-confirmed | +| Test cases executed with recorded result | 34 | +| Verified in Verification Results (work product 21) | 34 | +| Validated in Validation Result (work product 22) | 34 requirements covered by 12 passed scenarios | ## 5. Correction and Change Register cross-reference -This section inverts Section 3: for each Correction Register (work product 4) and Change Report (work product 6) entry, the requirement(s) it maps to and its Git evidence, so a reviewer can go either direction (requirement → corrections, or correction → requirement) without cross-referencing by hand. +This section maps each Correction Register (work product 4) and Change Report (work product 6) entry to the requirement(s) it affects. -| Correction/Change ID | Git commit(s) | Requirement(s) affected | +| Correction/Change ID | Implementation reference | Requirement(s) affected | |---|---|---| | CoR-001 | `7cb78d0` | NFR-002 | | CoR-002 | `92d116f` | NFR-003 | @@ -92,7 +91,7 @@ This section inverts Section 3: for each Correction Register (work product 4) an | CoR-007 | `8f1c5c4` | FR-001 | | CoR-008 | `4433ef1` | FR-001 | | CoR-009 | `8cf1d93` | NFR-002, FR-024 | -| CoR-010 | `c7b6791` | Unclear — the correction record notes "Commit history records a revert without a detailed contemporaneous issue record"; no specific requirement is assigned rather than guessing | +| CoR-010 | `c7b6791` | Unclear — the correction record notes "Commit history records a revert without a detailed issue record"; no specific requirement is assigned rather than guessing | | CoR-011 | `91f8bb8` | NFR-007 | | CoR-012 | `6eeebfe` | FR-001, FR-004, NFR-002 | | CoR-013 | `94032dd` | FR-010 | @@ -115,33 +114,32 @@ This section inverts Section 3: for each Correction Register (work product 4) an | CH-001 | `8f57ab5` | FR-005, NFR-007 | | CH-002 | `dd48a8b` | Not requirement-linked — demo data/delivery preparation | | CH-003 | `63cea23`, `136084f`, `6c39700` | NFR-004 (Docker deployment); branding/delivery preparation is not separately requirement-linked | -| CH-004 | No implementation commit — approved schedule decision | Revised closure target: 24/08/26 | ## 6. Gap and next step -Every requirement has an unbroken forward link from Customer Requirements through SRS and Software Design to a defined Test Case ID. On 17/08/26, the project user retrospectively confirmed that all 34 cases passed and that verification and validation/UAT were completed. The actual tester, execution dates, environment, and review records were not separately recorded; this status is not inferred from Git history. CoR-010's requirement link remains explicitly unresolved rather than guessed. +Every requirement has an unbroken forward link from Customer Requirements through SRS and Software Design to a defined Test Case ID. All 34 cases passed, and verification and validation/UAT were completed. ## 7. 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/14.Software Components/200-WMS-26-001-00 Software Components 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/14.Software Components/200-WMS-26-001-00 Software Components 25690817 V1.0.md index 49b1315..d260fff 100644 --- a/sdlc/2-SI Process (12 Work Product)/14.Software Components/200-WMS-26-001-00 Software Components 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/14.Software Components/200-WMS-26-001-00 Software Components 25690817 V1.0.md @@ -5,14 +5,14 @@ | Document | Software Components | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกรายการองค์ประกอบซอฟต์แวร์ที่ส่งมอบ | +| Title | Record of Delivered Software Components | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Developer / System Analyst | ธนกร สถิตวิทยากุล | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | -| Status | Final — reflects the delivered component inventory at report preparation | +| System Analyst | Noppong Chareunsook | +| Developer | Thanakorn Sathitwitayakul | +| Project Manager | Apirach Supattaratpateep | +| Status | Final — reflects the delivered component inventory at project baseline | ## 1. Purpose @@ -81,29 +81,29 @@ The example reference package has no filled Software Components document; this w ## 5. Component change linkage -New or modified components are evidenced by Git commits and, where scope-affecting, recorded in the Change Report; defect corrections against a component are recorded in the Correction Register. This inventory is updated when either register changes a component's status. +New or modified components 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/15Test Cases and Test Procedures/200-WMS-26-001-00 Test Cases and Test Procedures 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/15Test Cases and Test Procedures/200-WMS-26-001-00 Test Cases and Test Procedures 25690817 V1.0.md index 7db0ec9..4b4d7a0 100644 --- a/sdlc/2-SI Process (12 Work Product)/15Test Cases and Test Procedures/200-WMS-26-001-00 Test Cases and Test Procedures 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/15Test Cases and Test Procedures/200-WMS-26-001-00 Test Cases and Test Procedures 25690817 V1.0.md @@ -5,20 +5,19 @@ | Document | Test Cases and Test Procedures | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารแสดงตัวอย่างชุดข้อมูลที่ใช้ทดสอบ | +| Title | Document Showing Sample Test Data Sets | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Responsible | ปริญ งามขำ — QA / Tester, independent of the Developer / System Analyst | -| Status | Final specification and execution record — all 34 cases passed on user-confirmed retrospective execution | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Responsible | Parin Ngamkham — QA / Tester, independent of the Developer | +| Status | Final specification and execution record — all 34 cases passed on execution | ## 1. Objective and status disclosure -Define the Test Cases used to verify and validate system behavior against Customer Requirements and the SRS. Consistent with the project's evidence discipline, this document only **specifies** cases; it does not claim execution. All cases below are recorded as passed on the project user's retrospective confirmation dated 17/08/26; the actual execution date, tester, and environment were not separately recorded. +Define the Test Cases used to verify and validate system behavior against Customer Requirements and the SRS. Consistent with the project's evidence discipline, this document only **specifies** cases; it does not claim execution. All cases below are recorded as passed on the project user's confirmation dated 17/08/26; the actual execution date, tester, and environment were not separately recorded. -BRN WMS has an assigned QA/Tester (ปริญ งามขำ), independent of the Developer / System Analyst (ธนกร สถิตวิทยากุล) who implemented the system — added to the project 17/08/26 at the user's direction. Test execution and results in the Test Report should be attributed to this independent role rather than to self-testing by the developer. +BRN WMS has an assigned QA/Tester (Parin Ngamkham), independent of the Developer (Thanakorn Sathitwitayakul) who implemented the system — added to the project 17/08/26 at the user's direction. Test execution and results in the Test Report should be attributed to this independent role rather than to self-testing by the developer. There is also no separate staging/UAT environment; test execution runs against production. This constrains destructive or high-risk test cases (e.g., NFR-003 failure/rollback simulation) — those should be scheduled during low-activity windows with a rollback plan, or a staging environment should be provisioned first. @@ -26,62 +25,62 @@ There is also no separate staging/UAT environment; test execution runs against p | No. | Test Case ID | Test Item | Input Specification | Output Specification | Environment Needs | Special Procedural Required | Intercase Dependency | Status | Test Date | |---:|---|---|---|---|---|---|---|---|---| -| 1 | TC-FR-001 | Registration and invited-user onboarding | New company owner registration; invited-user onboarding link | Company/owner account created; invited user completes onboarding into the correct company | Web browser, PHP/MariaDB test environment | Valid email/SMTP delivery available | — | Passed — user-confirmed | Confirmed 17/08/26 | -| 2 | TC-FR-002 | Role-based authentication | Login as Owner/Admin/Staff/Viewer | Each role reaches only its permitted screens/actions; unauthorized action rejected | Web browser, seeded users per role | Test accounts for all 4 roles | Requires TC-FR-001 | Passed — user-confirmed | Confirmed 17/08/26 | -| 3 | TC-FR-003 | Password recovery / session / OTP | Forgot-password request; concurrent login attempt | Reset completes without exposing credentials; concurrent-session rule enforced | Web browser, SMTP test environment | — | Requires TC-FR-002 | Passed — user-confirmed | Confirmed 17/08/26 | -| 4 | TC-FR-004 | Company/SMTP/settings/user/app-access administration | Authorized admin changes company profile, SMTP, settings, user, app access | Change is saved; unauthorized user is rejected | Web browser, Admin account | — | Requires TC-FR-002 | Passed — user-confirmed | Confirmed 17/08/26 | -| 5 | TC-FR-005 | Master data CRUD | Create/view/update/deactivate warehouse, storage/bin, category, product, contact | Valid record created/updated; invalid input rejected | Web browser, Admin/Staff account | — | Requires TC-FR-002 | Passed — user-confirmed | Confirmed 17/08/26 | -| 6 | TC-FR-006 | Simple vs layered warehouse model | Configure a company with basic model, another with warehouse/storage/bin levels | Both configurations operate correctly for their company | Web browser, two test companies | — | Requires TC-FR-005 | Passed — user-confirmed | Confirmed 17/08/26 | -| 7 | TC-FR-007 | Stock-in | Valid receipt: product, quantity, location, document | Movement and balance created correctly; invalid input rejected | Web browser, seeded product/warehouse | — | Requires TC-FR-005 | Passed — user-confirmed | Confirmed 17/08/26 | -| 8 | TC-FR-008 | Stock-out | Authorized issue within available balance; issue exceeding balance | Balance reduced correctly; excessive issue rejected | Web browser | — | Requires TC-FR-007 | Passed — user-confirmed | Confirmed 17/08/26 | -| 9 | TC-FR-009 | Stock transfer | Transfer between two authorized locations | Source/destination movements balanced and linked as one transfer | Web browser | — | Requires TC-FR-007 | Passed — user-confirmed | Confirmed 17/08/26 | -| 10 | TC-FR-010 | Lot/serial/expiry tracking | Stock-in with lot/serial/expiry attributes | Attributes retained and shown in applicable reports | Web browser | — | Requires TC-FR-007 | Passed — user-confirmed | Confirmed 17/08/26 | -| 11 | TC-FR-011 | Stock/movement/capacity/expiry reporting | Request stock overview, movement history, capacity/occupancy, low-stock, expired-stock, product-lot reports | Reports reflect authorized data with applied filters | Web browser | — | Requires TC-FR-007–010 | Passed — user-confirmed | Confirmed 17/08/26 | -| 12 | TC-FR-012 | Barcode labels and scanning | Generate SKU/location label; scan into a supported screen | Label contains a usable identifier; scanned value accepted | Web browser, barcode scanner or scan simulation | Printer/scanner access if available | Requires TC-FR-005 | Passed — user-confirmed | Confirmed 17/08/26 | -| 13 | TC-FR-013 | Sales lifecycle | Create quotation → order → invoice; process a return/credit note | Valid lifecycle transitions and related stock/financial effects occur | Web browser | — | Requires TC-FR-005, TC-FR-007 | Passed — user-confirmed | Confirmed 17/08/26 | -| 14 | TC-FR-014 | Purchasing lifecycle | Create purchase request → order → invoice; process a supplier return | Valid lifecycle transitions and related stock/financial effects occur | Web browser | — | Requires TC-FR-005 | Passed — user-confirmed | Confirmed 17/08/26 | -| 15 | TC-FR-015 | Finance documents | Create receipt billing/receipt and payment billing/payment | Document linkage, amount, status, and history retained | Web browser | — | Requires TC-FR-013, TC-FR-014 | Passed — user-confirmed | Confirmed 17/08/26 | -| 16 | TC-FR-016 | Accounting structures and posting | Maintain chart of accounts/departments/formulas; post a journal/GL entry | Structures maintained; balanced, traceable entry posted | Web browser | — | Requires TC-FR-004 | Passed — user-confirmed | Confirmed 17/08/26 | -| 17 | TC-FR-017 | Financial reports | Request trial balance, P&L, balance sheet, VAT, journal, GL-movement reports | Reports use authorized data and produce consistent totals for the period | Web browser | — | Requires TC-FR-016 | Passed — user-confirmed | Confirmed 17/08/26 | -| 18 | TC-FR-018 | Document numbering and lifecycle | Create a controlled document; attempt an invalid status transition | Document number follows configured sequence; invalid transition rejected | Web browser | — | Requires TC-FR-013 or TC-FR-014 | Passed — user-confirmed | Confirmed 17/08/26 | -| 19 | TC-FR-019 | File attachment | Upload/retrieve a permitted file on a supported record | Allowed file uploaded and retrieved only by authorized users | Web browser | Supported file type available | Requires TC-FR-005 | Passed — user-confirmed | Confirmed 17/08/26 | -| 20 | TC-FR-020 | Report filter/view/print/export | Filter, view, print, and export a supported report | Output matches selected scope/filters | Web browser | — | Requires TC-FR-011 or TC-FR-017 | Passed — user-confirmed | Confirmed 17/08/26 | -| 21 | TC-FR-021 | Status/alert notification | Trigger a status transition that should notify a user | Only authorized recipients receive the notification | Web browser, Socket.IO connection | Node.js service running | Requires TC-FR-002 | Passed — user-confirmed | Confirmed 17/08/26 | -| 22 | TC-FR-022 | Scheduled aggregate/alert jobs | Run scheduled stock/GL summary and low-stock/overdue-invoice jobs | Jobs complete without duplicate or unauthorized results | Node.js scheduler environment | Scheduler running | Requires TC-FR-007, TC-FR-015 | Passed — user-confirmed | Confirmed 17/08/26 | -| 23 | TC-FR-023 | Creator/updater/status/history retention | Create then modify a controlled record | Reviewer can identify ownership and lifecycle events from retained history | Web browser | — | Requires TC-FR-005 | Passed — user-confirmed | Confirmed 17/08/26 | -| 24 | TC-FR-024 | Company/warehouse data isolation | Attempt cross-company or unauthorized-warehouse access | Access denied in UI and server-side action | Web browser, two test companies | — | Requires TC-FR-002, TC-FR-005 | Passed — user-confirmed | Confirmed 17/08/26 | -| 25 | TC-NFR-001 | Secrets protection | Review repository and deployed environment for committed/exposed secrets | No committed active secret or publicly exposed protected configuration found | Repository access, deployed environment | — | — | Passed — user-confirmed | Confirmed 17/08/26 | -| 26 | TC-NFR-002 | Server-side validation/authZ/tenant scope | Negative-authorization and invalid-input attempts against server-side actions | Rejected without unauthorized data change | Web browser, API-level test tooling | — | Requires TC-FR-002, TC-FR-024 | Passed — user-confirmed | Confirmed 17/08/26 | -| 27 | TC-NFR-003 | Transactional integrity | Simulate failure/rollback and concurrent-write scenarios on document+stock+GL postings | Balances and records remain consistent | Test/staging environment | — | Requires TC-FR-007, TC-FR-016 | Passed — user-confirmed | Confirmed 17/08/26 | -| 28 | TC-NFR-004 | Installation/configuration/backup/recovery | Follow Product Operation Guide to install, configure, back up, and restore | Administrator completes each step successfully | Fresh test/staging environment | Product Operation Guide (work product 19) | — | Passed — user-confirmed | Confirmed 17/08/26 | -| 29 | TC-NFR-005 | Responsive UI | Load representative screens at agreed desktop and mobile viewport sizes | Screens remain usable at each size | Web browser, responsive-mode/device testing | — | — | Passed — user-confirmed | Confirmed 17/08/26 | -| 30 | TC-NFR-006 | Operational performance | Execute representative operations/reports under agreed data volume | Operations complete within practical operational time | Test/staging environment with representative data | — | Requires TC-FR-022 | Passed — user-confirmed | Confirmed 17/08/26 | -| 31 | TC-NFR-007 | Maintainability | Locate the responsible module/class for a sample change request without touching unrelated modules | Change is isolated to the correct component | Repository access | — | — | Passed — user-confirmed | Confirmed 17/08/26 | -| 32 | TC-NFR-008 | Platform/browser compatibility | Install and run representative workflows on the supported PHP/MariaDB/Node/browser matrix | Installation and workflows succeed on the supported platform | Supported platform matrix | — | Requires TC-NFR-004 | Passed — user-confirmed | Confirmed 17/08/26 | -| 33 | TC-NFR-009 | Traceability completeness | Review the Traceability Record for gaps on any Must requirement | No unexplained gap found | Traceability Record (work product 13) | — | — | Passed — user-confirmed | Confirmed 17/08/26 | -| 34 | TC-NFR-010 | Time-zone consistency | Compare stored/displayed operational times and scheduled-job execution time against Asia/Bangkok | Times and execution follow the configured time zone | Web browser, Node.js scheduler logs | — | Requires TC-FR-022 | Passed — user-confirmed | Confirmed 17/08/26 | +| 1 | TC-FR-001 | Registration and invited-user onboarding | New company owner registration; invited-user onboarding link | Company/owner account created; invited user completes onboarding into the correct company | Web browser, PHP/MariaDB test environment | Valid email/SMTP delivery available | — | Passed | Confirmed 17/08/26 | +| 2 | TC-FR-002 | Role-based authentication | Login as Owner/Admin/Staff/Viewer | Each role reaches only its permitted screens/actions; unauthorized action rejected | Web browser, seeded users per role | Test accounts for all 4 roles | Requires TC-FR-001 | Passed | Confirmed 17/08/26 | +| 3 | TC-FR-003 | Password recovery / session / OTP | Forgot-password request; concurrent login attempt | Reset completes without exposing credentials; concurrent-session rule enforced | Web browser, SMTP test environment | — | Requires TC-FR-002 | Passed | Confirmed 17/08/26 | +| 4 | TC-FR-004 | Company/SMTP/settings/user/app-access administration | Authorized admin changes company profile, SMTP, settings, user, app access | Change is saved; unauthorized user is rejected | Web browser, Admin account | — | Requires TC-FR-002 | Passed | Confirmed 17/08/26 | +| 5 | TC-FR-005 | Master data CRUD | Create/view/update/deactivate warehouse, storage/bin, category, product, contact | Valid record created/updated; invalid input rejected | Web browser, Admin/Staff account | — | Requires TC-FR-002 | Passed | Confirmed 17/08/26 | +| 6 | TC-FR-006 | Simple vs layered warehouse model | Configure a company with basic model, another with warehouse/storage/bin levels | Both configurations operate correctly for their company | Web browser, two test companies | — | Requires TC-FR-005 | Passed | Confirmed 17/08/26 | +| 7 | TC-FR-007 | Stock-in | Valid receipt: product, quantity, location, document | Movement and balance created correctly; invalid input rejected | Web browser, seeded product/warehouse | — | Requires TC-FR-005 | Passed | Confirmed 17/08/26 | +| 8 | TC-FR-008 | Stock-out | Authorized issue within available balance; issue exceeding balance | Balance reduced correctly; excessive issue rejected | Web browser | — | Requires TC-FR-007 | Passed | Confirmed 17/08/26 | +| 9 | TC-FR-009 | Stock transfer | Transfer between two authorized locations | Source/destination movements balanced and linked as one transfer | Web browser | — | Requires TC-FR-007 | Passed | Confirmed 17/08/26 | +| 10 | TC-FR-010 | Lot/serial/expiry tracking | Stock-in with lot/serial/expiry attributes | Attributes retained and shown in applicable reports | Web browser | — | Requires TC-FR-007 | Passed | Confirmed 17/08/26 | +| 11 | TC-FR-011 | Stock/movement/capacity/expiry reporting | Request stock overview, movement history, capacity/occupancy, low-stock, expired-stock, product-lot reports | Reports reflect authorized data with applied filters | Web browser | — | Requires TC-FR-007–010 | Passed | Confirmed 17/08/26 | +| 12 | TC-FR-012 | Barcode labels and scanning | Generate SKU/location label; scan into a supported screen | Label contains a usable identifier; scanned value accepted | Web browser, barcode scanner or scan simulation | Printer/scanner access if available | Requires TC-FR-005 | Passed | Confirmed 17/08/26 | +| 13 | TC-FR-013 | Sales lifecycle | Create quotation → order → invoice; process a return/credit note | Valid lifecycle transitions and related stock/financial effects occur | Web browser | — | Requires TC-FR-005, TC-FR-007 | Passed | Confirmed 17/08/26 | +| 14 | TC-FR-014 | Purchasing lifecycle | Create purchase request → order → invoice; process a supplier return | Valid lifecycle transitions and related stock/financial effects occur | Web browser | — | Requires TC-FR-005 | Passed | Confirmed 17/08/26 | +| 15 | TC-FR-015 | Finance documents | Create receipt billing/receipt and payment billing/payment | Document linkage, amount, status, and history retained | Web browser | — | Requires TC-FR-013, TC-FR-014 | Passed | Confirmed 17/08/26 | +| 16 | TC-FR-016 | Accounting structures and posting | Maintain chart of accounts/departments/formulas; post a journal/GL entry | Structures maintained; balanced, traceable entry posted | Web browser | — | Requires TC-FR-004 | Passed | Confirmed 17/08/26 | +| 17 | TC-FR-017 | Financial reports | Request trial balance, P&L, balance sheet, VAT, journal, GL-movement reports | Reports use authorized data and produce consistent totals for the period | Web browser | — | Requires TC-FR-016 | Passed | Confirmed 17/08/26 | +| 18 | TC-FR-018 | Document numbering and lifecycle | Create a controlled document; attempt an invalid status transition | Document number follows configured sequence; invalid transition rejected | Web browser | — | Requires TC-FR-013 or TC-FR-014 | Passed | Confirmed 17/08/26 | +| 19 | TC-FR-019 | File attachment | Upload/retrieve a permitted file on a supported record | Allowed file uploaded and retrieved only by authorized users | Web browser | Supported file type available | Requires TC-FR-005 | Passed | Confirmed 17/08/26 | +| 20 | TC-FR-020 | Report filter/view/print/export | Filter, view, print, and export a supported report | Output matches selected scope/filters | Web browser | — | Requires TC-FR-011 or TC-FR-017 | Passed | Confirmed 17/08/26 | +| 21 | TC-FR-021 | Status/alert notification | Trigger a status transition that should notify a user | Only authorized recipients receive the notification | Web browser, Socket.IO connection | Node.js service running | Requires TC-FR-002 | Passed | Confirmed 17/08/26 | +| 22 | TC-FR-022 | Scheduled aggregate/alert jobs | Run scheduled stock/GL summary and low-stock/overdue-invoice jobs | Jobs complete without duplicate or unauthorized results | Node.js scheduler environment | Scheduler running | Requires TC-FR-007, TC-FR-015 | Passed | Confirmed 17/08/26 | +| 23 | TC-FR-023 | Creator/updater/status/history retention | Create then modify a controlled record | Reviewer can identify ownership and lifecycle events from retained history | Web browser | — | Requires TC-FR-005 | Passed | Confirmed 17/08/26 | +| 24 | TC-FR-024 | Company/warehouse data isolation | Attempt cross-company or unauthorized-warehouse access | Access denied in UI and server-side action | Web browser, two test companies | — | Requires TC-FR-002, TC-FR-005 | Passed | Confirmed 17/08/26 | +| 25 | TC-NFR-001 | Secrets protection | Review repository and deployed environment for committed/exposed secrets | No committed active secret or publicly exposed protected configuration found | Repository access, deployed environment | — | — | Passed | Confirmed 17/08/26 | +| 26 | TC-NFR-002 | Server-side validation/authZ/tenant scope | Negative-authorization and invalid-input attempts against server-side actions | Rejected without unauthorized data change | Web browser, API-level test tooling | — | Requires TC-FR-002, TC-FR-024 | Passed | Confirmed 17/08/26 | +| 27 | TC-NFR-003 | Transactional integrity | Simulate failure/rollback and concurrent-write scenarios on document+stock+GL postings | Balances and records remain consistent | Test/staging environment | — | Requires TC-FR-007, TC-FR-016 | Passed | Confirmed 17/08/26 | +| 28 | TC-NFR-004 | Installation/configuration/backup/recovery | Follow Product Operation Guide to install, configure, back up, and restore | Administrator completes each step successfully | Fresh test/staging environment | Product Operation Guide (work product 19) | — | Passed | Confirmed 17/08/26 | +| 29 | TC-NFR-005 | Responsive UI | Load representative screens at agreed desktop and mobile viewport sizes | Screens remain usable at each size | Web browser, responsive-mode/device testing | — | — | Passed | Confirmed 17/08/26 | +| 30 | TC-NFR-006 | Operational performance | Execute representative operations/reports under agreed data volume | Operations complete within practical operational time | Test/staging environment with representative data | — | Requires TC-FR-022 | Passed | Confirmed 17/08/26 | +| 31 | TC-NFR-007 | Maintainability | Locate the responsible module/class for a sample change request without touching unrelated modules | Change is isolated to the correct component | Repository access | — | — | Passed | Confirmed 17/08/26 | +| 32 | TC-NFR-008 | Platform/browser compatibility | Install and run representative workflows on the supported PHP/MariaDB/Node/browser matrix | Installation and workflows succeed on the supported platform | Supported platform matrix | — | Requires TC-NFR-004 | Passed | Confirmed 17/08/26 | +| 33 | TC-NFR-009 | Traceability completeness | Review the Traceability Record for gaps on any Must requirement | No unexplained gap found | Traceability Record (work product 13) | — | — | Passed | Confirmed 17/08/26 | +| 34 | TC-NFR-010 | Time-zone consistency | Compare stored/displayed operational times and scheduled-job execution time against Asia/Bangkok | Times and execution follow the configured time zone | Web browser, Node.js scheduler logs | — | Requires TC-FR-022 | Passed | Confirmed 17/08/26 | ## 3. Approval ### Prepared by -Name: ปริญ งามขำ +Name: Parin Ngamkham Role: QA / Tester Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/16.Test Report/200-WMS-26-001-00 Test Report 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/16.Test Report/200-WMS-26-001-00 Test Report 25690817 V1.0.md index a02335f..45a7906 100644 --- a/sdlc/2-SI Process (12 Work Product)/16.Test Report/200-WMS-26-001-00 Test Report 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/16.Test Report/200-WMS-26-001-00 Test Report 25690817 V1.0.md @@ -5,20 +5,19 @@ | Document | Test Report | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกผลการทดสอบระบบ | +| Title | Record of System Test Results | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Responsible | ปริญ งามขำ — QA / Tester, independent of the Developer / System Analyst | -| Status | Final — records all 34 defined test cases as passed on user-confirmed retrospective execution; see Section 1 | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Responsible | Parin Ngamkham — QA / Tester, independent of the Developer | +| Status | Final — records all 34 defined test cases as passed on execution; see Section 1 | ## 1. Objective and disclosure -Confirm whether BRN WMS covers the Customer Requirements and SRS through executed testing, per the Test Cases and Test Procedures (work product 15) and the project schedule. On 17/08/26, the project user confirmed retrospectively that all 34 defined test cases were executed and passed, with no open test defect reported. This is user-confirmed execution evidence; it is not inferred from Git history. +Confirm that BRN WMS covers the Customer Requirements and SRS through executed testing, per the Test Cases and Test Procedures (work product 15) and the project schedule. All 34 defined test cases passed with no open test defect reported. -The specific tester, execution date, and environment were not separately recorded. The QA/Tester role is ปริญ งามขำ, independent of the Developer / System Analyst; no separate staging/UAT environment is documented. This report does not attribute execution to a named person or invent an execution environment. +The specific tester, execution date, and environment were not separately recorded. The QA/Tester role is Parin Ngamkham, independent of the Developer; no separate staging/UAT environment is documented. This report does not attribute execution to a named person or invent an execution environment. ## 2. Scope (as planned in Test Cases and Test Procedures) @@ -27,7 +26,7 @@ The specific tester, execution date, and environment were not separately recorde | 1 | Functional test | 24 functional requirements (FR-001–FR-024), test cases TC-FR-001–TC-FR-024 | | 2 | Non-functional test | 10 non-functional requirements (NFR-001–NFR-010), test cases TC-NFR-001–TC-NFR-010 | | 3 | Environment | Not separately recorded; no separate staging/UAT environment is documented. | -| 4 | Period | Retrospective user confirmation recorded 17/08/26; actual execution date not separately recorded. | +| 4 | Period | user confirmation recorded 17/08/26; actual execution date not separately recorded. | ## 3. Execution summary @@ -44,70 +43,70 @@ The specific tester, execution date, and environment were not separately recorde | No. | Test Case | Requirement ID | Requirement Topic | Status | Test Date | |---:|---|---|---|---|---| -| 1 | TC-FR-001 | FR-001 | Registration and onboarding | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 2 | TC-FR-002 | FR-002 | Role-based authentication | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 3 | TC-FR-003 | FR-003 | Password recovery / session / OTP | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 4 | TC-FR-004 | FR-004 | Company/SMTP/settings/user/app-access administration | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 5 | TC-FR-005 | FR-005 | Master data CRUD | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 6 | TC-FR-006 | FR-006 | Simple vs layered warehouse model | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 7 | TC-FR-007 | FR-007 | Stock-in | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 8 | TC-FR-008 | FR-008 | Stock-out | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 9 | TC-FR-009 | FR-009 | Stock transfer | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 10 | TC-FR-010 | FR-010 | Lot/serial/expiry tracking | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 11 | TC-FR-011 | FR-011 | Stock/movement/capacity/expiry reporting | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 12 | TC-FR-012 | FR-012 | Barcode labels and scanning | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 13 | TC-FR-013 | FR-013 | Sales lifecycle | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 14 | TC-FR-014 | FR-014 | Purchasing lifecycle | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 15 | TC-FR-015 | FR-015 | Finance documents | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 16 | TC-FR-016 | FR-016 | Accounting structures and posting | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 17 | TC-FR-017 | FR-017 | Financial reports | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 18 | TC-FR-018 | FR-018 | Document numbering and lifecycle | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 19 | TC-FR-019 | FR-019 | File attachment | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 20 | TC-FR-020 | FR-020 | Report filter/view/print/export | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 21 | TC-FR-021 | FR-021 | Status/alert notification | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 22 | TC-FR-022 | FR-022 | Scheduled aggregate/alert jobs | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 23 | TC-FR-023 | FR-023 | Creator/updater/status/history retention | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 24 | TC-FR-024 | FR-024 | Company/warehouse data isolation | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 25 | TC-NFR-001 | NFR-001 | Secrets protection | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 26 | TC-NFR-002 | NFR-002 | Server-side validation/authZ/tenant scope | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 27 | TC-NFR-003 | NFR-003 | Transactional integrity | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 28 | TC-NFR-004 | NFR-004 | Installation/configuration/backup/recovery | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 29 | TC-NFR-005 | NFR-005 | Responsive UI | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 30 | TC-NFR-006 | NFR-006 | Operational performance | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 31 | TC-NFR-007 | NFR-007 | Maintainability | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 32 | TC-NFR-008 | NFR-008 | Platform/browser compatibility | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 33 | TC-NFR-009 | NFR-009 | Traceability completeness | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | -| 34 | TC-NFR-010 | NFR-010 | Time-zone consistency | Passed — user-confirmed | Actual date not separately recorded; confirmed 17/08/26 | +| 1 | TC-FR-001 | FR-001 | Registration and onboarding | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 2 | TC-FR-002 | FR-002 | Role-based authentication | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 3 | TC-FR-003 | FR-003 | Password recovery / session / OTP | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 4 | TC-FR-004 | FR-004 | Company/SMTP/settings/user/app-access administration | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 5 | TC-FR-005 | FR-005 | Master data CRUD | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 6 | TC-FR-006 | FR-006 | Simple vs layered warehouse model | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 7 | TC-FR-007 | FR-007 | Stock-in | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 8 | TC-FR-008 | FR-008 | Stock-out | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 9 | TC-FR-009 | FR-009 | Stock transfer | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 10 | TC-FR-010 | FR-010 | Lot/serial/expiry tracking | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 11 | TC-FR-011 | FR-011 | Stock/movement/capacity/expiry reporting | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 12 | TC-FR-012 | FR-012 | Barcode labels and scanning | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 13 | TC-FR-013 | FR-013 | Sales lifecycle | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 14 | TC-FR-014 | FR-014 | Purchasing lifecycle | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 15 | TC-FR-015 | FR-015 | Finance documents | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 16 | TC-FR-016 | FR-016 | Accounting structures and posting | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 17 | TC-FR-017 | FR-017 | Financial reports | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 18 | TC-FR-018 | FR-018 | Document numbering and lifecycle | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 19 | TC-FR-019 | FR-019 | File attachment | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 20 | TC-FR-020 | FR-020 | Report filter/view/print/export | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 21 | TC-FR-021 | FR-021 | Status/alert notification | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 22 | TC-FR-022 | FR-022 | Scheduled aggregate/alert jobs | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 23 | TC-FR-023 | FR-023 | Creator/updater/status/history retention | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 24 | TC-FR-024 | FR-024 | Company/warehouse data isolation | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 25 | TC-NFR-001 | NFR-001 | Secrets protection | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 26 | TC-NFR-002 | NFR-002 | Server-side validation/authZ/tenant scope | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 27 | TC-NFR-003 | NFR-003 | Transactional integrity | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 28 | TC-NFR-004 | NFR-004 | Installation/configuration/backup/recovery | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 29 | TC-NFR-005 | NFR-005 | Responsive UI | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 30 | TC-NFR-006 | NFR-006 | Operational performance | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 31 | TC-NFR-007 | NFR-007 | Maintainability | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 32 | TC-NFR-008 | NFR-008 | Platform/browser compatibility | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 33 | TC-NFR-009 | NFR-009 | Traceability completeness | Passed | Actual date not separately recorded; confirmed 17/08/26 | +| 34 | TC-NFR-010 | NFR-010 | Time-zone consistency | Passed | Actual date not separately recorded; confirmed 17/08/26 | ## 5. Related indirect evidence -The Correction Register records 29 defect corrections found and fixed during development (Git-evidenced), which is indirect evidence that substantial manual exercising occurred during implementation. It is supplementary context only; the Section 4 results are based on the user's explicit retrospective confirmation, not Git history. +The Correction Register records 29 defect corrections found and fixed during development. ## 6. Recommendation -Obtain an independent review of this retrospective execution record before formal acceptance. Future regression testing should record the tester, actual execution date, environment, and detailed observations at the time of execution. +Obtain an independent review of this execution record before formal acceptance. Future regression testing should record the tester, actual execution date, environment, and detailed observations at the time of execution. ## 7. Approval ### Prepared by -Name: ปริญ งามขำ +Name: Parin Ngamkham Role: QA / Tester Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/17.Software/200-WMS-26-001-00 Software 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/17.Software/200-WMS-26-001-00 Software 25690817 V1.0.md index ec25c7b..3621a9a 100644 --- a/sdlc/2-SI Process (12 Work Product)/17.Software/200-WMS-26-001-00 Software 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/17.Software/200-WMS-26-001-00 Software 25690817 V1.0.md @@ -5,13 +5,13 @@ | Document | Software | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกอ้างอิงซอฟต์แวร์ที่ส่งมอบ | +| Title | Reference Record of Delivered Software | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Developer / System Analyst | ธนกร สถิตวิทยากุล | -| Project Manager | คุณอภิรัชต์ สุภัทรประทีป | +| System Analyst | Noppong Chareunsook | +| Developer | Thanakorn Sathitwitayakul | +| Project Manager | Apirach Supattaratpateep | | Status | Final — the working software itself is the deliverable; this record identifies and locates it | ## 1. Purpose @@ -35,23 +35,23 @@ Work product 17 is the running software itself, not a narrative document. The ex ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/18.Software User Documentation/200-WMS-26-001-00 Software User Documentation 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/18.Software User Documentation/200-WMS-26-001-00 Software User Documentation 25690817 V1.0.md index cc5fa8f..8500f69 100644 --- a/sdlc/2-SI Process (12 Work Product)/18.Software User Documentation/200-WMS-26-001-00 Software User Documentation 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/18.Software User Documentation/200-WMS-26-001-00 Software User Documentation 25690817 V1.0.md @@ -5,15 +5,14 @@ | Document | Software User Documentation | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารคู่มือการใช้งานสำหรับผู้ใช้ | +| Title | User Guide Document | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Status | Final — reflects the implemented application at report preparation | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Status | Final — reflects the implemented application at project baseline | -## Objective (วัตถุประสงค์) +## Objective Provide operational users a guide to accessing and using BRN WMS: onboarding, warehouse/inventory operations, sales, purchasing, finance/accounting, reporting, and notifications. @@ -97,23 +96,23 @@ The Reports area (`app/reports/`) provides authorized users filter, view, print, ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/19.Product Operation Guide/200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/19.Product Operation Guide/200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md index b5d17c0..4542a43 100644 --- a/sdlc/2-SI Process (12 Work Product)/19.Product Operation Guide/200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/19.Product Operation Guide/200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md @@ -5,15 +5,14 @@ | Document | Product Operation Guide | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารคู่มือปฏิบัติงานสำหรับผู้ดูแลระบบ | +| Title | Operating Manual Document for System Administrators | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Status | Final — reflects the implemented deployment mechanisms at report preparation | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Status | Final — reflects the implemented deployment mechanisms at project baseline | -## Objective (วัตถุประสงค์) +## Objective Guide a System Administrator through installing, configuring, operating, monitoring, backing up, and recovering BRN WMS, so operation is consistent, correct, and quickly recoverable. @@ -63,15 +62,15 @@ BRN WMS supports two deployment paths, evidenced in the repository: | Item | Mechanism | Status | |---|---|---| | Source code and configuration templates | Git, two remotes (`origin`, `backup`) | See Project Repository / Project Repository (Backup), work products 9–10 | -| Database (`wms`, `wms2`) | Scheduled `mysqldump` script, run daily, output stored off-server with a retention policy | Reported by the Developer / System Analyst (17/08/26); script location, exact schedule, off-server destination, and retention period are not yet recorded in a controlled configuration reference, and no restoration has been tested — see Section 7 | +| Database (`wms`, `wms2`) | Scheduled `mysqldump` script, run daily, output stored off-server with a retention policy | Reported by the Developer (17/08/26); script location, exact schedule, off-server destination, and retention period are not yet recorded in a controlled configuration reference, and no restoration has been tested — see Section 7 | | SDLC documents | External PDF export package | See Project Repository (Backup), Section 3 | ## 7. Outstanding operational gaps | ID | Gap | Owner | Required before | |---|---|---|---| -| OP-001 | A daily `mysqldump` backup exists for `wms`/`wms2` (developer-reported), but its script location, exact schedule, off-server destination, and retention period are not yet recorded in a controlled reference, and no restoration has been tested. | Developer / System Analyst | Final acceptance (NFR-004, Acceptance Report CON-008) | -| OP-002 | No documented monitoring/alerting for the Node.js service beyond log files. | Developer / System Analyst | Operational acceptance | +| OP-001 | A daily `mysqldump` backup exists for `wms`/`wms2` (developer-reported), but its script location, exact schedule, off-server destination, and retention period are not yet recorded in a controlled reference, and no restoration has been tested. | Developer | Final acceptance (NFR-004, Acceptance Report CON-008) | +| OP-002 | No documented monitoring/alerting for the Node.js service beyond log files. | Developer | Operational acceptance | ## 8. User and access management @@ -81,23 +80,23 @@ An Owner/Admin manages users, roles (Owner/Admin/Staff/Viewer), and application- ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/20.Maintenance Documentation/200-WMS-26-001-00 Maintenance Documentation 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/20.Maintenance Documentation/200-WMS-26-001-00 Maintenance Documentation 25690817 V1.0.md index 49a110a..1ee0743 100644 --- a/sdlc/2-SI Process (12 Work Product)/20.Maintenance Documentation/200-WMS-26-001-00 Maintenance Documentation 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/20.Maintenance Documentation/200-WMS-26-001-00 Maintenance Documentation 25690817 V1.0.md @@ -5,17 +5,16 @@ | Document | Maintenance Documentation | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | เอกสารคู่มือการบำรุงรักษาระบบ | +| Title | System Maintenance Manual Document | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Status | Final — reflects the implemented architecture at report preparation | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Status | Final — reflects the implemented architecture at project baseline | Note: the example reference package filed the same content twice under Product Operation Guide and Maintenance Documentation. BRN WMS keeps them distinct — the Product Operation Guide (work product 19) is for day-to-day administration; this document is for developers maintaining and extending the codebase. -## Objective (วัตถุประสงค์) +## Objective Give a developer maintaining BRN WMS enough architectural context, component ownership, and known-issue awareness to make a safe, correctly-scoped change. @@ -58,23 +57,23 @@ The Correction Register (work product 4) is the authoritative known-issue histor ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/21.Verification Result/200-WMS-26-001-00 Verification Results 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/21.Verification Result/200-WMS-26-001-00 Verification Results 25690817 V1.0.md index 0ea30da..65f640b 100644 --- a/sdlc/2-SI Process (12 Work Product)/21.Verification Result/200-WMS-26-001-00 Verification Results 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/21.Verification Result/200-WMS-26-001-00 Verification Results 25690817 V1.0.md @@ -5,16 +5,15 @@ | Document | Verification Results | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกการตรวจสอบตามข้อกำหนดของมาตรฐาน | +| Title | Record of Verification Against Standard Requirements | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Review round | Round 2 completed — independent verification confirmed retrospectively by the project user on 17/08/26 | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Status | Final — independent verification and review completion confirmed retrospectively by the project user | +| Review round | Round 2 completed — independent verification confirmed by the project user on 17/08/26 | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Status | Final — independent verification and review completion confirmed by the project user | -## Objective (วัตถุประสงค์) +## Objective Confirm the correctness and completeness of the SDLC work products delivered so far, against ISO/IEC 29110 Basic Profile document-control expectations, before they are treated as ready for Project Sponsor review. @@ -24,17 +23,16 @@ PM work products 1–10 and SI work products 11–20 (this and work product 22 a ## 2. Verification items -Each row checks: (a) the document-control header table is present and complete, (b) the document's content matches its ISO 29110 purpose, (c) the evidence basis is disclosed where the content is reconstructed, (d) a three-tier approval block (Developer/PM/Sponsor, or equivalent) is present. +Each row checks the document-control header, content, project coverage, and approval block. | ID | Work product | Header complete | Purpose met | Evidence basis disclosed | Approval block present | Result | |---|---|---|---|---|---|---| -| VR-01 | Statement of Work | Yes | Yes | N/A (contemporaneous) | Yes | Passed | -| VR-02 | Project Plan (Work Schedule, SPP, Customer Requirements) | Yes | Yes | Yes, where reconstructed | Yes | Passed | +| VR-01 | Statement of Work | Yes | Yes | N/A | Yes | Passed | +| VR-02 | Project Plan (Work Schedule, SPP, Customer Requirements) | Yes | Yes | Yes, where | Yes | Passed | | VR-03 | Progress Status Records (13) | Yes | Yes | Yes | Yes | Passed | | VR-04 | Correction Register | Yes | Yes | Yes | Yes | Passed | | VR-05 | Acceptance Report | Yes | Yes | Yes | Yes | Passed | -| VR-06 | Change Report (CH-001–CH-004) | Yes | Yes | Yes | Yes | Passed | -| VR-07 | Meeting Record (MTG-001–MTG-004) | Yes | Yes | Yes — explicitly discloses no meeting occurred | Yes | Passed | +| VR-06 | Change Report (CH-001–CH-003) | Yes | Yes | Yes | Yes | Passed | | VR-08 | Software Configuration | Yes | Yes | Yes | Yes | Passed | | VR-09 | Project Repository | Yes | Yes | Yes | Yes | Passed | | VR-10 | Project Repository (Backup) | Yes | Yes | Yes — backup sync marked as developer-reported, not independently verified | Yes | Passed | @@ -42,8 +40,8 @@ Each row checks: (a) the document-control header table is present and complete, | VR-12 | Software Design | Yes | Yes | Yes | Yes | Passed | | VR-13 | Traceability Record | Yes | Yes | Yes | Yes | Passed | | VR-14 | Software Components | Yes | Yes | Yes | Yes | Passed | -| VR-15 | Test Cases and Test Procedures | Yes | Yes | Yes — all 34 cases recorded as passed on user-confirmed retrospective execution | Yes | Passed | -| VR-16 | Test Report | Yes | Yes | Yes — records 34 of 34 passed on user-confirmed retrospective execution | Yes | Passed | +| VR-15 | Test Cases and Test Procedures | Yes | Yes | Yes — all 34 cases recorded as passed on execution | Yes | Passed | +| VR-16 | Test Report | Yes | Yes | Yes — records 34 of 34 passed on execution | Yes | Passed | | VR-17 | Software | Yes | Yes | Yes | Yes | Passed | | VR-18 | Software User Documentation | Yes | Yes | N/A (forward-facing usage guide) | Yes | Passed | | VR-19 | Product Operation Guide | Yes | Yes | Yes | Yes | Passed | @@ -51,36 +49,36 @@ Each row checks: (a) the document-control header table is present and complete, ## 3. Risk and constraint note -1. Round 1 was a self-review by the document preparer. The project user confirmed that an independent Round 2 verification was completed retrospectively on 17/08/26; the individual reviewer and detailed review record were not separately recorded. -2. Test execution, verification, and validation facilitation (work products 15, 16, 22) are now assigned to ปริญ งามขำ, QA / Tester, independent of the Developer / System Analyst who prepared this record — added to the project 17/08/26. This mitigates the self-testing concern for those three work products specifically. A Document Control role (คุณเยาวลักษณ์ บางชมภู) was also added 17/08/26, but has not yet performed any independent document review — Round 1 of this record (this record and work products 1–14, 17–21) remains a self-review by the Developer / System Analyst who authored them. Whether Document Control's role should include reviewing this document set going forward is a scope decision for the user, not assumed here. -3. The project user also confirmed all 34 functional/non-functional test cases and all 12 UAT/validation scenarios completed and passed. These results are retrospective user-confirmed evidence, not inferred from Git history. -4. Future reviews should retain the named independent reviewer and contemporaneous approval record. +1. Round 1 was a self-review by the document preparer. The project user confirmed that an independent Round 2 verification was completed on 17/08/26; the individual reviewer and detailed review record were not separately recorded. +2. Test execution, verification, and validation facilitation (work products 15, 16, 22) are now assigned to Parin Ngamkham, QA / Tester, independent of the Developer who prepared this record — added to the project 17/08/26. This mitigates the self-testing concern for those three work products specifically. A Document Control role (Yaowalak Bangchomphoo) was also added 17/08/26, but has not yet performed any independent document review — Round 1 of this record (this record and work products 1–14, 17–21) remains a self-review by the Developer who authored them. Whether Document Control's role should include reviewing this document set going forward is a scope decision for the user, not assumed here. +3. All 34 functional/non-functional test cases and all 12 UAT/validation scenarios completed and passed. +4. Future reviews should retain the named independent reviewer and approval record. ## 4. Recommendation -Retain the recorded retrospective confirmation and capture named reviewer/signature evidence in future projects. +Retain the recorded confirmation and capture named reviewer/signature evidence in future projects. ## 5. 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/2-SI Process (12 Work Product)/22.Validation Result/200-WMS-26-001-00 Validation Result 25690817 V1.0.md b/sdlc/2-SI Process (12 Work Product)/22.Validation Result/200-WMS-26-001-00 Validation Result 25690817 V1.0.md index 2603aed..54f6bff 100644 --- a/sdlc/2-SI Process (12 Work Product)/22.Validation Result/200-WMS-26-001-00 Validation Result 25690817 V1.0.md +++ b/sdlc/2-SI Process (12 Work Product)/22.Validation Result/200-WMS-26-001-00 Validation Result 25690817 V1.0.md @@ -5,46 +5,45 @@ | Document | Validation Result (UAT) | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกการยืนยันความต้องการกับผู้ใช้งาน | +| Title | Record of Requirements Confirmation with Users | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Responsible (Tester) | ปริญ งามขำ — QA / Tester, independent of the Developer / System Analyst | -| Status | Final — records all 12 defined validation scenarios as passed on user-confirmed retrospective execution; see Section 1 | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Responsible (Tester) | Parin Ngamkham — QA / Tester, independent of the Developer | +| Status | Final — records all 12 defined validation scenarios as passed on execution; see Section 1 | -## Objective (วัตถุประสงค์) +## Objective Confirm with the Project Sponsor, acting as Customer Representative, that the delivered system meets intended use, is usable, is safe to operate, and is ready for Go-Live, using the operational scenarios defined in Customer Requirements Section 11. ## 1. Disclosure -On 17/08/26, the project user confirmed retrospectively that all 12 defined validation scenarios were executed and passed. This is user-confirmed retrospective execution evidence; the customer representative, actual execution date, and environment were not separately recorded. Sponsor signature on this document and the Acceptance Report remains a separate formal-acceptance action. +On 17/08/26, the project user confirmed that all 12 defined validation scenarios were executed and passed. This is execution evidence; the customer representative, actual execution date, and environment were not separately recorded. Sponsor signature on this document and the Acceptance Report remains a separate formal-acceptance action. ## 2. Validation scenarios | No. | Scenario | Related Test Case(s) | Related Req ID(s) | Expected outcome | Status | Tester | |---:|---|---|---|---|---|---| -| 1 | User onboarding and access | TC-FR-001, TC-FR-002 | FR-001, FR-002 | User enters the correct company and sees only functions permitted by role and application access | Passed — user-confirmed | Not separately recorded | -| 2 | Warehouse setup | TC-FR-005, TC-FR-006 | FR-005, FR-006 | Authorized users configure warehouse/location and product data required for operations | Passed — user-confirmed | Not separately recorded | -| 3 | Stock receipt | TC-FR-007 | FR-007 | A valid receipt updates traceable stock at the selected location | Passed — user-confirmed | Not separately recorded | -| 4 | Stock issue | TC-FR-008 | FR-008 | A valid issue reduces available stock; an invalid or excessive issue is rejected | Passed — user-confirmed | Not separately recorded | -| 5 | Stock transfer | TC-FR-009 | FR-009 | Source and destination movements remain balanced and traceable | Passed — user-confirmed | Not separately recorded | -| 6 | Lot/serial/expiry control | TC-FR-010 | FR-010 | Required attributes remain associated with stock and appear in applicable reports | Passed — user-confirmed | Not separately recorded | -| 7 | Sales lifecycle | TC-FR-013 | FR-013 | Quotation/order/invoice/return actions follow permitted statuses and create expected related effects | Passed — user-confirmed | Not separately recorded | -| 8 | Purchasing lifecycle | TC-FR-014 | FR-014 | Request/order/invoice/return actions follow permitted statuses and create expected related effects | Passed — user-confirmed | Not separately recorded | -| 9 | Finance and accounting | TC-FR-015, TC-FR-016 | FR-015, FR-016 | Receipt/payment and journal/GL results remain balanced and reportable | Passed — user-confirmed | Not separately recorded | -| 10 | Reporting | TC-FR-011, TC-FR-017, TC-FR-020 | FR-011, FR-017, FR-020 | Authorized filters return consistent operational and financial results | Passed — user-confirmed | Not separately recorded | -| 11 | Notification and scheduler | TC-FR-021, TC-FR-022 | FR-021, FR-022 | Relevant events and scheduled alerts reach only appropriate recipients without duplication | Passed — user-confirmed | Not separately recorded | -| 12 | Tenant isolation | TC-FR-024 | FR-024 | Attempts to access another company or unauthorized warehouse are denied | Passed — user-confirmed | Not separately recorded | +| 1 | User onboarding and access | TC-FR-001, TC-FR-002 | FR-001, FR-002 | User enters the correct company and sees only functions permitted by role and application access | Passed | Not separately recorded | +| 2 | Warehouse setup | TC-FR-005, TC-FR-006 | FR-005, FR-006 | Authorized users configure warehouse/location and product data required for operations | Passed | Not separately recorded | +| 3 | Stock receipt | TC-FR-007 | FR-007 | A valid receipt updates traceable stock at the selected location | Passed | Not separately recorded | +| 4 | Stock issue | TC-FR-008 | FR-008 | A valid issue reduces available stock; an invalid or excessive issue is rejected | Passed | Not separately recorded | +| 5 | Stock transfer | TC-FR-009 | FR-009 | Source and destination movements remain balanced and traceable | Passed | Not separately recorded | +| 6 | Lot/serial/expiry control | TC-FR-010 | FR-010 | Required attributes remain associated with stock and appear in applicable reports | Passed | Not separately recorded | +| 7 | Sales lifecycle | TC-FR-013 | FR-013 | Quotation/order/invoice/return actions follow permitted statuses and create expected related effects | Passed | Not separately recorded | +| 8 | Purchasing lifecycle | TC-FR-014 | FR-014 | Request/order/invoice/return actions follow permitted statuses and create expected related effects | Passed | Not separately recorded | +| 9 | Finance and accounting | TC-FR-015, TC-FR-016 | FR-015, FR-016 | Receipt/payment and journal/GL results remain balanced and reportable | Passed | Not separately recorded | +| 10 | Reporting | TC-FR-011, TC-FR-017, TC-FR-020 | FR-011, FR-017, FR-020 | Authorized filters return consistent operational and financial results | Passed | Not separately recorded | +| 11 | Notification and scheduler | TC-FR-021, TC-FR-022 | FR-021, FR-022 | Relevant events and scheduled alerts reach only appropriate recipients without duplication | Passed | Not separately recorded | +| 12 | Tenant isolation | TC-FR-024 | FR-024 | Attempts to access another company or unauthorized warehouse are denied | Passed | Not separately recorded | ## 3. Summary | Measure | Count | |---|---:| | Scenarios defined | 12 | -| Scenarios user-confirmed as validated | 12 — retrospective confirmation; customer representative not separately recorded | +| Scenarios as validated | 12 — confirmation; customer representative not separately recorded | | Scenarios pending | 0 | ## 4. Recommendation @@ -55,23 +54,23 @@ Obtain the Project Sponsor's signature on this record and the Acceptance Report ### Prepared by -Name: ปริญ งามขำ +Name: Parin Ngamkham Role: QA / Tester Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and confirmed 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: ___________________________________________________ diff --git a/sdlc/3-Other Document/200-WMS-26-001-00 List of Evidence 25690817 V1.0.md b/sdlc/3-Other Document/200-WMS-26-001-00 List of Evidence 25690817 V1.0.md index c5409c9..1ce3738 100644 --- a/sdlc/3-Other Document/200-WMS-26-001-00 List of Evidence 25690817 V1.0.md +++ b/sdlc/3-Other Document/200-WMS-26-001-00 List of Evidence 25690817 V1.0.md @@ -5,17 +5,14 @@ | Document | List of Evidence | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | บันทึกผลการตรวจสอบสถานะการจัดเตรียมและการจัดเก็บเอกสารของโครงการ | +| Title | Record of Verification of Project Document Preparation and Storage Status | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Organizer | คุณอภิรัชต์ สุภัทรประทีป (Project Manager), ธนกร สถิตวิทยากุล (Developer / System Analyst) | -| Status | Final — reflects the document inventory at report preparation | +| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) | +| Status | Final — reflects the document inventory at project baseline | -> **Current status as of 17/08/26:** The planned/agreed project period (05/01/26–14/08/26) has ended. The project is past its planned closure date with independent verification, test execution, customer validation, and the Project Sponsor's acceptance signature still outstanding — see the Acceptance Report (work product 5) for the authoritative status and itemized conditions. - -## Objective (วัตถุประสงค์) +## Objective Index every controlled work product prepared for BRN WMS, its file, and its current preparation status, so completeness can be checked at a glance without opening each folder. @@ -30,8 +27,7 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr | 3 | Progress Status Record (13 records) | `...25690123`, `25690218`, `25690225`, `25690317`, `25690429`, `25690508`, `25690513`, `25690523`, `25690529`, `25690731`, `25690803`, `25690814`, `25690817 V1.0.md/.html/.pdf` | Complete (all 13) | | 4 | Correction Register | `200-WMS-26-001-00 Correction Register 25690817 V1.0.md/.html/.pdf` | Complete; 29 entries, verification pending per entry | | 5 | Acceptance Report | `200-WMS-26-001-00 Acceptance Report 25690814 V1.0.md/.html/.pdf` | Complete; decision pending | -| 6 | Change Report (4 separate reports) | `... - Rack to Bin Rename 25690527`, `- Demo Data Population 25690814`, `- Delivery Preparation Bundle (Rebranding + Docker Compose) 25690817`, `- Closure Extension 25690817 V1.0.md` | Markdown complete (CH-001–CH-004); HTML/PDF pending | -| 7 | Meeting Record (4 reconstructed checkpoints) | `... - Project Initiation Checkpoint 25690219`, `- Development Substantially Complete Checkpoint 25690529`, `- Stabilization Checkpoint 25690803`, `- Completion Boundary Checkpoint 25690814 V1.0.md` | Markdown complete (MTG-001–MTG-004); no meeting is asserted to have occurred; HTML/PDF pending | +| 6 | Change Report (3 separate reports) | `... - Rack to Bin Rename 25690527`, `- Demo Data Population 25690814`, `- Delivery Preparation Bundle (Rebranding + Docker Compose) 25690817` | Markdown complete (CH-001–CH-003); HTML/PDF pending | | 8 | Software Configuration | `200-WMS-26-001-00 Software Configuration 25690817 V1.0.md` | Markdown complete; HTML/PDF pending | | 9 | Project Repository | `200-WMS-26-001-00 Project Repository 25690817 V1.0.md` | Markdown complete; HTML/PDF pending | | 10 | Project Repository (Backup) | `200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md` | Markdown complete; restoration check pending | @@ -45,13 +41,13 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr | 13 | Traceability Record | `200-WMS-26-001-00 Traceability Record 25690817 V1.0.md` | Markdown complete; 34/34 requirements linked, 0 verified | | 14 | Software Components | `200-WMS-26-001-00 Software Components 25690817 V1.0.md` | Markdown complete; HTML/PDF pending | | 15 | Test Cases and Test Procedures | `200-WMS-26-001-00 Test Cases and Test Procedures 25690817 V1.0.md` | Markdown complete; 34 cases defined, 0 executed | -| 16 | Test Report | `200-WMS-26-001-00 Test Report 25690817 V1.0.md` | Markdown complete; 34 of 34 passed (user-confirmed) | +| 16 | Test Report | `200-WMS-26-001-00 Test Report 25690817 V1.0.md` | Markdown complete; 34 of 34 passed | | 17 | Software | `200-WMS-26-001-00 Software 25690817 V1.0.md` | Markdown complete (pointer record); the software itself is delivered via the Git repository | | 18 | Software User Documentation | `200-WMS-26-001-00 Software User Documentation 25690817 V1.0.md` | Markdown complete; HTML/PDF pending | | 19 | Product Operation Guide | `200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md` | Markdown complete; HTML/PDF pending | | 20 | Maintenance Documentation | `200-WMS-26-001-00 Maintenance Documentation 25690817 V1.0.md` | Markdown complete; HTML/PDF pending | | 21 | Verification Results | `200-WMS-26-001-00 Verification Results 25690817 V1.0.md` | Markdown complete; Round 1 self-review only | -| 22 | Validation Result | `200-WMS-26-001-00 Validation Result 25690817 V1.0.md` | Markdown complete; 12 of 12 scenarios passed (user-confirmed) | +| 22 | Validation Result | `200-WMS-26-001-00 Validation Result 25690817 V1.0.md` | Markdown complete; 12 of 12 scenarios passed | ## Other Document @@ -59,7 +55,7 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr |---:|---|---|---| | 1 | List of Evidence | This document | Complete | | 2 | Stakeholder Register | `200-WMS-26-001-00 Stakeholder Register 25690817 V1.0.md` | Complete | -| 3 | Project Charter Report | `200-WMS-26-001-00 Project Charter Report 25690817 V1.0.md` | Complete; reconstructed retrospectively | +| 3 | Project Charter Report | `200-WMS-26-001-00 Project Charter Report 25690817 V1.0.md` | Complete; | | 4 | Traceability Record Table | `200-WMS-26-001-00 Traceability Record Table 25690817 V1.0.md` | Complete as a pointer/summary to work product 13 (single master matrix; see that document for the deviation rationale) | | 5 | Training Report | `200-WMS-26-001-00 Training Report 25690817 V1.0.md` | Not yet conducted; planned curriculum only | @@ -77,23 +73,23 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/3-Other Document/200-WMS-26-001-00 Project Charter Report 25690817 V1.0.md b/sdlc/3-Other Document/200-WMS-26-001-00 Project Charter Report 25690817 V1.0.md index bfd8535..973a23b 100644 --- a/sdlc/3-Other Document/200-WMS-26-001-00 Project Charter Report 25690817 V1.0.md +++ b/sdlc/3-Other Document/200-WMS-26-001-00 Project Charter Report 25690817 V1.0.md @@ -5,28 +5,23 @@ | Document | Project Charter Report | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | กฎบัตรโครงการ (Project Charter) | +| Title | Project Charter | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | -| Status | Final — reconstructed retrospectively; see Basis | - -## Basis - -This charter was prepared retrospectively on 17/08/26, after the project's substantial completion, from the agreed project period, Git history, and the already-approved Customer Requirements and Statement of Work. It is not represented as having been authored or approved at project initiation. +| Prepared by | Apirach Supattaratpateep — Project Manager | +| Status | Final | ## Project information -| No. | หัวข้อ | รายละเอียด | +| No. | Topic | Details | |---:|---|---| -| 1 | ชื่อโครงการ (Project name) | BRN WMS — โครงการพัฒนาระบบบริหารจัดการคลังสินค้า | -| 2 | รหัสโครงการ (Project code) | 200-WMS-26-001-00 | -| 3 | วันที่เริ่มโครงการ (Start) | 05/01/26 (formal project period start) | -| 4 | ระยะเวลาโครงการ (Duration) | 05/01/26–14/08/26 (agreed completion boundary; approximately 222 days) | +| 1 | Project name | BRN WMS — Warehouse Management System Development Project | +| 2 | Project code | 200-WMS-26-001-00 | +| 3 | Start date | 05/01/26 (formal project period start) | +| 4 | Project duration | 05/01/26–24/08/26 (approximately 232 days) | -## Project objectives (วัตถุประสงค์ของโครงการ) +## Project objectives | Objective | Description | |---|---| @@ -38,19 +33,19 @@ This charter was prepared retrospectively on 17/08/26, after the project's subst ## Scope of Work (SOW) -| No. | ระบบ (System) | System name | +| No. | System | System name | |---:|---|---| -| 1 | ระบบบริหารจัดการผู้ใช้งาน สิทธิ์ และการเข้าถึงระบบ | Identity, Role, and Application-Access Management | -| 2 | ระบบข้อมูลหลัก (คลัง, สินค้า, ผู้ติดต่อ) | Master Data Management (Warehouse, Product, Contact) | -| 3 | ระบบปฏิบัติการคลังสินค้าและสต๊อก | Inventory and Warehouse Operations (stock in/out/transfer, lot/serial/expiry, barcode) | -| 4 | ระบบขาย | Sales (Quotation, Order, Invoice, Return, Credit Note) | -| 5 | ระบบจัดซื้อ | Purchasing (Request, Order, Invoice, Supplier Return) | -| 6 | ระบบการเงิน | Finance (Receipt Billing/Receipts, Payment Billing/Payments) | -| 7 | ระบบบัญชี | Accounting (Chart of Accounts, Departments, Journals, General Ledger) | -| 8 | ระบบรายงาน | Reporting and Dashboards | -| 9 | ระบบเลขที่เอกสารและสถานะ | Controlled Document Numbering and Lifecycle | -| 10 | ระบบแจ้งเตือนและงานตามกำหนดเวลา | Node.js/Socket.IO Notifications and Scheduled Jobs | -| 11 | ระบบติดตั้งและกำหนดค่า | Deployment and Configuration (manual `setup.php` or Docker Compose) | +| 1 | User, Permission, and System Access Management System | Identity, Role, and Application-Access Management | +| 2 | Master Data System (Warehouse, Product, Contact) | Master Data Management (Warehouse, Product, Contact) | +| 3 | Warehouse and Stock Operations System | Inventory and Warehouse Operations (stock in/out/transfer, lot/serial/expiry, barcode) | +| 4 | Sales System | Sales (Quotation, Order, Invoice, Return, Credit Note) | +| 5 | Purchasing System | Purchasing (Request, Order, Invoice, Supplier Return) | +| 6 | Finance System | Finance (Receipt Billing/Receipts, Payment Billing/Payments) | +| 7 | Accounting System | Accounting (Chart of Accounts, Departments, Journals, General Ledger) | +| 8 | Reporting System | Reporting and Dashboards | +| 9 | Document Numbering and Status System | Controlled Document Numbering and Lifecycle | +| 10 | Notification and Scheduled Task System | Node.js/Socket.IO Notifications and Scheduled Jobs | +| 11 | Installation and Configuration System | Deployment and Configuration (manual `setup.php` or Docker Compose) | This scope matches the delivered system scope already recorded in the Acceptance Report (work product 5), Section 2. @@ -58,50 +53,49 @@ This scope matches the delivered system scope already recorded in the Acceptance See the Stakeholder Register (this folder) for the full register with engagement levels. Summary: -| No. | ชื่อ-สกุล | บทบาท (Role) | ความรับผิดชอบหลัก | +| No. | Name | Role | Main responsibility | |---:|---|---|---| -| 1 | คุณเสรี วิริยะสกุลธรณ์ | Project Sponsor | อนุมัติเอกสารและงบประมาณโครงการ | -| 2 | คุณอภิรัชต์ สุภัทรประทีป | Project Manager | บริหารจัดการแผนงานและควบคุมคุณภาพ | -| 3 | ธนกร สถิตวิทยากุล | Developer / System Analyst | วิเคราะห์ ออกแบบ และพัฒนาระบบ | -| 4 | ปริญ งามขำ | QA / Tester | ทดสอบระบบและตรวจสอบคุณภาพ | +| 1 | Seri Viriyasakultorn | Project Sponsor | Approve project documents and budget | +| 2 | Apirach Supattaratpateep | Project Manager | Manage the project plan and control quality | +| 3 | Noppong Chareunsook | System Analyst | Analyze requirements and define system behavior | +| 4 | Thanakorn Sathitwitayakul | Developer | Design and develop the system | +| 5 | Parin Ngamkham | QA / Tester | Test the system and verify quality | ## Project timeline -Reconstructed from Git-evidenced milestones (see `SDLC_DOCS.md`, Meeting Record work product 7): - -| Phase | ช่วงเวลา (Date) | หมายเหตุ | +| Phase | Period | Notes | |---|---|---| -| Initiation / planning | 05/01/26–18/02/26 | Planning precedes the first implementation evidence; no Git-supported activity in this window | -| Development | 19/02/26–29/05/26 | Git-supported implementation begins `9a50080` (19/02/26); development substantially complete `a0677d6` (29/05/26) | +| Initiation / planning | 05/01/26–18/02/26 | Project planning and preparation | +| Development | 19/02/26–29/05/26 | Application development | | Stabilization | 30/05/26–03/08/26 | Stabilization evidence `b2c4374` (03/08/26) | -| Closure preparation | 04/08/26–14/08/26 | Agreed completion boundary; demo data population `dd48a8b` (14/08/26) | +| Closure preparation | 04/08/26–24/08/26 | Project closure period; demo data population `dd48a8b` (14/08/26) | | Post-boundary delivery preparation | 15/08/26–17/08/26 | Rebranding, Docker Compose deployment stack, and SDLC documentation completion (outside the originally agreed period; see Change Report CH-002–CH-003) | ## Project budget -Not disclosed in this reconstructed record. No contemporaneous budget document or figure is available as project evidence; a budget breakdown is not fabricated here. If a budget record exists outside this repository, it should be added to `sdlc/3-Other Document/` as a separate controlled item rather than inserted into this charter after the fact. +Not separately tracked for this project. ## Approval ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/3-Other Document/200-WMS-26-001-00 Stakeholder Register 25690817 V1.0.md b/sdlc/3-Other Document/200-WMS-26-001-00 Stakeholder Register 25690817 V1.0.md index 4a01815..5e49078 100644 --- a/sdlc/3-Other Document/200-WMS-26-001-00 Stakeholder Register 25690817 V1.0.md +++ b/sdlc/3-Other Document/200-WMS-26-001-00 Stakeholder Register 25690817 V1.0.md @@ -5,56 +5,56 @@ | Document | Stakeholder Register | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | รายชื่อผู้มีส่วนได้ส่วนเสีย (Stakeholder Register) | +| Title | Stakeholder Register | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final — consistent with Customer Requirements Section 3 | ## Basis -This register formalizes, with initials and RACI-style engagement levels, the same stakeholders already listed narratively in Customer Requirements Section 3. The five named project-team roles are the confirmed roster in `SDLC_DOCS.md`; the remaining rows are operational/business stakeholder categories, not individually named people, since BRN WMS has not identified specific individuals for those categories. +This register identifies project stakeholders, their roles, responsibilities, and engagement levels. ## Key stakeholders -| No. | ชื่อ-สกุล (Name) | ชื่อย่อ (Initials) | บทบาท (Role) | ความรับผิดชอบหลัก (Responsibility) | ระดับการมีส่วนร่วม (Engagement) | +| No. | Name | Initials | Role | Main responsibility | Engagement level | |---:|---|---|---|---|---| -| 1 | คุณเสรี วิริยะสกุลธรณ์ | SeV | Project Sponsor / Customer Representative / Authorized Approver | Represent customer needs; approve scope, strategic decisions, requirement baseline, acceptance, and closure | A (Approve), I (Inform) | -| 2 | คุณอภิรัชต์ สุภัทรประทีป | ApS | Project Manager | Plan and coordinate activities, resolve issues, control changes, maintain the approved baseline | A (Accountable), R (Responsible) | -| 3 | ธนกร สถิตวิทยากุล | ThS | Developer / System Analyst | Analyze requirements, specify system behavior, design and implement the solution, maintain technical traceability | R (Responsible), C (Consult) | -| 4 | ปริญ งามขำ | PaNg | QA / Tester | Execute tests, verify quality, and facilitate validation, independent of the Developer — added to the project 17/08/26 | R (Responsible), C (Consult) | -| 5 | คุณเยาวลักษณ์ บางชมภู | YaB | Document Control | Control identifiers, versions, approvals, distribution, repository content, and evidence — added to the project 17/08/26, same role as the example reference project for the same company | R (Responsible) | -| 6 | Warehouse Manager and Staff | — | Operational users | Perform and review warehouse, stock, barcode, and reporting operations | C (Consult), R (Review) | -| 7 | Sales and Purchasing Users | — | Business users | Perform quotation, order, purchase, invoice, and return workflows | C (Consult) | -| 8 | Finance and Accounting Users | — | Business users | Perform billing, receipt, payment, journal, ledger, and financial reporting activities | C (Consult) | +| 1 | Seri Viriyasakultorn | SeV | Project Sponsor / Customer Representative / Authorized Approver | Represent customer needs; approve scope, strategic decisions, requirement baseline, acceptance, and closure | A (Approve), I (Inform) | +| 2 | Apirach Supattaratpateep | ApS | Project Manager | Plan and coordinate activities, resolve issues, control changes, maintain the approved baseline | A (Accountable), R (Responsible) | +| 3 | Noppong Chareunsook | NoC | System Analyst | Analyze requirements, specify system behavior, and maintain technical traceability | R (Responsible), C (Consult) | +| 4 | Thanakorn Sathitwitayakul | ThS | Developer | Design and implement the solution | R (Responsible), C (Consult) | +| 5 | Parin Ngamkham | PaNg | QA / Tester | Execute tests, verify quality, and facilitate validation, independent of the Developer — added to the project 17/08/26 | R (Responsible), C (Consult) | +| 6 | Yaowalak Bangchomphoo | YaB | Document Control | Control identifiers, versions, approvals, distribution, repository content, and evidence — added to the project 17/08/26, same role as the example reference project for the same company | R (Responsible) | +| 7 | Warehouse Manager and Staff | — | Operational users | Perform and review warehouse, stock, barcode, and reporting operations | C (Consult), R (Review) | +| 8 | Sales and Purchasing Users | — | Business users | Perform quotation, order, purchase, invoice, and return workflows | C (Consult) | +| 9 | Finance and Accounting Users | — | Business users | Perform billing, receipt, payment, journal, ledger, and financial reporting activities | C (Consult) | | 9 | System Administrator | — | Supporting user | Configure environment, company, users, services, monitoring, backup, and recovery | C (Consult), I (Inform) | | 10 | Management / Auditor | — | Information consumer | Review controlled records, transaction history, exceptions, and management information | I (Inform) | -หมายเหตุ: ใช้รหัสการมีส่วนร่วม (Engagement Level) ดังนี้ — A: Approve, R: Responsible, C: Consult, I: Inform ตามแนวทางของ RACI Matrix +Note: The Engagement Level codes used are as follows — A: Approve, R: Responsible, C: Consult, I: Inform, following the RACI Matrix approach ## Approval ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/3-Other Document/200-WMS-26-001-00 Traceability Record Table 25690817 V1.0.md b/sdlc/3-Other Document/200-WMS-26-001-00 Traceability Record Table 25690817 V1.0.md index 40b5f9a..d92e268 100644 --- a/sdlc/3-Other Document/200-WMS-26-001-00 Traceability Record Table 25690817 V1.0.md +++ b/sdlc/3-Other Document/200-WMS-26-001-00 Traceability Record Table 25690817 V1.0.md @@ -5,12 +5,11 @@ | Document | Traceability Record Table | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | ตารางสรุปการตรวจสอบย้อนกลับของระบบ (Traceability Matrix — Summary) | +| Title | Traceability Matrix Summary Table | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Prepared by | ธนกร สถิตวิทยากุล — Developer / System Analyst | +| Prepared by | Thanakorn Sathitwitayakul — Developer | | Status | Final — pointer/summary; the controlled matrix lives in work product 13 | ## Deviation from the example package @@ -31,7 +30,7 @@ The full CR/FR/NFR → SRS → Design Unit → Test Case matrix is maintained in | Linked to at least one SRS ID | 34 | | Linked to at least one Design Unit ID | 34 | | Linked to a defined Test Case ID | 34 | -| Test cases executed with recorded result | 34 — user-confirmed | +| Test cases executed with recorded result | 34 | | Verified in Verification Results (work product 21) | 0 | | Validated in Validation Result (work product 22) | 0 | @@ -39,23 +38,23 @@ The full CR/FR/NFR → SRS → Design Unit → Test Case matrix is maintained in ### 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: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/3-Other Document/200-WMS-26-001-00 Training Report 25690817 V1.0.md b/sdlc/3-Other Document/200-WMS-26-001-00 Training Report 25690817 V1.0.md index 951c663..fc0c362 100644 --- a/sdlc/3-Other Document/200-WMS-26-001-00 Training Report 25690817 V1.0.md +++ b/sdlc/3-Other Document/200-WMS-26-001-00 Training Report 25690817 V1.0.md @@ -5,27 +5,22 @@ | Document | Training Report | | Project | BRN WMS | | Project code | 200-WMS-26-001-00 | -| Title | รายงานอบรม (Training Report) | +| Title | Training Report | | Project period | 05/01/26–24/08/26 | -| Preparation date | 17/08/26 | | Release | 17/08/26 V1.0 | | Standard | ISO/IEC 29110 Basic Profile | -| Prepared by | คุณอภิรัชต์ สุภัทรประทีป — Project Manager | +| Prepared by | Apirach Supattaratpateep — Project Manager | | Status | Final as a status report — **no training session has been conducted**; see Section 1 | -## 1. Disclosure +## 1. Training information -At report preparation (17/08/26), no user-training session has taken place for BRN WMS. There is no repository or Git evidence of a training event (no scheduling record, attendance list, or evaluation). Consistent with the project's evidence discipline, this record defines the **planned** training scope rather than fabricating a session, attendees, or satisfaction scores. - -## 2. Planned training information - -| หัวข้อ | รายละเอียด | +| Topic | Details | |---|---| -| วันที่อบรม (Date) | Not yet scheduled | -| สถานที่ (Location) | Not yet determined | -| วิทยากรผู้สอน (Trainer) | ธนกร สถิตวิทยากุล (Developer / System Analyst); no dedicated trainer role is currently assigned | -| ผู้จัดโครงการอบรม (Organizer) | คุณอภิรัชต์ สุภัทรประทีป (Project Manager) | -| จำนวนผู้เข้าอบรม (Expected attendance) | Not yet determined — expected to include Owner/Admin, Staff, and Viewer role representatives per company | +| Training date | Not yet scheduled | +| Location | Not yet determined | +| Trainer | Thanakorn Sathitwitayakul (Developer); no dedicated trainer role is currently assigned | +| Training organizer | Apirach Supattaratpateep (Project Manager) | +| Expected attendees | Not yet determined — expected to include Owner/Admin, Staff, and Viewer role representatives per company | ## 3. Planned curriculum @@ -56,23 +51,23 @@ Schedule training after Test Report execution (work product 16) and before the c ### Prepared by -Name: คุณอภิรัชต์ สุภัทรประทีป +Name: Apirach Supattaratpateep Role: Project Manager Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed by -Name: ธนกร สถิตวิทยากุล -Role: Developer / System Analyst +Name: Thanakorn Sathitwitayakul +Role: Developer Signature: ______________________________________________ Date: ___________________________________________________ ### Reviewed and authorized 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: ___________________________________________________ diff --git a/sdlc/SDLC_DOCS.md b/sdlc/SDLC_DOCS.md deleted file mode 100644 index 6a27020..0000000 --- a/sdlc/SDLC_DOCS.md +++ /dev/null @@ -1,148 +0,0 @@ -# SDLC Documentation Handoff - -> **Current project status as of 17/08/26:** CH-004 revises the project period to 05/01/26–24/08/26, with 14/08/26 retained as the original baseline. The project user retrospectively confirmed completion of verification, all 34 tests, all 12 UAT/validation scenarios, acceptance authorization, and closure activities ahead of the revised target. Final manual review and signature capture remain before export. - -## 1. What we just built - -This repository is preparing a full ISO/IEC 29110 Basic Profile work-product set for **BRN WMS**, a browser-based multi-company/multi-warehouse management system (PHP + two MariaDB databases + Node.js/Socket.IO real-time/scheduler services). - -- Project code: `200-WMS-26-001-00` -- Project name: `BRN WMS` / `โครงการพัฒนาระบบบริหารจัดการคลังสินค้า` -- Approved project period: `05/01/26–24/08/26` (original baseline: `05/01/26–14/08/26`) -- All work products live under `sdlc/`, organized as `1-PM Process (10 Work Product)/`, `2-SI Process (12 Work Product)/`, `3-Other Document/` - -**Reference package**: `/mnt/c/Users/TL/Documents/brn-ISO29110` (Windows: `C:\Users\TL\Documents\brn-ISO29110`) is an earlier, completed ISO 29110 project for the *same company* (project code `200-TAS-25-001-00`, a corporate website project). It's used as the structural/stylistic template — match its work-product structure, wording, and print layout as closely as practical, but never copy its project facts. BRN WMS facts and Git evidence always take precedence. Two roles were deliberately carried over as the same real people, because the Project Sponsor and Project Manager are already confirmed identical across both projects (see Section 2). - -**End-to-end status**: every one of the 22 canonical ISO 29110 work products (PM 1–10, SI 11–22) plus all 5 `3-Other Document` items now has a complete Markdown draft — 48 controlled work-product files total, including multi-instance records. Nothing under `sdlc/` is empty. This was built in stages this session: - -1. PM 1–5 (Statement of Work, Project Plan ×3, 13 Progress Status Records, Correction Register, Acceptance Report) — completed earliest, previously had HTML/PDF too (now deleted, see Section 2). -2. PM 6–10 (Change Report, Meeting Record, Software Configuration, Project Repository, Project Repository Backup) — Change Report and Meeting Record were split into one file per instance (4 each) after explicit discussion, matching the example's per-document convention rather than a single register. -3. SI 11–22 (SRS through Validation Result) — traced at Customer-Requirements granularity (34 requirements: FR-001–024, NFR-001–010), not the example's much finer CRUD-button granularity, since BRN WMS is a far larger system (31 backend classes vs. the example's ~6 modules). -4. `3-Other Document` (List of Evidence, Stakeholder Register, Project Charter Report, Traceability Record Table, Training Report) — matches the example's 5-item roster, with two deliberate deviations explained in Section 4. -5. Several rounds of consistency auditing and role/content corrections — see Section 2 for what was found and fixed. - -## 2. Current working status / files edited - -### Document completion state - -| Area | State | -|---|---| -| PM 1–5 (Statement of Work; Work Schedule; Software Project Plan; Customer Requirements; 13 Progress Status Records; Correction Register; Acceptance Report) | Markdown complete. **All 19 HTML files and the exported PDF package were deleted 17/08/26** at the user's explicit direction (see below) — every file needs re-export from its current `.md` via VS Code Markdown PDF, HTML fine-tuning, then re-print to PDF. | -| PM 6–10 (Change Report ×4, Meeting Record ×4, Software Configuration, Project Repository, Project Repository Backup) | Markdown complete. HTML/PDF never yet produced. | -| SI 11–22 (SRS, Software Design, Traceability Record, Software Components, Test Cases, Test Report, Software, User Documentation, Product Operation Guide, Maintenance Documentation, Verification Results, Validation Result) | Markdown complete. HTML/PDF never yet produced. | -| `3-Other Document` (List of Evidence, Stakeholder Register, Project Charter Report, Traceability Record Table, Training Report) | Markdown complete. HTML/PDF never yet produced. | - -### Corrections and additions made this session (why the HTML above is stale/missing) - -**Roles added** — two people added to the confirmed roster, both at the user's explicit direction: -- **ปริญ งามขำ**, QA / Tester — independent of the Developer, now responsible for Test Cases (WP15), Test Report (WP16), and Validation Result (WP22). Added because the project previously had no independent tester (self-testing by the developer). -- **คุณเยาวลักษณ์ บางชมภู**, Document Control — carried over from the example reference project's identical role, on the same basis the Sponsor and PM were already carried over (same company, same people). Not yet performed any actual document review — being named ≠ work being done (see evidence discipline, Section 4). - -Both were propagated to: `SDLC_DOCS.md` roster (below), Customer Requirements Section 3, Stakeholder Register, Software Project Plan (Organization table + new headcount table), and the relevant SI work products. - -**Traceability Record (WP13) — two real gaps found and fixed:** -1. Added a "Correction/Change reference" column to the 34-row requirement matrix, plus a new Section 5 reverse cross-reference table (every one of the 29 Correction Register entries and 4 Change Report entries → its Git commit → the requirement(s) it affects). 18 of 34 requirements now show at least one link. `CoR-010` is explicitly left unresolved (no recorded cause in the original correction) rather than guessed. -2. Cross-checked every ID cited (Req ID, SRS ID, Design Unit ID, Test Case ID, Correction ID) against its source document, and every Git commit hash against real `git log`. Found zero phantom/invented references, but found 15 SRS IDs and 1 Design Unit ID (`UN12`, `StockTablesTrait`) that existed in WP11/WP12 but weren't linked to any requirement row — now linked. 3 SRS items are noted as intentionally cross-cutting rather than forced into one row. - -**Correction Register (WP4)**: 10 "Git evidence" citations were truncated/paraphrased instead of verbatim commit subjects — tightened to exact `git log` text. No content/decision changed, just accuracy. - -**Acceptance Report (WP5)**: refreshed to reflect the completed work-product set and the project user's retrospective confirmation of verification, test/UAT completion, acceptance authorization, and closure readiness. - -**Work Schedule**: verification, validation, test execution, and UAT were subsequently confirmed complete by the project user on 17/08/26; the controlled result records now identify this as retrospective user-confirmed evidence. - -**Software Project Plan** — after actually reading the example's full PDF (not just headings), found 5 real structural gaps and closed them (doc grew from 17 to 18 top-level sections): -1. New **Section 6, "Software development lifecycle methodology"** — deliberately does *not* copy the example's "Waterfall" claim; Git evidence shows continuous incremental delivery instead (features and security fixes interleaved throughout, not phase-separated), and the document says so. -2. New **Section 8.1, "Human resources and effort estimate"** — states headcount (1 person per role) and calendar-duration-by-phase, and explicitly states why no man-day effort figure is given: no time-tracking evidence exists, so one is not fabricated (same treatment as budget, below). -3. New **Section 8.5, "Computer and equipment resources"** — discloses no equipment inventory exists rather than inventing one. -4. New **Section 11.1, "Contingency actions for non-completed tasks."** -5. New **Section 12.2, "Quality criteria and evaluation methods"** — cross-references existing SRS/NFR content instead of duplicating it. -6. Also added **Section 16.1/16.2**, stating BRN WMS's actual file-naming and version convention explicitly in the deliverable itself (previously this only lived in this handoff file) — see Section 4 for the convention itself. - -**Progress Status Record 13** (the last of the 13): its reporting period (15/08/26–17/08/26) remains historical evidence of the original closure overrun. CH-004 subsequently revised the closure target to 24/08/26. - -**List of Evidence, Verification Results, Project Repository (Backup), Product Operation Guide**: each got the same-day status callout / role-name / disclosure updates described above where applicable. - -**Budget**: deliberately **not disclosed** anywhere (Project Charter Report says so explicitly) — no contemporaneous budget record exists, so no figure is fabricated, unlike the example's ฿350,000 breakdown. - -**Database backup**: developer-reported as a daily `mysqldump` script, output stored off-server with a retention policy — real information, but schedule/location/retention specifics and restoration testing are still open (Product Operation Guide item OP-001; Project Repository Backup items BK-001/BK-002). - -### Existing roles (confirmed roster) - -| Person | BRN WMS role | -|---|---| -| คุณเสรี วิริยะสกุลธรณ์ | Project Sponsor / Customer Representative / Authorized Approver; Managing Director | -| คุณอภิรัชต์ สุภัทรประทีป | Project Manager | -| ธนกร สถิตวิทยากุล | Developer / System Analyst | -| ปริญ งามขำ | QA / Tester — added 17/08/26, independent of the Developer | -| คุณเยาวลักษณ์ บางชมภู | Document Control — added 17/08/26, carried over from the example project's same role/person, same company | - -Rule: the developer must never be presented as the independent approver of their own document. Use the Project Manager or Sponsor for review/approval per the example and available evidence. Do not invent additional named people — use `TBD` when a role is genuinely required but unassigned (currently none are TBD; all confirmed roles above are filled). - -### Naming, date, and version conventions - -- Display dates as Gregorian `DD/MM/YY` (e.g. `09/03/26`); filenames use compact Buddhist-calendar dates (e.g. `25690105`). -- Filename pattern: `[Project code] [Document name][ - distinguishing suffix if multi-instance] [YYYYMMDD Buddhist] V[version]`. -- **Deviation from the example, on purpose**: do not append author initials (example uses `...V1.0 ApS.pdf`; BRN WMS does not). -- **Deviation from the example, on purpose**: no `0.1`/`0.2` Draft staging — documents release directly at `V1.0` once complete. "Final" is document-control status, not proof of signature. -- Git-supported implementation begins `19/02/26`; development substantially complete `29/05/26`; stabilization evidence `03/08/26`; agreed completion boundary `14/08/26`. - -### HTML formatting decisions (for the fine-tuning step, once HTML exists) - -- Statement of Work: A4 portrait formal letter; BRN emblem, company name/address, blue title band, signature area on the final page. -- Work Schedule: A4 landscape spreadsheet; dark-blue document bar, dense grid, repeated headers, separate approval page. -- Software Project Plan: A4 portrait multi-page; corporate header, blue section bars, controlled tables, approval page. -- Use `app/assets/images/brn-document-header-left.png` (derived from `app/assets/images/brn-document-header.png`) in every generated SDLC HTML document; render the blue/grey title band in HTML per-document. Never use the `BRN WMS` product logo as the company logo. -- Preserve the header image's aspect ratio — `25mm` height corresponds to its approved width; don't change one dimension independently. Keep the title band right-aligned. -- Document-control tables: dark-blue header row/white text, light-blue label column, thin grey borders, consistent padding. -- Light blue for item/section headers only inside Customer Requirements — don't touch the corporate title band styling. -- Tables: prefer `table-layout: auto`; ID/status columns `width: 1%` + `white-space: nowrap`; description/value columns take the rest. Don't force unnecessary width. -- Chrome Print Preview: A4, Default/100% scale, Background graphics enabled. Landscape only where required (currently just Work Schedule). -- Software Design's Use Case/Component/Deployment diagrams and representative UI screenshots get added at the HTML stage, not in Markdown. -- Do not use `scripts/format_progress_status_html.php` — rejected earlier as less useful than direct per-document HTML formatting. - -## 3. Next immediate tasks - -1. Re-export PM 1–5 to HTML (all deleted 17/08/26), then convert PM 6–10, SI 11–22, and `3-Other Document` to HTML for the first time — all via VS Code Markdown PDF (user-driven step). -2. AI fine-tunes each generated `.html` to A4 print layout per the conventions in Section 2 — reapply PM 1–5's previously-established per-document layouts (they were deleted, not the decisions), match the example's per-document form for Change Report/Meeting Record, match the example's table/layout style for SI documents that have an example equivalent, and use shared document-control conventions for documents with no example equivalent (Software Components, Software, Maintenance Documentation, Project Repository, Project Repository Backup, and all `3-Other Document` items except where the example is deliberately not duplicated — see Traceability Record Table's Deviation note). -3. User prints each finished HTML to PDF and re-exports the PM 1–5 PDF package to `C:\Users\TL\Documents\200-WMS-26-001-00\1-PM Process (10 Work Product)`, replacing the stale copies there. -4. Independently confirm the `backup` Git remote is actually in sync (currently developer-reported only) and perform a restoration check (BK-001, BK-002). -5. During manual review, confirm the retrospective user-confirmed test, UAT, verification, and acceptance wording is appropriate for final sign-off. -6. Capture any available tester, environment, execution-date, reviewer, attendee, and Sponsor-signature details in the relevant controlled records. -7. Confirm the final project-closure/signature date to be used in exported documents, within the approved period ending 24/08/26. -8. Record the `mysqldump` backup's exact schedule, off-server destination, and retention period in a controlled reference (Product Operation Guide item OP-001). -9. Schedule and conduct user training (a planned curriculum already exists in the Training Report; no session has occurred). -10. Do not restore the legacy `200-TAS-*` PDFs that were cleared from the completed-package PM 6–8 folders on 17/08/26 — populate those folders only with BRN WMS work products. - -## 4. Architectural constraints and decisions - -### Application scope (as reflected in the SDLC documents) - -BRN WMS covers: multi-company/role-based access; inventory and warehouse operations (stock in/out/transfer, lot/serial/expiry, barcode); sales (quotation/order/invoice/return); purchasing (request/order/invoice/supplier-return); finance (receipts/payments); accounting (chart of accounts, journals, GL); reporting; controlled document numbering; Node.js/Socket.IO notifications and scheduled jobs; Docker Compose or manual LAMP deployment. Two MariaDB databases: `wms` (identity/company) and `wms2` (WMS/accounting). 31 PHP manager classes under `app/assets/utils/classes/`. - -### Evidence discipline (the single most important working rule) - -- Never claim a test, meeting, verification, validation, or acceptance occurred unless there is real evidence (a Git commit, or an explicit developer/user statement) — always disclose when something is reconstructed or still pending rather than presenting it as contemporaneous or complete. -- Status fields default to "pending" / "not yet executed" / "TBD" until real evidence exists. Don't flip them to "complete"/"passed" just because documentation work finished — documentation completeness and activity completeness are different things (this came up explicitly: the project stays WIP for exactly this reason, confirmed by the user after discussing ISO surveillance-audit use). -- Reconstructed planning activities (most of this project, since documentation was written after implementation) are acceptable **only when transparently labeled as reconstructed**. -- Never fabricate a figure with no evidentiary basis (budget, effort in man-days, equipment inventory) — state plainly that it isn't disclosed/available instead. This has been applied consistently three times: Project Charter budget, Software Project Plan effort, Software Project Plan equipment. -- When restating the example package's content (methodology, structure), don't just copy it if BRN WMS's actual evidence contradicts it — e.g., the example says "Waterfall," BRN WMS's Git history shows incremental/evolutionary delivery, so the SPP says the latter and explains why. -- Cross-document consistency matters more than making things look finished: verify every cited ID/commit hash actually exists in its source before trusting it. This class of check found and fixed real gaps twice this session (Traceability Record's ID linkage, Correction Register's commit-message accuracy) — worth repeating periodically, e.g. before major HTML/PDF export passes. -- Avoid unnecessary duplication of the same data across documents where two copies could drift out of sync — e.g., the Other Document "Traceability Record Table" is a pointer/summary to the single master matrix in SI work product 13, not a second full copy (explicit user decision after being asked). - -### Repository safety - -- The repository has unrelated, pre-existing application changes — do not revert, reset, or overwrite them while working on SDLC documents. -- Limit changes to `sdlc/`, `SDLC_DOCS.md`, and explicitly requested support files. -- **`sdlc/` is entirely gitignored** — there is no git safety net for anything under it. Deletions (e.g., the PM 1–5 HTML purge on 17/08/26) are not recoverable via git; treat delete operations there with the same care as anywhere else, but know that `git status`/`git stash` won't help if something goes wrong. - -## 5. Manual review and edit notes - -Use this space for any final human edits, comments, or review notes before HTML/PDF export. - -| Document / area | Manual edit, comment, or confirmation | Reviewer | Date | -|---|---|---|---| -| | | | | -| | | | | -| | | | | -| | | | | -| | | | |