Attachment_1_TRM-Template.xls

TRM TEMPLATE

THE FOLLOWING REFERENCE MATERIAL PROVIDES INSTRUCTIONS ON FILLING OUT THE FIELDS AND CLARIFIES WHAT IS REQUIRED.

(1) Excel comments - Run cursor over red arrowhead to view instructions/notes

(2) PowerPoint shows at each section (column V)

(3) Supporting documents within the tabs labeled: Site Rep's, Level of Effort, and Active Test Sites

(4) Save this document as a "macro-enabled worksheet". Naming Convention: TRM_Namespace_Application Name, version (v)#, patch (p)#_yyyy-mm-dd.

Example for ABM Third Party Billing Version 40, Patch 1: TRM ABM-TPBv40p1_2018-12-31

&C&"Times New Roman,Bold"&18Application Testing and Release Management Worksheet (TRM) &LTRM-Template2411 (1/23/2015)&C&P of &N&RSoftware Quality Assurance (SQA) LOE is the estimated time the beta sites will spend doing work during the beta duration time period as specified by the development group. See the tab labeled "Level of Effort" for LOE guidelines.

Application packages are classified by a level of effort (LOE): Modest, moderate, large, and major. See the tab labeled "Level of Effort" for a complete description of level classifications.

Select in-house testing or the participating alpha test site within the drop-down box. If the site is not listed, go to the tab labeled "Active Test Sites" and enter the site name at the end of the table (blue-shaded area). Your entry will now appear within the drop-down box.

The minimum number of sites may be based on technical complexities of the application and/or patch being tested and best determined by the Developer.

According to the SAC Developer's Handbook (section 1.4.3.5), the customer group, with the assistance of the developer and OIT, will select at least two beta test sites. Test sites are selected based on adequate hardware, IT support and users able and willing to test all functionality, balancing size and type of facility.

You may review the SAC, section 1.4.3.5 for further details on beta testing. The link is located on row 70, column W.

Enter the 1st name, middle initial, and last name of personnel within columns 1 and 2. Enter nick names in paranthesis following the first name. Example: Robert (Bob) R. Reese

The "wrap" option is inactive and all data should fit on one row per cell. Data cannot be seen if it overlaps the cell.

Enter the name of the ITAC approver or supervisor.

Enter the 1st name, middle initial, and last name of personnel within this column. Enter nick names in paranthesis following the first name. Example: Katherine (Katy) K. Kook

The "wrap" option is enabled for two rows of data entry within each cell. Press "Alt-Enter" to advance to the next row within the same cell when needed.

Provide brief details or type "None" if not applicable.

The "wrap" option is enabled for two rows of data entry within this cell. Press "Alt-Enter" to advance to the next row within the same cell when needed.

Enter the full application name.

Naming convention: Namespace, Application name version #, patch # (if applicable)

Example: ABM Third Party Billing version 40, patch 1 Namespace = ABM, Application name = Third Party Billing, Version # = 40, patch # =1

The "wrap" option is inactive and all data should fit on one row within this cell. Data cannot be seen if it overlaps the cell.

Enter the expected date test files/builds will be submitted.

Enter the expected date(s) beta testing will start.

The "wrap" option is enabled for two rows of data entry within this cell. Press Alt-Enter to move to the next row within the same cell when needed.

If "Yes" is selected, provide brief details or type "None" if not applicable.

Example only: Test scripts will be provided to SQA.

The "wrap" option is enabled for two rows of data entry wtihin this cell. Press "Alt-Enter" to advance to the next row within the same cell when needed.

Provide brief details or type "None" if not applicable.

The "wrap" option is enabled for two rows of data entry wtihin this cell. Press "Alt-Enter" to advance to the next row within the same cell when needed.

Enter brief comments as shown below if they apply.

(1) Date a site was withdrawn, person stating the fact, and reason for withdrawal

(2) Date a site is added and person stating the fact

(3) List additional names to be included or excluded in email distribution and/or beta log

(4) Date the BTA or BTE was sent to the participating test site(s), submission deadline, and completion. (SQA only).

It is optional to provide other relevant information to support documentation of this process. Data entry convention: month/day: Comment. (initial).

The "wrap" option is enabled for three rows of data entry within this cell. Press Alt-Enter to move to the next row within the same cell when needed.

Enter the expected release date. Normally, the test cycle length for a patch application is a minimum of two weeks from when the beta test starts and for a version is a minimum of 30 days if test sites report no problems.

The "wrap" option is inactive for the cell. All data should fit on one row. Data cannot be seen if it overlaps the row.

Enter the expected quantity of test builds.

