Neuromodulation System Integration Program

SAP Interfaces
Test Plan

THESE DOCUMENTS ARE THE PROPERTY OF BOSTON SCIENTIFIC CORPORATION AND

SHALL NOT BE REPRODUCED, DISTRIBUTED, DISCLOSED OR USED FOR
MANUFACTURE OR SALE OF APPARATUS WITHOUT THE EXPRESS WRITTEN CONSENT
OF BOSTON SCIENTIFIC CORPORATION.
Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 1 of 9
 Table of Contents
1. INTRODUCTION 4
1.1. Document Objectives and Scope 4
1.2. References 4
1.3. Special Issues 4
1.4. Terminology 4

2. PROJECT TEST PLAN 5

2.1. Test Scope 5
2.2. Test Strategy 5
2.3. Test Objectives 5
2.4. Project Risks, Issues, and Dependencies 5

3. TEST SCHEDULE 5

4. TEST ACTIVITIES 6

5. TEST DELIVERABLES 6

6. TEST RESPONSIBILITIES 7
6.1. Test Resources 7
6.2. Test Tools 7
6.3. Test Environments and Test Repository 7

7. TEST SPECIFICATION TYPES 8

7.1. OTSS Test Specification 8
7.2. Unit Test Specification 8
7.3. Integration Test Specification 8
7.4. System Test Specifications 9
7.4.1. Functional Tests 9
7.5. Acceptance Test Specification 9

8. TEST RESULTS 9

9. TEST REPORTS 9

10. DEFECT AND ISSUE TRACKING 9

11. TRACEABILITY 9

Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 2 of 9
12. FINAL TEST REPORT 9

13. EXECUTION CRITERIA 9

14. Exit Criteria 10

Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 3 of 9
1. INTRODUCTION

1.1. Document Objectives and Scope

The goal of this document is to explain the test methodology for the SAP Interfaces to
the six Neuromodulation-specific 3rd-party applications: BN2.0, Clientele, Clippership,
MediSoft, NetRegulus/NetRM, and Sales Accelerator. Existing Legacy SAP interfaces
are not in scope.

1.2. References
Document Title
Number
90343083 Construction Phase
90343084 Implementation Phase
90343080 Testing Process
90343103 Test Report Template
90343102 Test Specification Template

1.3. Special Issues

Not applicable.

1.4. Terminology
Term Definition
Objective A specific goal that the group of tests is designed to
accomplish.

Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 4 of 9
2. PROJECT TEST PLAN

2.1. Test Scope

The scope of the SAP Interface testing is the transmission of the data from SAP to the
application (for both unidirectional and bi-directional interfaces) and from the application
to SAP (for bi-directional interfaces). These tests will not cover the creation of the data
either in SAP or in the application.
The testing will be done in accordance with the respective System Software
Requirements documents. These tests cover only the integration/UAT testing phase.

2.2. Test Strategy

The overall strategy of this testing initiative is manual, black box testing. We are testing
only the data interface part and not the systems at either end of that interface. The
testing at the SAP end of the interface will be covered by the SAP functional testing. On
the application side, there is no change; therefore, no testing will be done specifically on
that end other than the data comes across and is readable by the application. All testing
covered in this document is integration/UAT testing.
Some of the test specifications use test data which needs to be set-up in the SAP test
environment prior to executing the test cases.

2.3. Test Objectives

The general test objectives are to test the correctness of the generation of the interface
data file, the content of the interface data file, and any error conditions.

2.4. Project Risks, Issues, and Dependencies

The follow Risk(s) could have a potential impact on the testing schedule:
 The ability to test the BN 2.0 (Product Activation Portal) Interface is
dependent of the completion of the development of the Product Activation
Portal. In the event the Product Activation Portal has not completed
development at the time the test case is to be executed, there is a risk that the
interface testing for this application will not be done on time. The Product
Activation Portal development must be completed before the beginning of the
first functional test (see section 3 Test Schedule).

3. TEST SCHEDULE
The Integration/UAT testing of the SAP Interfaces shall be done in conjunction with the
NMSIP Functional Testing. The NMSIP Test Schedule can be found in the
Neuromodulation Systems Integration SharePoint: http://valweb01/is/sapproj/SAP
%20Documentation/Forms/AllItems.aspx in the Testing folder under Test Schedule.

Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 5 of 9
4. TEST ACTIVITIES
 Creation of the test plan
 Creation of test specifications
 Identification of test environments
 Creation of test data
 Performing test execution and documenting results
 Creation of test reports

