Requirements Traceability Matrix

AAES XOG Oracle

Requirements Traceability Matrix Template

Version: 1.0

The following template is provided for use with Requirements and Requirements Traceability Matrix. The blue text provides guidance to the author, and it should
be deleted before publishing the document.

See the Revision History table at the end of the document for revision status.

Modified: 11/12/2024 06:44:36 Last modified by: User

1
©2009 Accenture. All Rights Reserved.
 Requirements Traceability Matrix

o the author, and it should

Modified: 11/12/2024 06:44:36 Last modified by: User

2
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Using the Requirements Traceability Matrix (RTM)

Click the button to perform the specified action.

Enter Record Requirement

Determine Enter High- Track
Product Updates to s Definitions
Requiremen level Requirement
Requiremen Requirement and
ts Requirements s
ts s Categories
Ensure that the RTM is placed under Version Control
* Refer to the Configuration Management (CM) Plan or Project Plan for more detailed information on Requirements Management. Ensure that the RTW is put under ve
Name of Action How to Perform Action
Determine Requirements Use the project's Statement of Work (SOW) and/or High-level requirements gathering sessions to
(High-level Requirements and Product determine the requirements that the project is responsible for implementing.
Requirements Worksheets) The types of requirements are shown in Figure 1 below.

Enter High-level Requirements These are created in Plan stage. Enter the high-level requirements on the High-level Requirements
(High-level Requirements worksheet) worksheet. Complete the following steps for each high-level requirement:

Enter the Project Name. Use the official project title.

Enter a Project Stage. Enter project stage of work.

Modified: 11/12/2024 06:44:36 Last modified by: User

3
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Enter a High-level Requirement ID using the project's standard. Enter each requirement on a new
row.

Number High-level Requirements in whole numbers 1, 2, 3, ... and then number Product
Requirements in such a way to establish bidirectional traceability (to easily trace back to high-level
requirement and vice-versa). E.g. for a high-level requirement that is assigned number 3, the
corresponding product requirements should be numbered as 3.1, 3.2, 3.3, ... etc. For product
requirement 3.1, more detailed product requirements may be numbered as 3.1.1, 3.1.2, etc.

Enter a Business Topic using the project's standard. Refer to the TOC worksheet to find the Business
Topic that is appropriate for each Requirement ID. Copy the Business Topic from the TOC worksheet
to the Business Topic field on the High-level Requirements and the Product Requirements
worksheets. For example:
Requirement ID Business Topic
1 Application Functionality
2 Customer Support
3 Usability
Continue numbering for other business topics (see TOC worksheet for details).

The project can modify the types of Requirement IDs that can be entered and the Business Topics
that these requirements are mapped to by updating the TOC worksheet. To update the TOC
worksheet, click on the TOC Worksheet hyperlink.

Enter a High-level Requirement Name.

Enter a Short Description of the requirement.

Modified: 11/12/2024 06:44:36 Last modified by: User

4
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Enter the requirement Priority. This can be L, M, or H (Low, Medium, or High):

Priority High (H) is the one which is Critical – cannot live without
Priority Medium (M) is the one which is Important – not critical but strongly desired by
stakeholders
Priority Low (L) is the one which is Optional – nice to have.

Enter The Release Number that will include this high-level requirement.

Ensure that the RTM is put under version control so that older versions of requirements can be
retrieved. Also, make updates as appropriate to Requirement Name, Short Description, and Long
Description columns.

Enter a Long Description of the requirement.

Enter a Requirement Source, such as "SOW" for a requirement that came from the Statement of
Work or "JAD Session - 11/20/2005" for a requirement that resulted from a Joint Application
Development session on November 20, 2005.

Enter the Business/Process Area to which the requirements belong to, such as Billing or Customer
Service Design

Enter the Status. The status can be Approved, Rejected, Deferred, In-Progress. Choose from the list.

Enter the Owner of the requirement, stakeholder such as a team or person.

Enter Notes, as necessary.

Enter Product Requirements These are created in Analyze stage. Enter the product requirements on the Product Requirements
(Product Requirements worksheet) worksheet. Complete the following steps for each product requirement:

Modified: 11/12/2024 06:44:36 Last modified by: User

5
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Enter the Project Name. Use the official project title.

Enter a Project Stage. Enter project stage of work.

Enter a Requirement ID using the project's standard. Enter each requirement on a new row.

