Requirements Traceability Matrix (RTM)
Prepared for SharkNinja – EMEA-677 Project
1. Purpose
This document lists all known and emerging requirements for the Returns Credit
Automation project.
It links each requirement to its original source and records any notes or open questions.
The matrix provides a single point of reference for traceability from initial request to final
delivery.
2. Key
Type: Business / Functional / Non-Functional / Constraint / Future Scope
Priority: MoSCoW (Must / Should / Could / Won’t for now)
Status: Draft → Confirmed → Delivered
ID Requirement Type Priori Source Acceptanc Statu Notes /
ty e Criteria s Questions
(summary)
R1 Provide one Functio Must EMEA- Retailers Draft Confirm
standard way nal 677 submit via licensing
for retailers to Returns portal; all for external
send returns Credit mandatory retailers.
data (Power Automati fields
Pages portal on doc validated
or template) before
with built-in saving.
validation.
R2 Automate Functio Must EMEA- Validated Draft Confirm
transformatio nal 677 / JIRA data is which
n of retailer converted Oracle
data into the and passes fields are
Oracle HAP HAP mandatory.
SO Mass checks
Update without
format. manual
edits.
R3 Handle Constr Must EMEA- Files split Draft Confirm
Oracle limit of aint 677 automatic exact rule
≈250 lines per ally when (per order
order through limit or per
automatic exceeded. batch).
batching.
R4 Capture Non- Must EMEA- All Draft Confirm
Finance Functio 677 approvals Finance
approval and nal recorded approver
audit trail with user, role and
before time, SLA.
upload. decision,
and
attachmen
ts.
R5 Reduce Functio Must JIRA ≥90 % rows Draft Define
manual data nal processed normalisati
cleaning of without on rules
SKUs and manual and source
format edits; for SKU list.
inconsistenci others
es to near flagged as
zero. exceptions
.
R6 Provide Functio Shoul EMEA- User can Draft Confirm
traceability nal d 677 view and what data
between report on can be
Claim ↔ RMA linked stored
↔ Credit ↔ records in internally
Deduction. the app. vs Oracle.
R7 Store and Non- Shoul JIRA Power BI Draft Define
report on key Functio d dashboard formulas
metrics (cycle nal shows and data
time, % auto- current refresh
processed, and trend schedule.
exception data.
rate).
R8 Investigate Future Could EMEA- Discovery Draft Requires
future Scope 677 paper client
integration produced agreement
options (EDI, without for phase 2
API, XML) impacting scope.
once data is phase 1
standardised. delivery.
R9 Store Functio Must Confirme File Draft Confirm
generated nal d available retention
HAP files assumpti for period and
securely in on 2025- download folder
SharePoint for 10 with audit structure.
manual record.
upload.
R1 Maintain Non- Must Assumpti Data Draft Confirm
0 UK/EU data Functio on stored in corporate
residency and nal UK/EU retention
GDPR environme policy.
compliance. nt; audit
retained
for 6 years.
4. Next Steps
• Validate each open question with stakeholders during the discovery workshops.
• Update the Status column once requirements are confirmed.
• Link each confirmed requirement to corresponding backlog item in Azure
DevOps or Jira.