5. TEST DELIVERABLES
 BN2.0-SAP Interface Test Specification
 Clientele-SAP Interface Test Specification
 Clippership-SAP Interface Test Specification
 MediSoft-SAP Interface Test Specification
 NetRegulus-SAP Interface Test Specification
 Sales Accelerator-SAP Interface Test Specification

 BN2.0-SAP Requirements Trace Matrix

 Clientele-SAP Requirements Trace Matrix
 Clippership-SAP Requirements Trace Matrix
 MediSoft-SAP Requirements Trace Matrix
 NetRegulus-SAP Requirements Trace Matrix
 Sales Accelerator-SAP Integration Trace Matrix

 BN2.0-SAP Integration Test Report

 Clientele-SAP Integration Test Report
 Clippership-SAP Integration Test Report
 MediSoft-SAP Integration Test Report
 NetRegulus-SAP Integration Test Report
 Sales Accelerator-SAP Integration Test Report

 BN2.0-SAP Integration Final Test Report

 Clientele-SAP Integration Final Test Report
 Clippership-SAP Integration Final Test Report

Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 6 of 9
  MediSoft-SAP Integration Final Test Report
 NetRegulus-SAP Integration Final Test Report
 Sales Accelerator-SAP Integration Final Test Report

 Project Test Summary Report

6. TEST RESPONSIBILITIES

Table 1. Roles and Responsibilities

Role/Project Members Responsibility
Project Manager Track testing to project schedule.
Test Coordinator Coordinates all test activities and accumulation
of test results.
Business System Analysts Write Test Plan and Test Specifications.
Customer Role Review and Approve Business Process
Requirements and System Software
Requirements.
Test Team Execute Test Cases
Development Team Code software according to the System
Software Requirements (SSR).
SQA Review and approve Test Plan, Test
Specifications, Requirements Trace Matrix
(RTM), and Test Report.

6.1. Test Resources

BN2.0: Clinician’s Programmer (CP), Implantable Pulse Generator (IPG)
Clippership: FedEx test server (virtual machine license), scale, scanner
Sales Accelerator: Handheld with scanner, label printer.

6.2. Test Tools

Not Applicable.

6.3. Test Environments and Test Repository

The Test Environments and the Test Repository are outlined below:
 System Testing will be conducted on the SAP Test Environment. (Informal)
 Integration/UAT will be conducted on the SAP CNV Environment.
 Post Production Verification Testing will be conducted on the SAP Production
Environment.
Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 7 of 9
 Upon a successful completion of System Test, Integration/UAT and PPV, the test results
will be stored in PDM
BN2.0: valapp18 and valtest18.advancedbionics.com
Clientele: \\ab_sql01X\Program Files\Epicor\Clientele 7.3\CTELWIN.EXE
Clippership: Stand-alone HP-UX Samson B.11.00 U
MediSoft: \\absqltest\Medidata\BSC
NetRegulus: \\ab_sql01x\ pqi_production_test database
Sales Accelerator: Test FTP site DNS Name Server: 64.72.140.10 (ftp.noink.net)
SAP: Functional Testing will be done in the CNV environment
All test specifications will be stored in PDM. The specific PDM numbers will be
referenced in each individual interface SCR.

7. TEST SPECIFICATION TYPES

This test plan covers the Formal Integration/UAT testing. At this time, no determination
has been made as to whether PPV testing will be formal or informal.

7.1. OTSS Test Specification

Not Applicable.

7.2. Unit Test Specification

Unit testing will be conducted by the CRM EAI development team informally as part of
the development of the interfaces.

7.3. Integration Test Specification

The Integration/UAT testing shall be performed during the Construction Phase of the
project. There shall be a total of seven Test Specifications written: one for each of the
interfaces except for Sales Accelerator, which shall have one for the export files and
one for the import files.

7.4. System Test Specifications

Because the scope of this project is limited to the application interfaces and is not a
complete system, involving only the creation, transmission and consumption of the data,
there will be no formal System Testing.

7.4.1. Functional Tests

Functional tests, related to the interfaces, which shall be performed on the SAP
side, shall be discussed in the SAP System Test Specifications.
Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 8 of 9
 7.5. Acceptance Test Specification
The Acceptance Test Specification will be combined with the Integration Test
Specification. The Acceptance testing will be executed after the final integration test.

8. TEST RESULTS
The manually executed test specifications and resulting printed objective evidence shall
be given to the Test Coordinator. Any issues or deviations shall be documented, as well
as the evaluated results of the executed test cases, in the Test Summary Report.

9. TEST REPORTS
Individual Test Reports shall be created for each of the interfaces and shall be stored in
PDM. The specific PDM numbers will be referenced in each individual interface SCR.

10. DEFECT AND ISSUE TRACKING

The Accenture Delivery Tool (ADT) will be used for issue bugs/defects management and
traceability.

11. TRACEABILITY
Traceability will be documented in the Requirements Trace Matrix which shall be stored
in PDM. The specific PDM numbers will be referenced in each individual interface SCR.

12. FINAL TEST REPORT

Final Test reports shall be generated for each of the interfaces and shall stored in PDM.
A Project Test Summary Report which summarizes all interfaces shall be created and
shall be stored in PDM.

13. EXECUTION CRITERIA

Test execution can begin when the Functional testing begins for the SAP project.

14. EXIT CRITERIA

Testing will be complete when all the necessary parties from the technical side and the
business agree that the test results are satisfactory.

Boston Scientific
SAP Interfaces Test Plan
90552556 Rev/Ver AA
Page 9 of 9