Number High-level Requirements in whole numbers 1, 2, 3, ... and then number Product
Requirements in such a way to establish bidirectional traceability (to easily trace back to high-level
requirement and vice-versa). E.g. for a high-level requirement that is assigned number 3, the
corresponding product requirements should be numbered as 3.1, 3.2, 3.3, ... etc. For product
requirement 3.1, more detailed product requirements may be numbered as 3.1.1, 3.1.2, etc.

Enter a Business Topic using the project's standard. Refer to the TOC worksheet to find the
Business Topic that is appropriate for each Requirement ID. Copy the Business Topic from the TOC
worksheet to the Business Topic field on the High-level Requirements and the Product Requirements
worksheets. For example:
Requirement ID Business Topic
1 Application Functionality
2 Customer Support
3 Usability
Continue numbering for other business topics (see TOC worksheet for details)

The project can modify the types of Requirement IDs that can be entered and the Business Topics
that these requirements are mapped to by updating the TOC worksheet. To update the TOC
worksheet, click on the TOC Worksheet hyperlink.

Enter a Requirement Name.

Modified: 11/12/2024 06:44:36 Last modified by: User

6
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Enter a Short Description of the requirement.

Enter a Requirement Type. Choose from the list

Enter Requirement Sub-Type. Choose from the List.

Enter the requirement Priority. This can be L, M, or H (Low, Medium, or High):

Priority High (H) is the one which is Critical – cannot live without
Priority Medium (M) is the one which is Important – not critical but strongly desired
by stakeholders
Priority Low (L) is the one which is Optional – nice to have.

Enter The Release Number that will include this product requirement.

Ensure that the RTM is put under version control so that older versions of requirements can be
retrieved. Also, make updates as appropriate to Requirement Name, Short Description, and Long
Description columns.

Enter a Long Description of the requirement

Enter a Requirement Source, such as "SOW" for a requirement that came from the Statement of
Work or "JAD Session - 11/20/2005" for a requirement that resulted from a Joint Application
Development session on November 20, 2005.

Enter the Business/ Process Area to which the requirements belong to, such as Billing or Customer
Service Design

Enter the Status. The status can be Approved, Rejected, Deferred, In-Progress. Choose from the list.

Modified: 11/12/2024 06:44:36 Last modified by: User

7
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Enter the Owner of the requirement, stakeholder such as a team or person.

Enter Notes, as necessary.

Track Requirements The following fields on the RTM - Lifecycle Tracking worksheet have been pre-populated:
(RTM - Lifecycle Tracking worksheet) Project Name
Project Stage
Requirement ID
Short Description

To provide for requirements bi-traceability, the project may enter multiple rows for each.

To track requirements through the systems development lifecycle, complete the following information
for each requirement:

Enter the Release Number that will include this requirement.

Ensure that the RTM is put under version control so that older versions of requirements can be
retrieved. Also, make updates as appropriate to Requirement Name, Short Description, and Long
Description columns.

Enter the Priority of the requirement. Use H for high priority, M for medium priority, and L for low
priority.

Enter the High-level Requirement ID to create traceability to high-level requirements. If a

corresponding high-level requirement does not exist, put in the SOW Reference.

For the Analysis Stage:

Enter the Analysis Reference to track the requirements through the analysis stage. List the names or
the IDs that identify the analysis documents that resulted from the requirements.

Modified: 11/12/2024 06:44:36 Last modified by: User

8
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Enter the User Scenarios/Use Cases to track requirements through the analysis stage. List the
names or the IDs that identify the user scenario and/or use case documents that resulted from the
requirements.

Enter the Other Analysis Objects/Deliverables to track requirements through the analysis stage.
List the names or the IDs that identify these other analysis objects/deliverables that resulted from the
requirements.

For the Design Stage:

Enter the Design Reference to track the requirement through the design stage. List the names or the
IDs that identify the design documents that resulted from the requirements.

Enter the Design Objects/Deliverables to track the requirement through the design stage. List the
names or the IDs that identify the design objects/deliverables that resulted from the requirements.

For the Build Stage:

Enter the Code Module Reference to track the requirement through the build stage. List the names
or the IDs that identify the code modules that resulted from the requirements.

Enter the Interface Reference to track the requirement through the build stage. List the names or the
IDs that identify the interfaces that resulted from the requirements.

For the Test Stage:

Enter the Test Script Reference to track the requirement through the test stage. List the names or
the IDs that identify the test scripts that resulted from the requirements.

Modified: 11/12/2024 06:44:36 Last modified by: User

9
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Enter the Test Condition Reference to track the requirement through the test stage. List the names
or the IDs that identify the test conditions that resulted from the requirements.

