12 KiB
List of Evidence
| Document field | Value |
|---|---|
| Document | List of Evidence |
| Project | BRN WMS |
| Project code | 200-WMS-26-001-00 |
| Title | Record of Verification of Project Document Preparation and Storage Status |
| Project period | 05/01/26–24/08/26 |
| Release | 17/08/26 V1.0 |
| Standard | ISO/IEC 29110 Basic Profile |
| Organizer | Apirach Supattaratpateep (Project Manager), Noppong Chareunsook (System Analyst), Thanakorn Sathitwitayakul (Developer) |
| Status | Final — reflects the document inventory at project baseline |
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.
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 |
|---|---|---|---|
| 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.0 Final.md |
Complete |
| 2 | Project Plan — Software Project Plan | 200-WMS-26-001-00 Software Project Plan 25690817 V1.0 Final.md |
Complete |
| 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 and formally closed |
| 5 | Acceptance Report | 200-WMS-26-001-00 Acceptance Report 25690817 V1.0.md |
Complete; decision Accepted; all acceptance conditions closed |
| 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 |
Backup mechanism and restoration check complete; final SDLC delivery-branch synchronization tracked as BK-004 |
SI Process
| No. | Work product | File | Status |
|---|---|---|---|
| 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 |
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 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
| No. | Item | File | Status |
|---|---|---|---|
| 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 |
| 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 |
Summary
| Measure | Count |
|---|---|
| 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) |
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
Name: Thanakorn Sathitwitayakul
Role: Developer
Signature: ______________________________________________
Date: ___________________________________________________
Reviewed by
Name: Apirach Supattaratpateep
Role: Project Manager
Signature: ______________________________________________
Date: ___________________________________________________
Reviewed and authorized by
Name: Seri Viriyasakultorn
Project roles: Project Sponsor / Customer Representative / Authorized Approver
Position: Managing Director
Company: B.R.N. Enterprise Co., Ltd.
Signature: ______________________________________________
Date: ___________________________________________________