Preorder Traceability Matrix
Objective
Map business requirements for Preorder creation, pricing calculation, and credit limit validation to test coverage, execution status, and evidence to ensure complete traceability and financial accuracy.
Requirement Traceability Matrix
| Requirement ID | Business Requirement | Business Risk | Test Coverage | Status | Evidence / Defect |
|---|---|---|---|---|---|
| REQ-PPO-001 | Preorder creation with accurate pricing (subtotal, discount, PPN) | Incorrect totals lead to financial loss | TC-PPO-092, API-CALC-001, SQL-PRC-002 | Passed | Pricing calculation screenshot & DB reconciliation |
| REQ-PPO-002 | Real-time credit limit validation before Preorder submission | Over-limit Preorders increase financial exposure | TC-PPO-092, API-ELIG-003 | Passed | Credit limit check before & after order |
| REQ-PPO-003 | Automatic credit limit deduction on successful CREDIT Preorder | Credit limit not updated causes over-exposure | TC-PPO-092, API-CREDIT-004, SQL-CREDIT-001 | Passed | Credit usage update verification |
| REQ-PPO-004 | Preorder blocked when credit limit is insufficient | Uncontrolled credit usage | TC-PPO-093, API-BLOCK-005 | Passed | Blocked Preorder with warning message |
| REQ-PPO-005 | Consistency between UI, API, and Database | Mismatch between displayed and stored values | Cross-check TC-PPO-092 | Passed | UI vs DB reconciliation |
Coverage Interpretation
- High financial risk areas (credit limit & pricing) have multiple validation layers: UI + API + SQL.
- Boundary testing applied for credit limit: exactly at limit, below, and above.
- All critical requirements are covered and currently show Passed status.
- Evidence includes screenshots, API responses, and database queries.
When to Use It
- UAT preparation and stakeholder sign-off.
- Release regression validation.
- Audit of financial controls.
- Impact analysis for future changes in pricing or credit rules.