QA Framework
Our QA framework is designed to improve performance through out the SDLC. This gives the clear picture of our quality best practices. Framework consists of the high level details of different artifacts, tools, processes, environments across different groups.
The Process, Functions, Dependencies, and Tools of the QA Framework are depicted in the following diagram. Testing Artifacts and supporting documentation to accomplish the corresponding function is also listed in the diagram.

The QA Process is made up of the following integrated sub processes:

1.      QA Planning and Training– provides for the development and base lining of the QA Plan to train project team members who have not been exposed to the Product or Project.

2.      QA, Requirements and Audit Review – uses structured review checklists to gather the data required for analyzing project and product compliance to process and standards. QA team performs a review on the product or project requirements with BA/Product Management, PM and Dev team.

3.      Test Plan and Test Cases Creation – QA Team creates a test plan, which includes Entrance Criteria, Exit Criteria, Suspension/Resumption Criteria, Test Process and planning documentation.  Subsequently, each requirement is then further broken down into test case during the Test Case creation process.  The Test Cases are reviewed with client for feedback/signoff.

4.      QA Entrance Criteria – The following criteria must be met for a successful QA test cycle launch.  All business requirements are documented and approved by the business users.  (i.e. Statement of Work, Storyboard, Workflows, Data Dictionary, etc.). Design specifications are reviewed and approved.  Test Plan and Test Cases (internal/external) are reviewed and approved by BA/Product Management, PM and Dev team.  Unit and System integration has been completed by the dev team. Necessary hardware for testing is available, and test data is reviewed and compiled by the BA, Dev and QA team.  The product or project is delivered to the QA environment via load notice, with a reliable quality.  Initial smoke test of the delivered functionality is approved by the QA team. 

5.      Test Case Execution – QA Team performs a series of Test Case Execution cycles.  Findings are documented in the corresponding test case and tracked in the Issue Tracking Tool.

6.      Deviations, Issues, and Recommendations Tracking – provides for a set of tools for tracking and ensuring closure of deviations, issues, and recommendations identified during test cycles.

7.      Findings Report and Review – The results collected from each Test Cycle are summarized in Reporting Metrics. The Metrics are shared amongst the team, senior management and presented to the client for analysis and review.  Structured reviews and audits are synthesized into a Findings Report containing specific deviations, issues, and recommendations. These results are reviewed with the responsible team members and managers.

8.      QA Exit Criteria – Once Test Cycles are completed, the QA team performs a set of standards to hand off the product or project into the Client Test Environment.  All issues with priority levels 1, 2, 3 are resolved and re-tested.  All outstanding issues are documented.  Test results are shared amongst the teams. A subsequent Go/No-go/RRR (Release Readiness Review) meeting is held internally to determine acceptability of product or project into the Client Test Environment.