The following templates and document specifications have been included in the Systems Solution package:

1.SSE_traceability_example v2.0

This document example showcases a couple of ways to include traceability information in a report document. The report first shows DOORS requirement object information for a specified system requirements module. A count of the number of linked test cases and work items is shown for each requirement object. The requirement ID is a clickable hyperlink to Appendix A, which is a traceability matrix. Appendix A is a concise list of each requirement with its linked RTC and RQM artifacts. The RTC and RQM artifact IDs are clickable hyperlinks to Appendices B and C, which show more details of the artifact. This document shows how you can include related artifact information in your report documents.

1.1 Included Example Files

• SSE_traceability_example v2.0.dsx - Document specification for this example. This specification points to the rational_cover_page.dta and SSE_traceability_example v2.0.dta templates to produce the SSE_traceability_example v2.0.doc file.
• SSE_traceability_example v2.0.dta - Document template for this example. You must specify the URI and credentials for the "DOORS_SRS" data source. The URI for the other data sources are dynamically configured in the template. You must specify appropriate credentials for the WI_ccm (RTC login) and VersionedTC_qm (RQM login) data sources. Always leave the TC_qm data source empty.
• SSE_traceability_example v2.0.doc - This is the Word 2003 output file that is produced by a document generation. To produce this output you must use the rpe.dot Word style sheet that is provided in the installation home directory of any RPE Launcher installation.

1.2 URI properties for the Document Specification

In the SSE_traceability_example v2.0.dsx document specification, specify these URI properites:

1. Configure the DOORS_SRS - DOORS data source as described in the DOORS Data Source section of Using the RPE Report Templates. To see traceability, you must specify a module that has established "Validated by" and/or "Implemented by" relationships.
2. Provide RTC login credentials to the WI_ccm data source.
3. Provide RQM login credentials to the VersionedTC_qm data soruce.

2. SystemReqSpec_Test_Coverage

This document example showcases requirements covered by test from the perspective of a DOORS requirements module. For each requirement in the module if a link to a test case exists, the test case ID is given. If a test case is not linked to a requirement, a red warning indicator is given. At the top of the document several module properties are listed, including baseline information. A metric for the total requirements covered by test cases in the module is also provided.

2.1 Included Example Files

• SystemReqSpec_Test_Coverage.dsx - Document specification for this example. This specification points to the rational_cover_page.dta and SystemReqSpec_Test_Coverage.dta templates to produce the SystemReqSpec_Test_Coverage.doc file.
• SystemReqSpec_Test_Coverage.dta - Document template for this example. You must specify the URI and credentials for the "DOORS_SRS" data source. The URI for the other data sources are dynamically configured in the template. You must specify appropriate credentials for the VersionedTC_qm (RQM login) data source. Always leave the TC_qm data source empty.
• SystemReqSpec_Test_Coverage.doc - This is the Word 2003 output file that is produced by a document generation. To produce this output you must use the rpe.dot Word style sheet that is provided in the installation home directory of any RPE Launcher installation.

2.2 URI properties for the Document Specification

In the SystemReqSpec_Test_Coverage.dsx document specification, specify these URI properties:

1. Configure the DOORS_SRS - DOORS data source as described in DOORS Data Source section of Using the RPE Report Templates. To see test coverage, you must specify a module that has established "Validated by" relationships.
2. Provide RQM login credentials to the VersionedTC_qm data soruce

3. TestPlan_Requirements_Coverage

This document example showcases test coverage of requirements from the perspective of an RQM test plan. For each test plan in the specified project, a list of test cases and which requirement(s) the test case verifies is provided. Included in the first page of the document is a summary count for each test plan of how many test cases are in the plan and how many requirements are tested by those test cases.

3.1 Included Example Files

• TestPlan_Requirements_Coverage.dsx- Document specification for this example. This specification points to the rational_cover_page.dta and TestPlan_Requirements_Coverate.dta templates to produce the TestPlan_Requirements_Coverate.doc file.
• TestPlan_Requirements_Coverage.dta - Document template for this example. You must specify the URI and credentials for the "TP_feed" data source. The URI for the other data source is dynamically configured in the template. Always leave the TC_qm data source empty.
• TestPlan_Requirements_Coverage.doc - This is the Word 2003 output file that is produced by a document generation. To produce this output you must use the rpe.dot Word style sheet that is provided in the installation home directory of any RPE Launcher installation.

3.2 URI properties for the Document Specification

In the TestPlan_Requirements_Coverage.dsx document specification, specify these URI properties:

1. Configure the "TP_feed" data source as described in RQM Data Source section of Using the RPE Report Templates. The URI should be a feed for test plans in your RQM database (either in the default project, a specific project, a specific test plan, etc.).