Customer Acceptance Testing (CAT) Process

PURPOSESCOPEPROCESS DESCRIPTIONPROCESS INPUTS/OUTPUTSSUPPORTING DOCUMENTATIONREVISION HISTORY

Process Owner: Manager, Business Relationship Management

Note: An owner must be a PCES-level manager.

This document establishes processes for the TSLC Agile (Release) Customer Acceptance Testing (CAT) and Waterfall CAT phase within the Postal Service Technical Environment.

PURPOSE

The purpose of the CAT process is to:

SCOPE

This process applies to all:

Exemptions:

PROCESS DESCRIPTION

The CAT process validates for the business owner (customer) that the technology solution and its components conform to the approved Technology Solution Requirements prior to deployment. This process is composed of the following subprocesses. Baseline artifacts are mandatory and must be uploaded. Baseline artifacts are indicated in this document by an asterisk (*).

  1. Follow the Certification and Accreditation (C&A) Process.

    The Business Relationship Management Program Manager (BRM PM) coordinates this task.

    For security-related processes and artifacts, follow the Certification and Accreditation Process as described in the Handbook AS-805A, Information Resource Certification and Accreditation Process.

  2. PCI in-scope only: Develop and Maintain Secure PCI In-Scope Systems and Applications.

    The BRM PM coordinates this task.

    Ensure that all requirements listed and referenced in the Develop and Maintain Secure PCI In-Scope Systems and Applications are met.

  3. Finalize CAT Documentation.

    The BRM PM coordinates the following tasks.

    • Finalize the CAT Strategy and CAT Plan that were started in the Sprint 0/Requirements phase.
    • Create and finalize CAT Scripts to ensure that requirements are thoroughly tested.

  4. Perform CAT.

    The BRM PM coordinates this task.

    Execute the CAT Plan. All CAT results are documented. See Update Requirements Traceability Matrices (RTMs) for additional information.

  5. Analyze *CAT Results.

    The BRM PM coordinates this task.

    Review the CAT results and determine if the Technology Solution meets the system requirements.

    Each Stakeholder is responsible for reviewing all CAT results, including issues logged, to ensure that CAT is complete and the Technology Solution will meet their requirements. The Stakeholder is also responsible for understanding the impact of any issues on their requirements and the overall release.

    Document all known issues and explanations of failures and workarounds in CAT Results. All test results must be retained in accordance with Postal Service data retention requirements.If the issue results in a change to the accepted Technology Solution Requirements or Design documents, it will be logged and submitted to the CCB. Problems will be entered, prioritized, and resolved during the CAT process.

  6. Update Requirements Traceability Matrices (RTMs).

    The BRM PM coordinates this task.

    RTMs must be updated to reflect final CAT scripts, results, and any CAT exemptions. If the CAT scripts, results, and/or exemptions are not documented in the RTM, the RTM must include mapping to SIT/CAT Scripts and results documents that address each requirement in the RTM.

  7. Obtain CAT Approval.
  8. The BRM PM coordinates this task.

    All Stakeholders provide consensus approval of all CAT results and issues after performing a thorough review of test results, the final RTM(s), and the Known Issues Log. This approval represents the final decision to implement the solution into production based on testing results as compared to the final requirements. This final approval also indicates that all Stakeholders were aware of and approved all changes made to requirements throughout the release.

    Tollgate Process Only: Conduct Implementation Tollgate

    If the release has been selected for the Tollgate process, the Implementation Tollgate is conducted at the end of CAT. Tollgate requirements for attendance and approval are provided in the TSLC Policy.

    In addition to Stakeholder approval, the following documentation must be created and presented to Stakeholders during the Tollgate meeting:

    • *Updated RTM
      • *Final CAT scripts
      • *Final CAT results with known issues
      • *CAT Exemptions if needed

    CAT Results with Approval is the Implementation Tollgate. Tollgate Meeting Minutes are a mandatory output of this meeting.

  9. Provide Release Notes.
  10. The Technology Solution Coordinator is responsible for providing Release Notes to be included in the Build.

  11. Upload Documents to the TSLC Artifacts Library.
  12. The BRM PM ensures that the following artifacts are uploaded to the TSLC Artifacts Library in the appropriate folders:

PROCESS INPUTS/OUTPUTS

Baseline artifacts are mandatory and must be uploaded prior to release to production unless the project is following the Tollgate process. If Tollgate, documents from the Tollgate must be uploaded within 10 business days. Baseline artifacts are indicated in this document by an asterisk (*).

Inputs

Outputs

SUPPORTING DOCUMENTATION

Access supporting documentation from ITWEB (Internal):

Access Supporting Documentation from USPS.com (external):

REVISION HISTORY

Version
Date
Description of Change
1.0 05.10.2013 Agile and Waterfall processes combined; updated for Tollgates, PCI, and general compliance; Ownership of TSLC processes transferred from Manager, Solutions Development and Support, to Manager, Business Relationship Management.

Note: This document is Section 508 compliant.
1.1 08.16.2013 Scope:
Updated to clarify that the Requirements must be approved, not the Requirements Traceability Matrix document.
1.2 03.18.2014 Process Description:
Replaced "customer" with "business owner (customer)" to define the customer as the business owner.

Process Inputs/Outputs:
Updated "baseline artifacts" statement to clarify that they must be uploaded prior to release unless the project is following the Tollgate process. If Tollgate, required Tollgate artifacts must be uploaded within 10 business days.
1.2.1 06.15.2015 The annual review for functional accuracy and current PCI DSS requirements has been completed: No changes. CR 81805
1.2.2 06.26.2015 Non-substantive update: Update CR for annual review. Remove link and version of PCI DSS.
1.2.3 03.14.2016 Annual Review: No changes. The annual review for functional accuracy and current PCI requirements has been completed. CR 154951
1.2.4 10.31.2016 Annual Review: The annual review for functional accuracy and current PCI requirements has been completed. CR 223948
Powered By OneLink