ABCDEFGHIJKL
1
How to Prepare this Document
2
3
4
5
REQUIREMENTS TRACEABILITY MATRIX
6
7
8
1
Get ALL available requirements from stakeholders
9
- Functional
10
- Non Functional
11
- Business
This will serve as the Grouping Names. It represents the top level features of the API. Usually it is Resources or Operational Groups
12
13
2
List the top level requirements/Features (Business).
14
- Assign an Identifier to each one
15
Format: BR_22
BR_22
16
17
3
Add Functional and NonFunctional Requirements. Each should fall underneath the most relevant Business Requirement
18
- Each should have a unique Identifier
19
FormatFR_01
functional requirement
20
FormatNFR_99
non functional requirement
21
22
4
Add TestCases to address each Requirement
23
- There should be at least one TestCase per Requirement
24
- Each TestCase should have a unique identifer
25
FormatTC#002
26
27
5
Go to SoapUI.
28
Create TestSuites for the Business Requirements/Features
29
To each TestSuite, create Custom Property called REQ_NUMBER
30
Set value as the number from the spreadsheet. (BR_XXX)
31
32
Create TestCases to test the functional and nonfunctional requirements
33
To each TestCase, create Custom Property called REQ_NUMBER
34
Set value as the number from the spreadsheet (FR_XXX or NFR_XXX)
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100