Record Updates to Requirements As referenced in the project's CM Plan or Project Plan, controlling changes to requirements is a large
(High-level Requirements and Product part of the ensuring the requirement's integrity. To track changes to the project's requirements, enter
Requirements worksheet) the Change Request ID of the change request that has been approved to modify the requirement.

Ensure that the RTM is put under version control so that older versions of requirements can be
retrieved. Also, make updates as appropriate to Requirement Name, Short Description, and Long
Description columns.

Requirements Definitions and All requirements, including the high-level requirements created in the Plan stage and more detailed
Categories product and product component requirements created in Application, Technical Architecture, Training
and Performance Support, Service Introduction, and Deploy workstreams, need to be collected,
documented, verified, analyzed, prioritized, validated and accepted by the stakeholders, baselined,
and put under appropriate levels of configuration management. The types of requirements are shown
in Figure 1 below:

Modified: 11/12/2024 06:44:36 Last modified by: User

10
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

!!! Delete all these boxed instructions in the final version of your RTM !!!

Modified: 11/12/2024 06:44:36 Last modified by: User

11
©2009 Accenture. All Rights Reserved.
 Requirements Traceability Matrix

Requirement
s Definitions
and
Categories

sure that the RTW is put under version control.

Related Field
Requirements Definitions and Categories

Go to Project Name

Go to Project Stage

Modified: 11/12/2024 06:44:36 Last modified by: User

12
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Go to High-level Requirement ID

Go to Business Topic

Go to the TOC Worksheet

Go to High-level Requirement Name

Go to Short Description

Modified: 11/12/2024 06:44:36 Last modified by: User

13
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Go to Priority

Go to Release Number

Go to Long Description

Go to Requirements Source

Go to Business/ Process Area

Go to Status

Go to Owner

Go to Notes

Modified: 11/12/2024 06:44:36 Last modified by: User

14
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Go to Project Name

Go to Project Stage

Go to Requirement ID

Go to Business Topic

Go to the TOC Worksheet

Go to Requirement Name

Modified: 11/12/2024 06:44:36 Last modified by: User

15
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Go to Short Description

Go to Requirement Type

Go to Requirement Sub-Type

Go to Priority

Go to Release Number

Go to Long Description

Go to Requirements Source

Go to Business/ Process Area

Go to Status

Modified: 11/12/2024 06:44:36 Last modified by: User

16
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Go to Owner

Go to Notes

Go to Release Number

Go to Priority

Go to High-level requirement ID or SOW or B/U Reference

Go to Analysis Reference

Modified: 11/12/2024 06:44:36 Last modified by: User

17
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Go to User Scenarios/ Use Cases

Go to Other Analysis Objects/Deliverables

Go to Design Reference

Go to Design Objects/Deliverables

Go to Code Module Reference

Go to Interface Reference

Go to Test Script Reference

Modified: 11/12/2024 06:44:36 Last modified by: User

18
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Go to Test Condition Reference

Go to Change Request ID (High-level Requirements)

Go to Change Request ID (Product Requirements)

Modified: 11/12/2024 06:44:36 Last modified by: User

19
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Modified: 11/12/2024 06:44:36 Last modified by: User

20
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

High-level Requirements
Project Name: AAES XOG Oracle
Project Stage: <Enter the project stage>

Business Topic High-level

High-level
<Refer to the TOC Requirement Short Description Priority (L,M,H) Release Number Long Description
Requirement ID
Worksheet> Name
Organization Use of existing Ability to leverage the
Setup Business Group, if existing Business
Application any Group (BG)/HR
Functionality Structure
1
Organization Requires single
Application Setup ledger or multiple
Functionality ledgers
2
Organization Requirement of legal
Application Setup entities to be defined
Functionality
3
Organization Requirement of All transactions for
Setup Multiple Operating each Joint Venture
Units company must be
associated with their
own operating unit so
data such as project
information, purchase
Application orders and payables
Functionality should not be shared
across these
companies.

Modified: 11/12/2024 06:44:36 Last modified by: User

21
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

High-level Requirements
Project Name: AAES XOG Oracle
Project Stage: <Enter the project stage>

Business Topic High-level

High-level
<Refer to the TOC Requirement Short Description Priority (L,M,H) Release Number Long Description
Requirement ID
Worksheet> Name
Organization Requirement of All transactions for
Setup access control each Joint Venture
across various company must be
multiple operating associated with their
units own operating unit so
data such as project
information, purchase
Application orders and payables
Functionality should not be shared
across these
companies.