Select the expected overall total duration of beta. Normally, the test cycle length for a patch application is a minimum of two weeks from when the beta test starts and for a version is a minimum of 30 days if test sites report no problems.

See the tab labeled "Level of Effort" for LOE guidelines.

Enter the IHS Unanet task code(s) the project will be charged to. Example only: IHS R-002-02-00065 Practice Management Applications O&M - 1.1. Accounts Receivable (BAR) O&M

The "wrap" option is enabled for three rows of data entry within this cell. Press "Alt-Enter" to advance to the next row within the same cell when needed.

Answer "yes" only if the following has been performed.

Request the project manager to enable the task code within the IHS Unanet timesheet of the SQA Caretaker of the project and the SQA TRM administrator the same day the TRM is submitted to SQA.

If the answer is "No" or the box is not "checked," SQA personnel will follow-up with the person who has submitted the TRM for completion.

For inquiries, contact all SQA personnel at: OIT SQA <OITSQA@ihs.gov>.

Click on the link titled "TRM-Template2411" to open a current blank template directly from the SQA SharePoint site. This template allows the preparer to list one application package.

Select "Yes" only if the following requirements have been met.

Software Quality Assurance (SQA) requires the assigned project team member to personally contact the site manager to: (1) confirm the sites availability to beta test and ensure site recipients are aware of their participation, (2) relay specifics of the project, (3) answer questions site recipients may have, and (4) confirm current names of site signatories posted within the BTA table.

If "No" is selected or there is no selection, SQA will follow-up with the person preparing the TRM to answer item 6a.

Select "Yes" only if the following requirements have been met.

Personnel turnover, relocation, or re-assignment may occur at any time; therefore, it is extremely important to confirm the current names of site representatives / signatories participating in the beta test through the site manager. Ensure test site recipient names entered within the beta test site table (below) are confirmed before submitting the TRM to the SQA Team.

If "No" is selected or there is no selection, SQA will follow-up with the person who has submitted the TRM to answer 6b.

Note: Confirming personnel names expedites the documentation process and ensures accurate, current information is provided to SQA and project participants.

Enter the name of the lead tester for IHS, Tribal, or Urban facilities. Representation depends on the application being tested and location is not a factor. The name provided here may be included in the addressee list within the beta log for the project.

Note: Do not leave this column blank if an adjacent test site is selected. The TRM will be returned to the preparer if required data is either incomplete or not provided.

The "wrap" option is enabled for three rows of data entry within each cell. Press Alt-Enter to move to the next row within the same cell as needed.

Enter the name of the test site manager for IHS, Tribal, or Urban facilities. Location is not a factor. The name provided here may be included in the addressee list within the beta log for the project.

Note: Do not leave this column blank if an adjacent test site is selected. The TRM will be returned to the preparer if required data is either incomplete or not provided.

The "wrap" option is enabled for three rows of data entry within each cell. Press Alt-Enter to move to the next row within the same cell as needed.

AFFILIATION AND LOCATION ARE FACTORS

(1) Enter the name of the Site Chief Executive Officer (CEO) for IHS, Tribal, or Urban sites not in the Great Plains area (formally Aberdeen).

(2) Representation from the Site CEO is not required for IHS, Tribal, or Urban sites in the Great Plains area. If the site is in the Great Plains, enter the name of the area RPMS tier 2 administrator. Example: Tier 2 Admin. - First name, middle initial, last name.

Note: Do not leave this column blank if an adjacent test site is selected. The TRM will be returned to the preparer if required data is either incomplete or not provided.

AFFILIATION AND LOCATION ARE FACTORS

(1) Enter the name of the Area Information Systems Coordinator (ISC) for IHS facilities not in the Great Plains area.

(2) Representation from the Area ISC is not required for Tribal and Urban facilities not in the Great Plains. However, since Area ISC's have requested to be copied on email transmissions for their sites, provide the name of the Area ISC within the field.

(3) Enter the name of the Area ISC and Area Chief Information Office (CIO) for IHS, Tribal, or Urban facilities in the Great Plains area and identify their titles. The following applies for sites in the Great Plains: (a) The area CIO must provide approval for a site to participate in beta testing, (b) Required signatures must prove to be valid.

Note: Do not leave this column blank if an adjacent test site is selected. The TRM will be returned to the preparer if required data is either incomplete or not provided.

SQA tracks the performance and reliability of beta test sites testing application packages classified with an LOE of moderate, large, and major. Therefore, it is essential for the assigned project team member to inform SQA if a site is withdrawn or is unable to complete the beta test. In either case, SQA will check the box titled "W-DRAW" to identify a site as withdrawn and document the event within the section titled "Notation" (beneath the table).

