nok/wms-app
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(sdlc): align V1.0 audit evidence

Browse Source
This commit is contained in:
Thanakorn
2026-08-19 14:11:00 +07:00
parent 36ab46b9d1
commit 02e1483087
14 changed files with 78 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sdlc/1-PM Process (10 Work Product)/2.Project Plan/1-Work Schedule/200-WMS-26-001-00 Work Schedule 25690817 V1.1 Final.md → sdlc/1-PM Process (10 Work Product)/2.Project Plan/1-Work Schedule/200-WMS-26-001-00 Work Schedule 25690817 V1.0 Final.md
+7 -8
View File
@@ -7,19 +7,18 @@
| Project code | 200-WMS-26-001-00 |
| Project period | 05/01/26–24/08/26 |
| Project end date | 24/08/26 |
| Release | 17/08/26 V1.1 Final |
| Original baseline | 05/01/26 V1.0 Final |
| Release | 17/08/26 V1.0 Final |
| Schedule baseline | 05/01/26 |
| Standard | ISO/IEC 29110 Basic Profile |
| Status | Final — ready for authorized approval |
| Status | Final — reviewed and authorized |
## Revision history
| Version | Date | Change | Prepared by |
|---|---|---|---|
| V1.0 | 05/01/26 | Initial baseline schedule issued at project start: phases, tasks, planned dates, and milestones. | Apirach Supattaratpateep |
| V1.1 | 17/08/26 | Re-issued at closure. Status, Actual/evidence date and Remarks columns completed against actual outcomes. Planned dates, project end date and task breakdown from V1.0 are unchanged. | Apirach Supattaratpateep |
| V1.0 | 17/08/26 | Initial controlled issue. Records the 05/01/26 schedule baseline and actual outcomes through product acceptance; administrative handover and training continue through project closure on 24/08/26. | Apirach Supattaratpateep |
The Status, Actual/evidence date and Remarks columns below record outcomes as at 17/08/26. The Start, Finish and Duration columns remain the V1.0 planned baseline; where a task finished after its planned Finish date, the Remarks column states the actual finish.
The Status, Actual/evidence date and Remarks columns below record outcomes as at 17/08/26. The Start, Finish and Duration columns retain the 05/01/26 planned baseline; where a task finished after its planned Finish date, the Remarks column states the actual finish.
## Schedule basis
@@ -27,7 +26,7 @@ The Status, Actual/evidence date and Remarks columns below record outcomes as at
|---|---|---|---|---|---:|---:|---:|---|---|---|
| 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 |
| 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 | Completed | Approved scope recorded |
| 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 |
@@ -49,7 +48,7 @@ The Status, Actual/evidence date and Remarks columns below record outcomes as at
| 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 | Round 2 independent verification performed by Document Control 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 |
| 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 | In progress | Product acceptance and authorization completed 17/08/26; administrative handover and training continue through 24/08/26 |
## Milestones
sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690817 V1.1 Final.md → sdlc/1-PM Process (10 Work Product)/2.Project Plan/2-Software Project Plan/200-WMS-26-001-00 Software Project Plan 25690817 V1.0 Final.md
+7 -8
View File
@@ -7,20 +7,19 @@
| Project code | 200-WMS-26-001-00 |
| Title | Warehouse Management System Development Project Plan |
| Project period | 05/01/26–24/08/26 |
| Release | 17/08/26 V1.1 Final |
| Original baseline | 05/01/26 V1.0 Final |
| Release | 17/08/26 V1.0 Final |
| Planning baseline | 05/01/26 |
| Standard | ISO/IEC 29110 Basic Profile |
| Project Manager | Apirach Supattaratpateep |
| Status | Final — ready for review and authorized approval |
| Status | Final — reviewed and authorized |
## Revision history
| Version | Date | Change | Prepared by |
|---|---|---|---|
| V1.0 | 05/01/26 | Initial project plan issued at project start: scope, lifecycle, organization, resources, risks, quality, configuration and closure approach. | Apirach Supattaratpateep |
| V1.1 | 17/08/26 | Re-issued at closure. Section 6 records the lifecycle actually followed and the implementation commit count; Section 8.5 records the equipment-evidence position; Section 12.2 records achieved quality results; Section 16 records the naming/version conventions and repository state as applied across the controlled file set. Scope, organization and risk content from V1.0 are unchanged. | Apirach Supattaratpateep |
| V1.0 | 17/08/26 | Initial controlled issue. Consolidates the 05/01/26 planning baseline with lifecycle, quality, equipment-evidence, and configuration outcomes recorded through closure preparation. | Apirach Supattaratpateep |
Sections 6, 8.5, 12.2 and 16 describe outcomes as at 17/08/26; the remaining sections are the V1.0 baseline.
Sections 6, 8.5, 12.2 and 16 describe outcomes as at 17/08/26; the remaining sections retain the 05/01/26 planning baseline.
## 1. Purpose
@@ -348,7 +347,7 @@ BRN WMS document filenames do not append author initials.
### 16.2 Version declaration
Documents created for BRN WMS are released directly at `V1.0` once content is complete, without the example's separate `0.1`/`0.2` Draft stages — BRN WMS work products are not labeled `Draft` unless explicitly requested, per the same recorded decision. "Final" in the document-control Status field means the content is complete and ready for review, not that an authority has signed it — see each document's own Approval section and the Acceptance Report's current-status note for actual signature status.
Documents created for BRN WMS are released directly at `V1.0` once content is complete, without the example's separate `0.1`/`0.2` Draft stages — BRN WMS work products are not labeled `Draft` unless explicitly requested, per the same recorded decision. "Final" in the document-control Status field means the controlled content is complete; authorization and the project-acceptance decision are recorded in each document's Approval section and the Acceptance Report.
### 16.3 Repository and backup
@@ -356,7 +355,7 @@ Documents created for BRN WMS are released directly at `V1.0` once content is co
- Documents identify title, date, version, status, preparer, reviewer, and approver as applicable.
- Drafts remain distinguishable from approved baselines.
- The Project Repository contains the current controlled work products and supporting evidence (work product 9).
- The repository backup is maintained separately and checked during project closure (work product 10); that check was performed manually by the Developer (BK-001, BK-002 closed).
- The repository backup is maintained separately and checked during project closure (work product 10); the baseline and restoration checks were performed manually by the Developer (BK-001 and BK-002 closed), package completeness is recorded by BK-003, and final SDLC delivery-branch synchronization is tracked by BK-004 through 24/08/26.
- Superseded records are retained or archived according to organizational control practices.
## 17. Acceptance and closure