Modified: 11/12/2024 06:44:36 Last modified by: User

22
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Change
Requirement Business/
Status Owner Request Notes
Source Process Area
ID

Modified: 11/12/2024 06:44:36 Last modified by: User

23
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Change
Requirement Business/
Status Owner Request Notes
Source Process Area
ID

Modified: 11/12/2024 06:44:36 Last modified by: User

24
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Product Requirements
Project Name: <Enter the project name>
Project Stage: <Enter the project stage>

Business Topic
Requirement Requirement Sub
Requirement ID <Refer to the TOC Short Description Requirement Type Priority (L,M,H)
Name Type
Worksheet>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>
<Insert <Insert Business
Requirement ID> Topic>

Modified: 11/12/2024 06:44:36 Last modified by: User

25
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Change
Requirement Business/
Release Number Long Description Status Owner Request Notes
Source Process Area
ID

Modified: 11/12/2024 06:44:36 Last modified by: User

26
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Requirements Traceability Matrix

NOTE: The Requirement ID, Short Description, Release Number and Priority columns are linked with
the Requirements ID field on the Product Requirements worksheet. These field will pre-populate by the
respective column on the Product Requirements worksheet.

To provide for requirements bi-traceability, the project may enter multiple rows for each requirement ID
so as to track each Requirement to the multiple design documents, module code references, and test
scripts/conditions that result from it.

Project Stage: <Enter the project stage>

Product Requirements Analysis Stage
High-level
Other Analysis
Short Release Priority Requirement ID Analysis User Scenarios/
Requirement ID Objects/
Description Number (H, M, L) or SOW Reference Use Cases
Deliverables
Reference
<Insert Requirement ID>
<Insert Requirement ID>
<Insert Requirement ID>
<Insert Requirement ID>
<Insert Requirement ID>
<Insert Requirement ID>
<Insert Requirement ID>
<Insert Requirement ID>
<Insert Requirement ID>

Modified: 11/12/2024 06:44:36 Last modified by: User

27
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Design Stage Build Stage Test Stage

Design Test
Design Code Module Interface Test Script
Objects/ Condition
Reference Reference Reference Reference
Deliverables Reference

Modified: 11/12/2024 06:44:36 Last modified by: User

28
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

How to Use the TOC Worksheet

The TOC Worksheet lists all Business Topics and their corresponding Requirement IDs. For example, all
Requirement IDs that begin with 1 will correspond to the Application Functionality business topic. Further, a
requirement with an ID of 1.4.7 will correspond to the Application Functionality business topic as well. Both the
Requirement Begins With and the Business Topic columns can be modified to reflect the project's standards.

For example, if the project agrees to have requirements that begin as R1, R2, R3, etc., then modify the values in
the Requirement Begins With column to include these values. Type the new requirement number on the same
row as the business topic to which it corresponds.

To modify the Business Topic that is associated with a corresponding Requirement Begins With column, type the
new topic in the Business Topic column. Type the topic on the same row as the requirement to which it
corresponds.

Requirement
Business Topic
Begins With
1 Application Functionality
2 Customer Support
3 Usability
4 Page Layout and Configuration
5 Content Management and Production
6 System Administration
7 Technical Architecture Security
8 Technical Architecture Standards
9 Interface Requirements
10 <Insert Other Requirement Topic #1>
11 <Insert Other Requirement Topic #2>
12 <Insert Other Requirement Topic #3>
13 <Insert Other Requirement Topic #4>
14 <Insert Other Requirement Topic #5>

Modified: 11/12/2024 06:44:36 Last modified by: User

29
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Requirement
Business Topic
Begins With
15 <Insert Other Requirement Topic #6>
16 <Insert Other Requirement Topic #7>
17 <Insert Other Requirement Topic #8>
18 <Insert Other Requirement Topic #9>
19 <Insert Other Requirement Topic #10>
20 <Insert Other Requirement Topic #11>
21 <Insert Other Requirement Topic #12>
22 <Insert Other Requirement Topic #13>
23 <Insert Other Requirement Topic #14>
24 <Insert Other Requirement Topic #15>
25 <Insert Other Requirement Topic #16>
26 <Insert Other Requirement Topic #17>

Modified: 11/12/2024 06:44:36 Last modified by: User

30
©2009 Accenture. All Rights Reserved.
Requirements Traceability Matrix

Revision History

Date Version Description Author

Modified: 11/12/2024 06:44:36 Last modified by: User

31
©2009 Accenture. All Rights Reserved.