If a Beta Test Agreement (BTA) is generated for this project, specific authorized test site personnel will be required to participate and/or endorse the BTA for application packages with an LOE of moderate, large, or major. A project classified as a modest LOE is not required to go through the BTA process unless the project is deemed a special case. Also, affiliation (IHS, Tribal, or Urban) and location (if the site is in the Great Plains area) may be factors for selection of test site representatives.

The following reference material provides details for filling out this section.

(1) Excel comments at each column

(2) Go to the Excel tab titled "Site Rep's,"

(3) Click on the link titled "Beta Test Sites" (PowerPoint show at row 20, column V)

(4) Click on the link titled "Valid E-Signature" (PowerPoint show at row 22, column V) The TRM must be completed for all project levels: modest, moderate, large, and major. There are two templates: (1) TRM-Template2411 - Allows the preparer to list one application (link at cell H4), and (2) TRM-Template 2411a - Allows the preparer to list up to 38 applications (link at cell J4).

The TRM is updated routinely to reflect feedback from users and to incorporate SQA beta process improvements. Submitting a current TRM with all text fields filled in as required, and test site information verified by the site manager, will ensure project participants are receiving the most current and accurate data. Incomplete TRM's will be returned to the creator.

The TRM template may be modified to accommodate special needs, such as additional rows to list test sites, or to have a supporting spreadsheet inserted within the Excel file. Relay special needs to the BTA/BTE administrator or the SQA caretaker of the project.

Submit the completed form to SQA at OIT SQA<OITSQA@ihs.gov. An email link is provided at row 4, cell Q.

Ensure an appropriate selection is made from the combo-box drop-down list in Item 10 (row 59). If applicable, enter the required information as needed (beginning on row 61).

The "wrap" option is inactive for each cell. All data should fit on one row per cell. Data can not be seen if it overlaps the cell1 Click on the link titled "TRM-Template2411a" to open a current blank template directly from the SQA SharePoint site. This template allows the preparer to list up to 38 application packages.

After selecting the link, allow time for each PowerPoint show to open. When needed, click the "X" in the upper right corner of the program to exit the show and close PowerPoint.

Select the participating test site from the drop-down menu. If the site is not listed, go to the tab labeled "Active Test Sites" and enter the site name in CAPS at the end of the table (blue-shaded area). Instructions are provided. Your entry will now appear within this drop-down box.

The SQA Site Facility Database contains information of IHS, Tribal, and Urban facilities. The Access database is available at the SQA SharePoint site. SQA requires the designated project team member to personally verify all test site signatory names through the site manager before submitting the TRM to SQA

To open the zipped file, click on the link titled "Site-Facility DB v2.1". Once the file is open, select "Site/Facility". The field titled "Contains" in the upper right corner will enable you to perform a search - Enter the site name, then select the tab titled "Site Contact" to view the names of site representatives.

Project 1: Enter information concerning beta testing of the application for the project within each field on row 37 as required.

Project 2 for the test site(s) added after project 1 was completed: Enter information concerning beta testing of the application within each field as required . If the data is the same as in row 37, enter "No changes" as needed on row 38.

Enter the 1st name, middle initial, and last name of all personnel throughout the TRM. Use identifying aspects ONLY to differentiate similar or identical names, such as Jr., MD, location (IHS/HQ), etc. Place nicknames in parenthesis following the 1st name. Example: Richard (Rick) A. Donner Jr.

Confirm the spelling of all personnel names. The IHS global address list (GAL) will help. The email address is required for all personnel listed within the TRM. If the name is not listed in the GAL, the preparer is required to provide the email address following the name. There is no need to enter the email address if the name is listed in the GAL.

While filling in the personnel names throughout the document, keep in mind that the addressee list for the beta log may be taken from personnel listed within the TRM. This would include the sections for the project team, additional project team members, and all sites managers and lead testers within the beta test site table.

Enter the names of additional project team members as needed. Provide the email address only if the personnel are not listed in the IHS GAL. It is optional to briefly provide other pertinent information concerning team members. The names provided here may be included in the addressee list within the beta log for the project.

The "wrap" option is enabled for two rows of data entry. Press "Alt-Return" to advance to the next row in the same cell as needed.

Enter and identify the name of the business sponsor and alternate. A business sponsor oversees the project and federal project lead. An alternate would be the person authorized to sign required documentation (if needed) for release of the application package on behalf of the sponsor.

Site-Facility DB v2.1 Site-Facility DB v2.1 TRM-Template2411 TRM-Template2411a

EMAIL TECHNICAL WRITER(S)

EMAIL SQA

LEVEL OF EFFORT

&C&P of &N&RSoftware Quality Assurance (SQA)