Test Traceability The scope of testing has been validated by use of a Test Traceability Matrix (TTM), setting out how each requirement within SEC Sections E, G, H and L and the Testing Baseline Requirements Document is met. BEIS first produced the Testing Baseline Requirements Document (TBRD) in 2015, setting out the subsidiary documents that form the testing requirements baseline. DCC established a project to ensure that testing be able demonstrate coverage of the requirements within the TBRD. The key components of that project were: A project board, formed of representatives from DCC, Systems Integrator, BEIS and the SIT Auditor; and A working group, formed of the DCC, Systems Integrator, with support from BEIS. Each of the requirements within each of the documents listed in the TBRD has been recorded within spreadsheets. DCC has assessed whether and where each is tested. The Systems Integrator has set out the test scenarios and test scripts along with a mapping between the requirements and the scenarios / scripts a Test Traceability Matrix – (TTM). These scenarios, scripts and the mapping have been assured by DCC supported by BEIS. The Systems Integrator performs testing by running test scripts and records the results and logs in the test tool, HP ALM. Test results are assured through a range of activities including test observation, witnessing and inspection of results. The results of testing have been presented to the Test Assurance Board, which confirmed that testing aligns with contracts and the Joint Test Strategy and that agreed defect thresholds had not been exceeded. The TTM provides further assurance that testing aligns with the SEC, SIT Approach Document and TBRD. The TAB has issued Test Completion Certificates. The SIT Auditor has been engaged throughout the lifetime of the TTM project and has had visibility of the approach and the outcomes of the work. The SIT Auditor has taken a sampling approach to assessing the TTM project. The TTM spreadsheets have been attached in the SIT Completion Report for the Region, set out: Which requirements are testable and where; A mapping between requirement and test scenario; A description of the scenario; Test scripts and test logs are held within HP ALM. The information is not replicated in this report, given that it would be a repetition of a report provided with this report and the primary focus of the Test Traceability Matrix is SIT.
Test Traceability The scope of testing has been validated by use of a Test Traceability Matrix (TTM), setting out how each requirement within SEC Sections E, G, H and L and the Testing Baseline Requirements Document is met. BEIS first produced the Testing Baseline Requirements Document (TBRD) in 2015, setting out the subsidiary documents that form the testing requirements baseline. DCC established a project to ensure that testing be able demonstrate coverage of the requirements within the TBRD. The key components of that project were: A project board, formed of representatives from DCC, Systems Integrator, BEIS and the SIT Auditor; and A working group, formed of the DCC, Systems Integrator, with support from BEIS. Each of the requirements within each of the documents listed in the TBRD has been recorded within spreadsheets. DCC has assessed whether and where each is tested. The Systems Integrator has set out the test scenarios and test scripts along with a mapping between the requirements and the scenarios / scripts – a Test Traceability Matrix (TTM). These scenarios, scripts and the mapping have been assured by DCC supported by BEIS. The Systems Integrator performs testing by running test scripts and records the results and logs in the test tool, HP ALM. Test results are assured through a range of activities including test observation, witnessing and inspection of results. The results of testing have been presented to the Test Assurance Board, which confirmed that testing aligns with contracts and the Joint Test Strategy and that agreed defect thresholds had not been exceeded. The TTM provides further assurance that testing aligns with the SEC, SIT Approach Document and TBRD. The TAB has issued Test Completion Certificates. The SIT Auditor has been engaged throughout the lifetime of the TTM project and has had visibility of the approach and the outcomes of the work. The SIT Auditor has taken a sampling approach to assessing the TTM project. The TTM spreadsheets have been attached in the SIT Completion Report for the Region, set out: Which requirements are testable and where; A mapping between requirement and test scenario; A description of the scenario; Test scripts and test logs are held within HP ALM. The information is not replicated in this report, given that it would be a repetition of a report provided with this report and the primary focus of the Test Traceability Matrix is SIT.
dcc_interim_test_completion_report_-_region_cs_-_it_for_r12_v10_published.docx