Attachment_2_Beta_Test_Site_Agreement.pdf

Indian Health Service Beta Test Agreement

Service Unit

Namespace Page 1 of 4 Form revised 04/07/2017

RPMS Beta Test Agreement Namespace

The Service Unit has been proposed as a beta test site for Namespace. This document formalizes the conditions of the beta test and documents agreement by the parties affected by the testing process. As a beta test site, your facility will assume a key role in verifying the software works properly and is compatible in a live and unique environment with other RPMS packages. While the developer has made every effort to ensure the application functions as it is designed to, there is always a risk of latent issues discoverable only by the beta testing process.

Scope of Prior Testing This application has been tested in both the development and alpha test environments. It has not been tested in a production environment at field facilities.

Scope of Verification and Release Management Software Quality Assurance (SQA) has received the required application files and has conducted a baseline review with satisfactory results. SQA Release Management will receive the following items prior to releasing beta test files:

• SQA baseline review document

• Application software test version (t1)

• Application documentation (t1) o Installation Guide and Release Notes o User and Technical Manuals

• Test scripts, checklists, and beta test plan

• Signed Beta Test Agreement(s)

Test Period The beta test period will officially begin when the software package is installed in a test or production environment at all beta test sites and will officially end when it has operated in production at all beta sites without significant changes (as determined by the RPMS Program Office) for thirty days.

During testing, each beta test site will complete the beta test checklists provided by the project team.

When testing is complete, the site will be asked to endorse the software package for national release.

Scope of Testing Required The application being tested is categorized as a Refer to superscript #1 on TRM effort project. OIT estimates beta testing will require Refer to superscript #2 on TRM level of effort (LOE) from Service Unit (spread out over the entire beta period). The entire beta period is estimated to be completed in Refer to superscript #6 on TRM. It is expected testing will occur first on your test environment to ensure there are no problems, and then on your production environment to acquire real usage.

Namespace Page 2 of 4 Form revised 04/07/2017

Estimated Time Frame OIT estimates this software/process will be ready for beta test on Refer to superscript #4 on TRM.

OIT estimates this beta effort will require about Refer to superscript #5 on TRM test builds throughout the process.

Roles and Responsibilities SQA Release Management will provide the software and related documentation to the beta test sites.

Any software modifications to Namespace to be distributed during the test period will also be provided through SQA Release Management.

During the beta test period, the Namespace team will provide any necessary training and primary support for the package. The developer and/or project team requires system access to support investigation and problem resolution. Service Unit’s RPMS staff will provide the limitations and requirements for this access. Any emergency fixes required by the site must be reported promptly to the project team, who will coordinate all necessary modifications to the software. Local fixes or enhancements must not be implemented in order to preserve the reliability and integrity of the test.

Development Project Team Responsibilities Prior to testing, the development project team will be responsible for the following.

• Test the application in all appropriate environments at the levels of detail necessary to ensure quality.

• Establish a communication process for beta testing feedback and communicate this process to the beta test sites.

• Establish testing guidelines specific to the application being tested. This includes identifying system requirements, software prerequisites, licenses, or any other special considerations the sites must address in order to test the software package.

During testing, the development project team will be responsible for the following.

• Provide application training and support to testing sites.

• Address beta test site feedback.

• Provide updated test versions to SQA Release Management for distribution as required.

• Coordinate all emergency fixes related to the test package required by the site.

• Coordinate all necessary updates to application documents based on any fixes or modifications made as a result of testing.

• Determine when sufficient testing has been completed.

SQA Release Management Responsibilities

• Prepare and generate the Beta Test Agreement(s) (BTA - this document) to the test site(s), and collect the final endorsed documents from the site(s).

• Distribute software to the test site(s).

Namespace Page 3 of 4 Form revised 04/07/2017

SQA Verification Responsibilities

• Priority review of new test builds.

Beta Test Site Responsibilities Prior to testing, the beta test site will be responsible for the following.

• Identify the package test coordinator who will be involved in operational use of the package and will be responsible for local implementation and oversight of the application. Provide adequate hardware for users testing the package, and ensure all software prerequisites and other infrastructure considerations specified by the project team have been addressed.

• Approve/complete an ITAC request, submitted by SQA on behalf of the Development Project Team, to provide them access to the test site’s RPMS environment(s).

• Promptly install all software related to the package once received. Test software should be installed on a test system within one week of receiving it and on the production system no more than two weeks after test system installation. For tracking purposes, please notify the development federal project team lead and SQA Release Management when production use of the software begins. If the site identifies significant barriers to installation in production, inform the project team, who will determine whether it is appropriate for the facility to continue as a beta test site.

During testing, the beta site will be responsible for the following.

• Verify the application against items in the beta test checklists provided.

• Participate in all related conference calls.

• Report all problems and details about their occurrence to the developer, federal project team lead, and SQA Release Management promptly.

After testing is complete, the beta site will be responsible for the following.

• Complete and return the beta check list and national release endorsement form(s).

• Approve/complete an ITAC request, submitted by SQA on behalf of the Developmental

Project Team, to remove their access to the test site’s RPMS environment(s).

Namespace Page 4 of 4 Form revised 04/07/2017

Agreement If you are willing to participate in beta testing Namespace, and accept the conditions and responsibilities outlined above, please sign and email this form as a PDF to OITSQA@ihs.gov.

Please direct questions regarding this agreement to Refer to superscript #3 on TRM at phone number Refer to superscript #3 on TRM.

, OIT Federal Project Lead Date

, OIT SQA Team Lead Date

, Site Manager Date

, Lead Site Tester Date

, Site Chief Executive Officer Date

, Area Information Systems Coordinator Date mailto:OITSQA@ihs.gov