8/8/2019 Sample 2 Requirements Trace Ability Matrix

1/28

1

v0.1

4/5/2009

ID Legend

B - Business RequirementNF - Non-Functional Requirement

F - Functional Requirement

T - Technical Requirement

ID Requirement Type Maps To Owner(s)

Interface Feed

7.1.1. Business

7.1.2. Business

7.1.3. The data on these feeds will be at a transactional level. Business

7.1.4. The feed must be created at the lowest level available. Business

7.1.5. Business

7.1.6. Business

7.1.7. Business

7.1.8. Business

Billing System reports

7.4.5.3.1. Business

Note: The purpose of the matrix is to help ensure the object/scope item of the requirements conforms to the requirements by associating etraceability matrix.The matrix is used to verify that all stated and derived requirements are allocated to system components and other deliverables as well as The matrix is also used to ensure all requirements are met and to locate affected system components when there is a requirements changethe impact of requirements changes on the system to be determined, facilitating cost, benefit, and schedule determinations.

OwningArea(s)

Each billing system as listed under section 5.1 (ACR) of this document willcreate and send a feed into the FDM.

The FDM will receive data daily from the billing systems. Some systems mayhave monthly feeds as a part of their monthly process. In such cases, theFDM will receive data as it becomes available.

Each transaction will have an identifier (Billing Transaction Group Code &Billing Transaction Code) which will form the basis of downstream logicwhich will apply GEAC accounts and other details

Certain operational data will be required. A detailed list of data elements willbe provided to the source system SMEs (see hyperlink in references section1.0 or Appendix 1)

A one time load that shows the as of (that day) outstanding premium

receivables balance will be needed once the FDM goes live. This balance isat a policy or account level.

The billing systems will save copies of the feed files in the FDM. Last 60 filesshould be saved.

Each billing system will create a daily compare report that shows theoutstanding receivable at the end of the day.

8/8/2019 Sample 2 Requirements Trace Ability Matrix

2/28

2

ID Requirement Type Maps To OwnerOwningArea(s)

7.4.5.3.1. Business

7.4.5.3.1. Business

7.4.5.3.1. Any exceptions will be shown through this report. Business

7.4.5.3.1. This compare is at the lowest level available. Business

7.4.5.3.2. Business

7.4.5.3.3. Business

The process will take the prior days ending balance, show all transactionsfrom the current day that impact receivables and calculate the endingreceivable.

This report will compare the calculated receivable to the receivable reportedthrough the feed file to FDM.

Month end balancing report will compare the change in outstandingreceivable in each billing system between current month and prior month tothe total in the FDM.

An activity report is needed from the billing system daily & monthly. Thisreport will show the billing system activity for the day and/or month. This is adetailed report at a transaction level.

8/8/2019 Sample 2 Requirements Trace Ability Matrix

3/28

3

ID Requirement Type Maps To OwnerOwningArea(s)

8/8/2019 Sample 2 Requirements Trace Ability Matrix

4/28

4

ID Requirement Type Maps To OwnerOwningArea(s)

8/8/2019 Sample 2 Requirements Trace Ability Matrix

5/28

5

ID Requirement Type Maps To OwnerOwningArea(s)

8/8/2019 Sample 2 Requirements Trace Ability Matrix

6/28

6

ID Requirement Type Maps To OwnerOwningArea(s)

8/8/2019 Sample 2 Requirements Trace Ability Matrix

7/28

7

ID Requirement Type Maps To OwnerOwningArea(s)

8/8/2019 Sample 2 Requirements Trace Ability Matrix

8/28

8

ID Requirement Type Maps To OwnerOwningArea(s)

8/8/2019 Sample 2 Requirements Trace Ability Matrix

9/28

v0.1

4/5/2009

Business Rules

ID Business Rules Maps To Date

Interface Feed

7.1.3 7.1.3

Billing System reports

Balanced entries are not needed as these will be assigned in the FDM basedon pre-defined accounting logic.

8/8/2019 Sample 2 Requirements Trace Ability Matrix

10/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

11/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

12/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

13/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

14/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

15/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

16/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

17/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

18/28

Active/Retired

8/8/2019 Sample 2 Requirements Trace Ability Matrix

19/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

20/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

21/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

22/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

23/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

24/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

25/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

26/28

8/8/2019 Sample 2 Requirements Trace Ability Matrix

27/28

RTM Change Management Process

Once the BRS, SRS and the RTM documents have been authorized, the requirements will be locked down. No c

a) Requirements Change Notice must be sent to Requirements Owner (via email)b) Requirements Owner will analyze impacts to existing requirementsc) If impacts exist, Requirements Owner will discuss with impacted Requirements Owners and received) If no impacts exist, Requirements Owner will approve Requirements Change Noticee) Notification must be sent to owner of RTM to document the requirements change.

8/8/2019 Sample 2 Requirements Trace Ability Matrix

28/28

hanges will be allowed to the stated requirements without going through the approval process below:

their approval with Requirements Change