PMO-04.02.04 Phase 04: Planning

REQUIREMENTS TRACEABILITY MATRIX

مصفوفة تتبع المتطلبات

tasleemat asset PMO-04.02.04 template --lang en

Deliverable Summary & Governance Boundaries

Lifecycle Phase Alignment

Phase 04: Planning

Sizing Tier Requirements

Validation Contract

This deliverable conforms to a strict companion Draft 2020-12 JSON Schema for automated structural and semantic validation.

tasleemat validate PMO-04.02.04 ./completed_data.json

Template Markdown (Bilingual)

<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Section Instructions:
- Traceability Parameters: Provide comprehensive project data for all required fields in this section.
- Requirements Traceability Mapping: Provide comprehensive project data for all required fields in this section.
- Inter-Requirements Dependencies: Provide comprehensive project data for all required fields in this section.
-->

<h3 align="right">{{Company_Name}}</h3>
<h2 align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 align="center">REQUIREMENTS TRACEABILITY MATRIX</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## 1. Traceability Parameters

**Traceability Purpose and Baseline Reference:**
[ Add details... ]

**Traceability Dimensions and Attributes:**
[ Add details... ]

---

## 2. Requirements Traceability Mapping

**Business Need to Requirement Linkage:**
[ Add details... ]

**Requirement to WBS Deliverable Mapping:**
[ Add details... ]

**Requirement to Design and Test Case Mapping:**
[ Add details... ]

---

## 3. Inter-Requirements Dependencies

**Core Inter-Requirement Dependencies:**
[ Add details... ]

**Impact and Traceability Governance:**
[ Add details... ]

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **Requirements Analyst Lead** | {{Requirements_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Quality Assurance (QA) Lead** | {{QA_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> REQUIREMENTS TRACEABILITY MATRIX | <strong>Ref:</strong> PMO-04.02.04 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

User Guide & Practitioner Instructions

Tasleemat Forms Guide

Project Artifact: Requirements Traceability Matrix

Document Reference: PMO-04.02.04

This document provides a comprehensive, professional reference to understand the purpose and effective usage of the Requirements Traceability Matrix in alignment with the Tasleemat framework.

1. What?

A bidirectional tracking artifact ensuring each requirement provides business value and is verified by test execution.

2. Why?

Guarantees no requirements are omitted, prevents unauthorized work, and provides instant impact analysis for changes.

3. When?

Established during requirements planning and maintained through development, testing, and acceptance.

4. Who?

Maintained by Business Analyst and QA Lead, audited by Project Manager and PMO.

Tailoring Tips

Use ALM/Jira issue links for agile feature-to-story-to-test traceability.
Maintain comprehensive tabular compliance matrices for external regulatory audits.

Alignment & Dependencies

1. Pre-requisites & Inputs (Upstream Dependencies)

Mandatory:
- Project Charter (PMO-03.01)
- Stakeholder Requirements
Optional / Contextual:
- Product Vision (PMO-03.02)
- Assumption Log (PMO-03.03)

2. Downstream Dependents

Mandatory:
- Work Breakdown Structure / WBS (PMO-04.02.06)
- Project Schedule (PMO-04.03.08)
- Cost Estimates (PMO-04.04.02)
Optional / Contextual:
- Product Backlog (PMO-04.02.08)
- Quality Metrics (PMO-04.05.02)

5. How?

To accurately and professionally complete the Requirements Traceability Matrix, the responsible party must populate the following critical sections based on the project context (ensure parameters.md is referenced for global project variables):

Traceability Purpose and Baseline Reference: The governing objective and versioned requirements baseline linked across the matrix.
Traceability Dimensions and Attributes: Key parameters tracked including source origin, WBS work package, design component, and test case ID.
Business Need to Requirement Linkage: Explicit linkage connecting overarching business goals to detailed functional requirements.
Requirement to WBS Deliverable Mapping: Traceability mapping associating each requirement with its corresponding WBS work package.
Requirement to Design and Test Case Mapping: Verification mapping linking requirements to technical architecture components and test verification cases.
Core Inter-Requirement Dependencies: Identified functional linkages, prerequisite requirements, and cross-feature constraints.
Impact and Traceability Governance: Protocols for assessing downstream deliverable impact when a linked requirement is modified.

6. Reference Example

A fully completed, gold-standard reference example illustrating this artifact in practice is available:

📖 Completed Example: 04_02_04_Requirements_Traceability_Matrix_Example.md

LLM Generation Prompt & Agent Instructions

Requirements Traceability Matrix - Generation Prompt

System Instructions: This document contains instructions for generating the «Requirements Traceability Matrix». When asked to fill this template, follow the section-by-section instructions below. Refer to parameters.md for project variables.

Context and Definition: A structured matrix that links product requirements from their origin to the deliverables, architecture components, and test cases that satisfy them.

Alignment & Dependencies: * Pre-requisites (Inputs): * Mandatory: Project Charter (PMO-03.01), Stakeholder Requirements * Optional: Product Vision (PMO-03.02), Assumption Log (PMO-03.03) * Downstream Dependents: * Mandatory: Work Breakdown Structure / WBS (PMO-04.02.06), Project Schedule (PMO-04.03.08), Cost Estimates (PMO-04.04.02) * Optional: Product Backlog (PMO-04.02.08), Quality Metrics (PMO-04.05.02)

Traceability Parameters

Traceability Purpose and Baseline Reference

Instruction: The governing objective and versioned requirements baseline linked across the matrix.