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

docs(sdlc): finalize ISO 29110 evidence package

Browse Source
This commit is contained in:
Thanakorn
2026-08-26 12:35:57 +07:00
parent c68a43449f
commit 5d93e87771
53 changed files with 195 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
sdlc/3-Other Document/200-WMS-26-001-00 List of Evidence 25690817 V1.0.md
+34 -1
View File
@@ -16,6 +16,38 @@
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.
## Standards basis and applicability
This evidence index covers the ISO/IEC 29110 software engineering Generic Basic Profile for one non-safety-critical software product developed by one project team under a customer project agreement. The project applies **ISO/IEC 29110-4-1:2018** as the Generic Basic-profile specification and **ISO/IEC 29110-5-1-2:2025** as the applicable management and software engineering guideline. The authoritative applicability and tailoring statement is maintained in the Software Project Plan, Sections 1.1 and 1.2.
| Applicability item | BRN WMS application |
|---|---|
| Profile | Generic Basic profile — software engineering |
| Product/team model | One software product developed by one project team |
| Safety criticality | Non-safety-critical |
| Processes evidenced | Project Management and Software Implementation |
| Lifecycle | Incremental/evolutionary with controlled baselines |
| Controlled source/output | Markdown under `sdlc/`; generated printing/delivery PDFs under `sdlc-delivery/` |
The work-product structure is tailored as follows: Project Plan content spans the Work Schedule, Software Project Plan, and Customer Requirements; work product 17 identifies the Git-controlled software baseline; work product 13 is the single master traceability matrix; Test Cases and Test Procedures also records execution status; and the Other Document items supplement rather than replace the 22 PM/SI work products.
## Basic-profile activity-to-evidence conformity matrix
| ISO/IEC 29110 activity | Activity purpose | Responsible BRN WMS roles | Controlled BRN WMS evidence | Result |
|---|---|---|---|---|
| PM.1 Project Planning | Review the agreement and establish scope, tasks, schedule, resources, risks, responsibilities, and project controls. | Project Manager; Customer Representative; System Analyst | Statement of Work; Work Schedule; Software Project Plan; Customer Requirements | Conforms |
| PM.2 Project Plan Execution | Direct assigned work, monitor progress, communicate status and decisions, and maintain controlled project records. | Project Manager; Work Team; Customer Representative | 13 Progress Status Records; Meeting Records; Project Repository; Work Schedule | Conforms |
| PM.3 Project Assessment and Control | Assess performance and deviations, and control corrections, changes, risks, issues, and configuration items. | Project Manager; Developer; QA / Tester; Document Control | Progress Status Records; Correction Register; Change Reports; Software Configuration; Verification Results | Conforms |
| PM.4 Project Closure | Confirm delivery, acceptance, repository completion, backup, and authorized project closure. | Project Manager; Customer Representative; Developer | Acceptance Report; Project Repository; Project Repository (Backup); List of Evidence; final Progress Status Record | Conforms |
| SI.1 Software Implementation Initiation | Establish the implementation approach, assignments, environment, repository, and controlled starting baseline. | Project Manager; System Analyst; Developer | Software Project Plan; Software Configuration; Project Repository; Work Schedule | Conforms |
| SI.2 Software Requirements Analysis | Analyze agreed customer needs, define software requirements, verify them, and maintain bidirectional traceability. | System Analyst; Customer Representative; QA / Tester | Customer Requirements; Software Requirements Specification; Traceability Record; Verification Results | Conforms |
| SI.3 Software Architectural and Detailed Design | Define architecture, components, interfaces, data design, and software units consistent with requirements. | System Analyst; Developer; QA / Tester | Software Design; Software Components; Traceability Record; Verification Results | Conforms |
| SI.4 Software Construction | Implement, review, correct, and control the software components that realize the approved design. | Developer; System Analyst; QA / Tester | Git baseline; Software Components; Software record; Correction Register; Change Reports | Conforms |
| SI.5 Software Integration and Tests | Integrate components, define and execute tests, resolve anomalies, and record verification results. | Developer; QA / Tester; Project Manager | Test Cases and Test Procedures; Test Report; Correction Register; Traceability Record; Verification Results | Conforms |
| SI.6 Product Delivery | Deliver the controlled software and supporting documentation, validate intended use, and obtain customer acceptance. | Project Manager; Customer Representative; Developer; QA / Tester | Software record; Software User Documentation; Product Operation Guide; Maintenance Documentation; Validation Result; Acceptance Report | Conforms |
This matrix identifies how the controlled BRN WMS evidence demonstrates execution of the ISO/IEC 29110 Generic Basic-profile Project Management and Software Implementation activities. `Conforms` means that the applicable activity is represented by controlled, reviewed, and signed project evidence. Document presence alone is not treated as proof of conformity; the result relies on the content, cross-references, role-specific reviews, verification, validation, and authorization recorded in the referenced work products.
## PM Process
| No. | Work product | File(s) | Status |
@@ -47,7 +79,7 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr
| 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; operational follow-up actions include targets and closure criteria |
| 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 |
| 21 | Verification Results | `200-WMS-26-001-00 Verification Results 25690817 V1.0.md` | Complete; Round 2A document-control and Round 2B technical work-product verification completed 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
@@ -66,6 +98,7 @@ Index every controlled work product prepared for BRN WMS, its file, and its curr
|---|---:|
| Total controlled work-product entries (PM + SI, counting each grouped item as one row above) | 22 |
| Total individual controlled files (13 Progress Status Records + 3 Change Reports + 4 Meeting Records + 26 single-instance documents) | 46 |
| Basic-profile activities mapped to controlled evidence | 10 of 10 (PM.1–PM.4 and SI.1–SI.6) |
| Markdown source complete under `sdlc/` | 46 of 46 |
| Included in the generated PDF delivery package (`sdlc-delivery/`) | 46 of 46, including all 4 Meeting Records |
| Other Document items complete | 4 of 5 (Training Report pending execution, not preparation) |