1. Different layers of UAT in Global Wealth Markets Domain
Bharathi Reddykonda - Lead Analyst
Shankar Dabadi – Associate Consultant
CGI Information Systems & Management Consultants Pvt Ltd

2. Abstract
The User Acceptance Testing (UAT) approach is to define the overall validation approach to be applied to the software products/services to ensure it complies with the functional and other operational customer requirements. UAT has three different layers of testing, as far as the Global Wealth and Capital Markets (GWCM) are concerned, due to the sensitivity of data and financial matters.  UAT is the most effective in reducing both time and cost, whilst increasing customer satisfaction.
At different layers of UAT, testing done by QA, BA and End User will be having their specific views and strategies. QA will test to make sure if software/product can handle required tasks in real-world scenarios. BA can assess if the system/product can support day-to-day business and user scenarios and to ensure the system is sufficient and correct for business usage. End User concentrates on meeting the customer's requirements functional/software/hardware requirements.
During UAT, more focus is given to identify the critical business requirements from client perspective, to choose realistic data, different process involved in execution, understand the system restrictions and environment constraints, work in real time environments, to achieve user expectations.

3. Introduction:-
In general, User Acceptance Testing is the last phase in Software Testing Process, before the Software is put into production environment. Software is tested by the actual users in production like environment to ensure that Software/Product can handle required tasks in real-world scenarios, according to specifications. UAT is also called as Beta Testing.
UAT phase and its strategies differ, based on the type of Software product and Business Domain where it is used.
SDLC
Req. Analysis
Design
Implem-entation
Testing
Evolution

4. Getting started with UAT:-
In the SDLC, a parallel process Software Testing Life Cycle (STLC) process hold phase UAT. In the STLC after the System and System Integration testing phase is completed, the deliverables will be promoted to UAT environment. Client performs the testing as per the business needs.

5. User Acceptance Testing Entry Criteria:-
UAT Strategy has been presented to and approved by steering committee
Detailed UAT Plan is complete
Testing Schedule/Timeline is confirmed and committed
All Test Suites/Business Scenarios have been Identified on the UAT Plan
All Test cases/steps have been written with priorities and reviewed by the Business
Testing environment is established
Security requirements have been documented and necessary user access obtained

6. UAT Layers in Global Wealth Markets Domain:-
In Global Wealth and Capital Markets (GWCM) domain of business, Software products UAT phase is split in different layers based on the testing done by the done by different groups as described below. Due to testing by different testing groups involved, the outcome of the product will be of high quality due the sensitivity of the data and process involved.
User Acceptance testing by QA (Quality Assurance)
User Acceptance testing by BA ( Business Analyst)
Use Acceptance testing by End User (Business User Acceptance testing)

7. User Acceptance testing by QA
Before the UAT starts, QA designs the overall test approach, Test strategy and finalizes the Scope of testing with involvement of the Client side Business Analysts and Business User who will be going to use software application. QA will test to make sure if software/product can handle required tasks in real-world scenarios.
UAT Test Design
Analyse the business and functional requirements, Risk assessment.
Identifying the critical business &functional requirements and impacted areas.
Create the business cases, test scenarios and test cases.
UAT test execution
Verify the UAT environments are ready for testing
Identifying correct data or create test data and continue with execution
UAT Defect process
Expected and Actual results are not matching, create the Defect.
Follow-up the defect till the closure.

8. Regression testing
QA performs the quick round of Regression testing to make sure everything around the defect is working as expected.
Next Layer of UAT
Complete and provide QA Signoff
Deliverables moved to next level of UAT
Advantages
As QA performs the testing in and around the complete functionality , the quality of the product is not compromised
Maximum defects found by QA, the chances of finding defect in next layers of UAT can be minimized. Trust is built from client.
Challenges
UAT implementation at times take longer than expected
QA needs to co-ordinate with support teams for any environment related issues or constraints
UAT has certain restrictions while performing tasks or execution, so there must be lot of coordination needed with support teams or functions
At times selecting or identifying the right test data becomes difficult, the QA should have the complete functional knowledge to create the test data

9. Case Study: Mutual Fund Order Entry
Below is the Case Study of Mutual Fund Order Entry and going forward, we will come to know how this Scenario is tested in different layers of UAT by different groups.
UAT by QA
Order Entry
Fund Types
Currency types
Account types
Backend
Active Money Market
CAD
Registered
Frontend
Active Non-Money Market
USD
Non-Registered
QA tests the Mutual fund Order entry using both Frontend and Backend for account types, using generic Fund Types, currency.

