SDLC docs feedback and additional adjustment
This commit is contained in:
@@ -20,34 +20,35 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr
|
||||
|
||||
| No. | Work product | File(s) | Status |
|
||||
|---:|---|---|---|
|
||||
| 1 | Statement of Work | `200-WMS-26-001-00 Statement of Work 25690105 V1.0 Final.md/.html/.pdf` | Complete (Markdown, HTML, PDF) |
|
||||
| 2 | Project Plan — Work Schedule | `200-WMS-26-001-00 Work Schedule 25690105 V1.0 Final.md/.html/.pdf` | Complete |
|
||||
| 2 | Project Plan — Software Project Plan | `200-WMS-26-001-00 Software Project Plan 25690105 V1.0 Final.md/.html/.pdf` | Complete |
|
||||
| 2 | Project Plan — Customer Requirements | `200-WMS-26-001-00 Customer Requirements 25690112 V1.0 Final.md/.html/.pdf` | Complete |
|
||||
| 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 (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 |
|
||||
| 1 | Statement of Work | `200-WMS-26-001-00 Statement of Work 25690105 V1.0 Final.md` | Complete (Markdown, HTML, PDF) |
|
||||
| 2 | Project Plan — Work Schedule | `200-WMS-26-001-00 Work Schedule 25690817 V1.1 Final.md` | Complete (V1.1 re-issue; V1.0 dated 25690105 superseded) |
|
||||
| 2 | Project Plan — Software Project Plan | `200-WMS-26-001-00 Software Project Plan 25690817 V1.1 Final.md` | Complete (V1.1 re-issue; V1.0 dated 25690105 superseded) |
|
||||
| 2 | Project Plan — Customer Requirements | `200-WMS-26-001-00 Customer Requirements 25690112 V1.0 Final.md` | Complete |
|
||||
| 3 | Progress Status Record (13 records) | `...25690123`, `25690218`, `25690225`, `25690317`, `25690429`, `25690508`, `25690513`, `25690523`, `25690529`, `25690731`, `25690803`, `25690814`, `25690817 V1.0.md` | Complete (all 13) |
|
||||
| 4 | Correction Register | `200-WMS-26-001-00 Correction Register 25690817 V1.0.md` | Complete; 28 entries, all verified against linked test cases |
|
||||
| 5 | Acceptance Report | `200-WMS-26-001-00 Acceptance Report 25690817 V1.0.md` | Complete; decision Accepted; CON-009 (signature capture) open |
|
||||
| 6 | Change Report (3 separate reports) | `... - Rack to Bin Rename 25690521`, `- Demo Data Population 25690808`, `- Delivery Preparation Bundle 25690810` | Complete (CH-001–CH-003) |
|
||||
| 7 | Meeting Record (4 checkpoint records) | `... - Project Initiation Checkpoint 25690213`, `- Development Substantially Complete Checkpoint 25690529`, `- Stabilization Checkpoint 25690803`, `- Closure Preparation Checkpoint 25690814` | Complete (MTG-001–MTG-004) |
|
||||
| 8 | Software Configuration | `200-WMS-26-001-00 Software Configuration 25690817 V1.0.md` | Complete |
|
||||
| 9 | Project Repository | `200-WMS-26-001-00 Project Repository 25690817 V1.0.md` | Complete |
|
||||
| 10 | Project Repository (Backup) | `200-WMS-26-001-00 Project Repository (Backup) 25690817 V1.0.md` | Complete; restoration check performed |
|
||||
|
||||
## SI Process
|
||||
|
||||
| No. | Work product | File | Status |
|
||||
|---:|---|---|---|
|
||||
| 11 | Software Requirements Specification (SRS) | `200-WMS-26-001-00 Software Requirements Specification 25690817 V1.0.md` | Markdown complete; HTML/PDF pending |
|
||||
| 12 | Software Design | `200-WMS-26-001-00 Software Design 25690817 V1.0.md` | Markdown complete; HTML/PDF pending |
|
||||
| 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 |
|
||||
| 11 | Software Requirements Specification (SRS) | `200-WMS-26-001-00 Software Requirements Specification 25690817 V1.0.md` | Complete |
|
||||
| 12 | Software Design | `200-WMS-26-001-00 Software Design 25690817 V1.0.md` | Complete |
|
||||
| 13 | Traceability Record | `200-WMS-26-001-00 Traceability Record 25690817 V1.0.md` | Complete; 34/34 requirements linked and verified |
|
||||
| 14 | Software Components | `200-WMS-26-001-00 Software Components 25690817 V1.0.md` | Complete |
|
||||
| 15 | Test Cases and Test Procedures | `200-WMS-26-001-00 Test Cases and Test Procedures 25690817 V1.0.md` | Complete; 34 cases defined, 34 executed 10/08/26–14/08/26 |
|
||||
| 16 | Test Report | `200-WMS-26-001-00 Test Report 25690817 V1.0.md` | 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 |
|
||||
| 18 | Software User Documentation | `200-WMS-26-001-00 Software User Documentation 25690817 V1.0.md` | Complete |
|
||||
| 19 | Product Operation Guide | `200-WMS-26-001-00 Product Operation Guide 25690817 V1.0.md` | Complete |
|
||||
| 20 | Maintenance Documentation | `200-WMS-26-001-00 Maintenance Documentation 25690817 V1.0.md` | Complete |
|
||||
| 21 | Verification Results | `200-WMS-26-001-00 Verification Results 25690817 V1.0.md` | Complete; Round 2 independent verification by Document Control 17/08/26 |
|
||||
| 22 | Validation Result | `200-WMS-26-001-00 Validation Result 25690817 V1.0.md` | Complete; 12 of 12 scenarios passed |
|
||||
|
||||
## Other Document
|
||||
|
||||
@@ -55,7 +56,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; |
|
||||
| 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 |
|
||||
|
||||
@@ -64,11 +65,13 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr
|
||||
| Measure | Count |
|
||||
|---|---:|
|
||||
| Total controlled work-product entries (PM + SI, counting each grouped item as one row above) | 22 |
|
||||
| Total individual files across grouped items (13 PSR + 4 CR + 4 MTG counted individually, plus the other 30 singular items) | 42 |
|
||||
| Complete with Markdown, HTML, and PDF | 19 (PM work products 1–5 set) |
|
||||
| Markdown complete, HTML/PDF pending | 23 (PM 6–10, all SI 11–22) |
|
||||
| Total individual controlled files (13 Progress Status Records + 3 Change Reports + 4 Meeting Records + 26 single-instance documents) | 46 |
|
||||
| Markdown source complete under `sdlc/` | 46 of 46 |
|
||||
| Included in the generated PDF delivery package (`sdlc-delivery/`) | 42 of 46 — regeneration pending for the 4 Meeting Records |
|
||||
| Other Document items complete | 4 of 5 (Training Report pending execution, not preparation) |
|
||||
|
||||
The PDF delivery package is generated from `sdlc/` by `scripts/build-sdlc-delivery.sh`; it is build output and is not edited by hand.
|
||||
|
||||
## Approval
|
||||
|
||||
### Prepared by
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
| 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) |
|
||||
| 4 | Project duration | 05/01/26–24/08/26 (232 days) |
|
||||
|
||||
## Project objectives
|
||||
|
||||
@@ -60,6 +60,7 @@ See the Stakeholder Register (this folder) for the full register with engagement
|
||||
| 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 |
|
||||
| 6 | Yaowalak Bangchomphoo | Document Control | Control identifiers, versions, approvals, and evidence |
|
||||
|
||||
## Project timeline
|
||||
|
||||
@@ -68,8 +69,9 @@ See the Stakeholder Register (this folder) for the full register with engagement
|
||||
| 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–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) |
|
||||
| Test, validation and demonstration data | 04/08/26–14/08/26 | Test and validation execution 10/08/26–14/08/26; demo data population `dd48a8b` (14/08/26) |
|
||||
| Delivery preparation | 15/08/26–17/08/26 | Rebranding, Docker Compose deployment stack, and SDLC documentation completion, and the recorded acceptance decision; see Change Report CH-003 |
|
||||
| Closure | 18/08/26–24/08/26 | Final work-product review and Project Sponsor signature capture; acceptance decision recorded 17/08/26 |
|
||||
|
||||
## Project budget
|
||||
|
||||
|
||||
@@ -24,13 +24,13 @@ This register identifies project stakeholders, their roles, responsibilities, an
|
||||
| 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) |
|
||||
| 5 | Parin Ngamkham | PaNg | QA / Tester | Execute tests, verify quality, and facilitate validation, independent of the Developer | R (Responsible), C (Consult) |
|
||||
| 6 | Yaowalak Bangchomphoo | YaB | Document Control | Control identifiers, versions, approvals, distribution, repository content, and evidence; 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) |
|
||||
| 10 | System Administrator | — | Supporting user | Configure environment, company, users, services, monitoring, backup, and recovery | C (Consult), I (Inform) |
|
||||
| 11 | Management / Auditor | — | Information consumer | Review controlled records, transaction history, exceptions, and management information | I (Inform) |
|
||||
|
||||
Note: The Engagement Level codes used are as follows — A: Approve, R: Responsible, C: Consult, I: Inform, following the RACI Matrix approach
|
||||
|
||||
|
||||
@@ -30,9 +30,9 @@ 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 |
|
||||
| Verified in Verification Results (work product 21) | 0 |
|
||||
| Validated in Validation Result (work product 22) | 0 |
|
||||
| Test cases executed with recorded result | 34 (executed 10/08/26–14/08/26) |
|
||||
| Verified in Verification Results (work product 21) | 34 |
|
||||
| Validated in Validation Result (work product 22) | 34 requirements covered by 12 passed scenarios |
|
||||
|
||||
## Approval
|
||||
|
||||
|
||||
@@ -10,19 +10,21 @@
|
||||
| Release | 17/08/26 V1.0 |
|
||||
| Standard | ISO/IEC 29110 Basic Profile |
|
||||
| Prepared by | Apirach Supattaratpateep — Project Manager |
|
||||
| Status | Final as a status report — **no training session has been conducted**; see Section 1 |
|
||||
| Status | Final as a training plan — a session is **scheduled but not yet conducted**; see Section 1 |
|
||||
|
||||
## 1. Training information
|
||||
|
||||
| Topic | Details |
|
||||
|---|---|
|
||||
| Training date | Not yet scheduled |
|
||||
| Location | Not yet determined |
|
||||
| Trainer | Thanakorn Sathitwitayakul (Developer); no dedicated trainer role is currently assigned |
|
||||
| Training date | Scheduled 21/08/26, within the project period ending 24/08/26; not yet conducted |
|
||||
| Location | B.R.N. Enterprise Co., Ltd. head office, with remote attendance available for warehouse-floor staff |
|
||||
| Trainer | Thanakorn Sathitwitayakul (Developer), supported by Parin Ngamkham (QA / Tester) for workflow walkthroughs; no dedicated trainer role is assigned |
|
||||
| Training organizer | Apirach Supattaratpateep (Project Manager) |
|
||||
| Expected attendees | Not yet determined — expected to include Owner/Admin, Staff, and Viewer role representatives per company |
|
||||
| Expected attendees | Owner/Admin, Staff, and Viewer role representatives per company, plus the System Administrator |
|
||||
| Planned duration | One day, structured as the ten curriculum topics in Section 2 |
|
||||
| Materials | Software User Documentation (work product 18) and Product Operation Guide (work product 19) |
|
||||
|
||||
## 3. Planned curriculum
|
||||
## 2. Planned curriculum
|
||||
|
||||
Derived from the Software User Documentation (work product 18):
|
||||
|
||||
@@ -39,15 +41,28 @@ Derived from the Software User Documentation (work product 18):
|
||||
| 9 | Notifications |
|
||||
| 10 | Reports (filter, view, print, export) |
|
||||
|
||||
## 4. Result
|
||||
## 3. Result
|
||||
|
||||
No result to report — training has not yet occurred. This section will be completed with actual attendance, evaluation, and feedback once a session is held.
|
||||
**No result to report — the session has not yet taken place.** This section is to be completed only after training is delivered, and must then record:
|
||||
|
||||
## 5. Recommendation
|
||||
| Field | To be recorded after the session |
|
||||
|---|---|
|
||||
| Actual date and duration | |
|
||||
| Trainer and organizer | |
|
||||
| Attendance | Name, company, and role of each attendee |
|
||||
| Evaluation | Comprehension check or post-training assessment result |
|
||||
| Feedback | Attendee comments and any follow-up requests |
|
||||
| Follow-up actions | Any documentation or system change arising from the session |
|
||||
|
||||
Schedule training after Test Report execution (work product 16) and before the customer validation session (work product 22), so trained users can meaningfully participate in validation walkthroughs.
|
||||
Nothing in this section may be filled in before the session is delivered.
|
||||
|
||||
## 6. Approval
|
||||
## 4. Recommendation
|
||||
|
||||
Test execution (work product 16) and customer validation (work product 22) were completed over 10/08/26–14/08/26 without a prior training session; validation was performed by the Customer Representative rather than by trained end users.
|
||||
|
||||
Training is therefore scheduled for 21/08/26, before operational go-live and within the project period ending 24/08/26, so that operational users are trained on the delivered system before they rely on it. Section 3 must be completed with actual attendance, evaluation, and feedback immediately after the session; until then this document stands as a plan and not as evidence that training has occurred.
|
||||
|
||||
## 5. Approval
|
||||
|
||||
### Prepared by
|
||||
|
||||
|
||||
Reference in New Issue
Block a user