You are on page 1of 28

<78323A- GL Receivables III (ACR) SAMPLE>

v0.1 4/5/2009

Note: The purpose of the matrix is to help ensure the object/scope item of the requirements conforms to the requirements by associating each requirement with the object/scope item via the traceability matrix. The matrix is used to verify that all stated and derived requirements are allocated to system components and other deliverables as well as to determine the source of requirements. The matrix is also used to ensure all requirements are met and to locate affected system components when there is a requirements change. The ability to locate affected components allows the impact of requirements changes on the system to be determined, facilitating cost, benefit, and schedule determinations. ID Legend
B - Business Requirement NF - Non-Functional Requirement F - Functional Requirement T - Technical Requirement

ID Interface Feed 7.1.1.

Requirement

Type

Maps To

Owning Area(s)

Owner(s)

Date

Active/ Retired

Software Module/Code

Level of Test

Test Case # Verification

Modified Field/Code

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

Business

7.1.2. 7.1.3. 7.1.4.

The FDM will receive data daily from the billing systems. Some systems may have monthly feeds as a part of their monthly process. In such cases, the FDM will receive data as it becomes available. Business The data on these feeds will be at a transactional level. The feed must be created at the lowest level available. Each transaction will have an identifier (Billing Transaction Group Code & Billing Transaction Code) which will form the basis of downstream logic which will apply GEAC accounts and other details Business Business

7.1.5.

Business

7.1.6.

Certain operational data will be required. A detailed list of data elements will be provided to the source system SMEs (see hyperlink in references section 1.0 or Appendix 1) Business 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 is at a policy or account level. Business The billing systems will save copies of the feed files in the FDM. Last 60 files should be saved. Business Billing System reports

7.1.7. 7.1.8.

7.4.5.3.1.

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

Business

1

ID

Requirement The process will take the prior days ending balance, show all transactions from the current day that impact receivables and calculate the ending receivable.

Type

Maps To

Owning Area(s)

Owner(s)

Date

Active/ Retired

Software Module/Code

Level of Test

Test Case # Verification

Modified Field/Code

7.4.5.3.1.

Business

7.4.5.3.1.

This report will compare the calculated receivable to the receivable reported through the feed file to FDM. Business

7.4.5.3.1. 7.4.5.3.1.

Any exceptions will be shown through this report. This compare is at the lowest level available.

Business Business

7.4.5.3.2.

Month end balancing report will compare the change in outstanding receivable in each billing system between current month and prior month to the total in the FDM. Business An activity report is needed from the billing system daily & monthly. This report will show the billing system activity for the day and/or month. This is a detailed report at a transaction level. Business

7.4.5.3.3.

2

ID Requirement Type Maps To Owning Area(s) Owner(s) Date Active/ Retired Software Module/Code Level of Test Test Case # Verification Modified Field/Code 3 .

ID Requirement Type Maps To Owning Area(s) Owner(s) Date Active/ Retired Software Module/Code Level of Test Test Case # Verification Modified Field/Code 4 .

ID Requirement Type Maps To Owning Area(s) Owner(s) Date Active/ Retired Software Module/Code Level of Test Test Case # Verification Modified Field/Code 5 .

ID Requirement Type Maps To Owning Area(s) Owner(s) Date Active/ Retired Software Module/Code Level of Test Test Case # Verification Modified Field/Code 6 .

ID Requirement Type Maps To Owning Area(s) Owner(s) Date Active/ Retired Software Module/Code Level of Test Test Case # Verification Modified Field/Code 7 .

ID Requirement Type Maps To Owning Area(s) Owner(s) Date Active/ Retired Software Module/Code Level of Test Test Case # Verification Modified Field/Code 8 .

1. 7.GL Receivables III (ACR) SAMPLE> v0.1.1 4/5/2009 Business Rules ID Interface Feed 7.<78323A.3 Business Rules Maps To Date Balanced entries are not needed as these will be assigned in the FDM based on pre-defined accounting logic.3 Billing System reports .

.

.

.

.

.

.

.

.

Active/ Retired .

.

.

.

.

.

.

.

.

No changes will be a)       Requirements Change Notice must be sent to Requirements Owner (via email) b)       Requirements Owner will analyze impacts to existing requirements c)       If impacts exist. SRS and the RTM documents have been authorized. Requirements Owner will discuss with impacted Requirements Owners and receive their approva d)       If no impacts exist. . Requirements Owner will approve Requirements Change Notice e)       Notification must be sent to owner of RTM to document the requirements change.RTM Change Management Process Once the BRS. the requirements will be locked down.

No changes will be allowed to the stated requirements without going through the approval process below: s and receive their approval with Requirements Change .down.