Editing Test Traceability Matrix (section)

== 1. Purpose and How to Use This Matrix ==

A Test Traceability Matrix (TTM) provides bidirectional traceability between:

<pre>Business Requirement  ←→  Design Element  ←→  Test Case  ←→  Test Result</pre>
It answers two critical questions:

# '''Completeness:''' Is every requirement covered by at least one test? (forward trace)
# '''Necessity:''' Does every test correspond to a requirement? (backward trace — prevents test bloat)

<span id="status-values-used-in-this-document"></span>
=== Status values used in this document ===

{|
!width="50%"| Status
!width="50%"| Meaning
|-
| <code>Planned</code>
| Test case defined; not yet implemented
|-
| <code>Implemented</code>
| Test case exists in the test suite
|-
| <code>Passed</code>
| Test executed and passed in the latest run
|-
| <code>Failed</code>
| Test executed and failed in the latest run
|-
| <code>Blocked</code>
| Cannot be run due to an open defect or missing dependency
|-
| <code>N/A</code>
| Not applicable to this version
|}

<span id="test-case-id-scheme"></span>
=== Test case ID scheme ===

<pre>TC-&lt;LEVEL&gt;-&lt;NNN&gt;

LEVEL:
  UT   Unit test  (single program in isolation)
  IT   Integration test (two or more programs together)
  ST   System test (full end-to-end)
  NFT  Non-functional test (performance, security, etc.)

NNN: zero-padded sequence

Examples:
  TC-UT-001   Unit test #1
  TC-ST-001   System test #1
  TC-NFT-001  Non-functional test #1</pre>

-----

<span id="test-levels-and-types"></span>