10. User Acceptance testing by Business Analyst
The second layer of UAT can be carried out by BA or the Business group. The Business group will be more familiar with critical and most used scenarios. Based on the knowledge, experience the group will carry out the testing. They may or may not document the things during the testing.
BA can assess if the system/product can support day-to-day business and user scenarios and to ensure the system is sufficient and correct for business usage. 
Advantages
As Business group has more of business knowledge, the testing can be more accurate and it is more from End User perspective
Number of defects moving on to the next layer of testing is very minimal
Challenges
UAT has certain restrictions while performing tasks or execution, so there must be lot of coordination needed with support teams or functions.
Technical related information or test data, BA may have to co-ordinate with QA or other support teams.
BA must have in and around knowledge for performing E2E flow of testing.

11. Case Study: Mutual Fund Order Entry
UAT by BA
Order Entry
Fund Types
Currency types
Account types
Backend
Active ROC MMK funds
CAD
Registered – Client
Frontend
Inactive Fee Rebate Non-Money Market
USD
Non-Registered –Broker
BA tests the Order Entry with more specific data such as ROC and Non-ROC funds and account types to make sure functionality is as expected

12. Business User Acceptance testing
This is the final layer of UAT testing. The User tests the product, as if the end user with utmost care and sensitive data. End User concentrates on meeting the customer's requirements functional/software /hardware requirements
Advantages
As the User uses more realistic data, the results achieved can be more accurate
Precise and accuracy is required at most, while dealing with financial transactions
Product can be defect free in PROD
Challenges
User must have knowledge on the functional/ technical aspects of the Application
The time frame for the UAT can be very stringent and hence becomes challenging

13. Case Study: Mutual Fund Order Entry
UAT by End User
Order Entry
Fund Types
Currency types
Account types
Entry type
Backend
Active ROC MMK funds
CAD
Registered – Client
Direct orders
Frontend
Inactive Fee Rebate Non-Money Market
USD
Non-Registered –Broker
Network Order/Wire Orders
End User tests the Order Entry with Direct orders/Network & Wire orders to make sure various order types are supported.

14. Defect Trends
Taking the above case study of Mutual Fund Order Entry into consideration, the below is the UAT defect trend in each Layer. This means more number of defects can be found in first layer, second layer. End User testing can results in Zero defect or very minimal defects. Prod is assumed to be defect free.
UAT by
End user
UAT by BA
UAT by QA
No of Defects: 1
No of Defects: 2
No of Defects: 2

15. Case of defects distribution for one of client in System testing and UAT Layers:

16. Automation testing in UAT
In the first layer of UAT testing, there is scope for Automation. In case of new requirements, QA can identify the most repeated or most commonly used Business Scenarios or Use cases and plan to automate them. In case of existing requirements, QA can create the Regression suite and run them.
In terms of automation approach, various tools and frame works are available. QA can choose the most suitable tool and framework for the product. The Client can be given more leverage and opportunity. The product will be up- to –date in Market and on demand.

17. Tools
Tool Name
Tool Function
Bus. Requirements
F-E2E
HPQC
Business Requirements for traceability X
Test Case Management
Test Execution Management
Defect Tracking
Reporting
HPQC tool is mainly used for UAT Test Design, Execution and Defect management, Test results documentation and reporting by QA.

18. Conclusion
We hope this article gives you an idea of what is UAT and how it is carried out for Software projects and how it is different from regular Integration and System Integration testing.
How UAT can be carried out at three different layers. What are the challenges that can come across and how to handle them, understand the restrictions, how to test with realistic data and to achieve the expected results.
After the Successful UAT, the product is delivered to the Client with at most quality and warranty period also provided in case of any issues that can be encountered in Production. Also client can get familiar with product.

19. References & Appendix
The reference mentioned below is, the Author has worked on the first layer of UAT for one of the leading Canadian Bank. UAT is performed on CGI’s Wealth Management Product. It is an investment fund transaction record keeping and processing service solution. System is used by fund Management Company and/or financial institution to enter and process financial and non-financial information, perform inquiries on its database and produce reports and other documents.
The Bank follows V-model process for QA verification and validation within the SDLC (Software Development Life Cycle) framework for Banks IT Software Projects.
Bank Business group and stakeholders decides the In -scope items for UAT. UAT performing group is known as QAT. QAT team got to test four different releases in a year. Apart from the regular CGI releases, certain Ad-hoc requirements will come to UAT. QAT team, testing approach and Test Strategy has to be agreed by all the Stake holders before UAT is started.

20. Author Biography
Bharathi has about 10+ years of IT testing experience and worked on BFSI [Global Wealth Management & Capital Markets, Investment Banking] domains. She has worked in various stages of testing including Integration, System Integration and User Acceptance testing. She has delivered various trainings related to project domains, testing process. She has worked as a Tester and Lead Analyst.
Shankar has about 13+ years of IT testing experience and worked on BFSI [Global Wealth Management & Capital Markets, Investment Banking] domains. He has worked as a Tester and Lead Analyst and currently working as a Test Manager.

21. Thank You!!!