ROFESSIONAL SUMMARY

• 7 years of experience in information technology.
• Good understanding of Software life cycle and quality processes.
• Expertise in QA testing of Mainframe and web-based Applications.
• Possess good functional knowledge in Insurance and Banking Industries.
• Experience in writing Test Scripts and Test Scenarios from business, functional and technical requirements.
• Facilitate requirements entry, test case creation and defect tracking in Quality Center, which improved efficiency and traceability.
• Extensive QA experience in all phases of lifecycle, including Requirements Gathering, Project Planning, Testing, Defect Tracking, Management and Reporting.
• Extensive experience in analyzing, reviewing and understanding of Business/Functional & Testing requirements and writing Test Plans, Test Strategy, Test Scenario, Test Cases and Test Scripts.
• Experience in writing & executing SQL Queries for back end testing.
• Experience in using of SQL, in order to check the data validity and data integrity.
• Performed business functional tests at various stages of STLC such as Functional Testing, Integration, User Acceptance Testing (UAT), Regression Testing in Web/Client Servers.
• Expertise in SPUFI, QMF, File Master and FILEAID as testing tools and for data manipulation and Data cleansing.
• Experience in importing and exporting of requirements between Quality Center and MS Excel.
• Logging and tracking defects and measuring the testing effort and the quality of the software by creating reports in Quality Center.
• Excellent analytical, communication and interpersonal skills and consistently being organized by management and peer for producing high quality works.
• Efficient and versatile team player with a positive approach to all tasks.
• Created test case coverage metrics and requirement coverage metrics and checked test case run , pass or fail, not run, not run due to defect, total number of open defect and total number of closed defect in quality center
• Experience of defect creation in defect management tool assigning defect and retesting the fixed defects.
• Quick learner, self starter, great communicator and follow good work ethics and QA methodologies and a strong team player.

TECHNICAL SKILLS

Hardware Systems : IBM OS/390
Languages : COBOL, Easytrieve and JCL
Tools : Mercury Quality Center, ClearQuest, File Master, Test Director,
Endeavor & File-Aid
Front End : CICS
Back End : DB2 & IMS
Others : VSAM

PROFESSIONAL EXPERIENCE

Client: Confidential, Chattanooga, TN Dec 2008-tilldate
Project: Strategic Enrollment
Unum is the industry leader in Disability Income Protection and one of the top providers of supplemental benefits in the nation. In the United States, they have enjoyed 30 consecutive years of market leadership in group income protection: Fast Forward is a re-engineering version of an existing Disability Income Protection Individual Insurance System; and now it is developed for supporting Group VWB products with .Net technology with supporting of i-Services, CCP, IRP, NaviLink, PCES & CRM platforms. The some of the major modules are being re-developed on .NET platform from IBM Mainframes. The new Simply Unum will include the features available in the application relating to the following major tracks like Acquisition (Quote/Proposal, Sold Case/Implementation, Enrollment, Policy Issue & Risk), Administration (Billing, Claims, Compensation, Product Build & Financial Reporting), Self-Service and Customer Management. IMS database is supported to IBM Mainframes services and DB2 database is supported to .Net developed products
The primary goal of Strategic Enrollment is to conduct enrollment for the employees of various classes belonging to Organizations that provide Group insurance to its employees and also enroll employees for Voluntary insurance benefits of their choice.
The UNUM employees can also avail the benefit by using the self-enroller logon registration, which is exclusively given for UNUM employees alone.

Responsibilities:

• Preparing the Test cases for the requirements.
• The test cases will be uploaded into QC and after execution the same will be run in QC
• Defects that are raised during the testing will be tracked in Quality Center.
• Testing status will be reported to on-site coordinator on daily basis.

Tools: ClearQuest, File-Aid and Mercury Quality Center

Client: Confidential, US Aug 2008-Nov 2008
Project: HLSS (Home Loan Servicing system)
Location: Computer Sciences Corporation, India

Confidential,started its activities by offering home loans to Seattle, Washington residents in 1890. On June 25, 1908, the company changed its name to Washington Savings and Loan Association. In 1911 marking the start of a relationship between Murphey Favre, Inc. an investment firm and Washington Mutual.
Home Loan Interface (HI) System consolidates loan input from the Loan Origination Systems like STeP(Retail and Consumer Direct) ,MLCS (Mortgage Lending Control System) , LoanWorks, LBM(Long Beach Mortgage), Simple Loan Manager and OPTIS transforming them into a consistent format for processing by Fidelity MSP and other downstream applications like Capital Markets Database (CMDB), Document Tracking System (DTS), Enterprise Data Delivery (EDD), Financial Data Mart (FDM), General Ledger (GL), LODS(Loan Origination Data Store), QRM(Quantitative Risk Management), etc.
Home Loan Interface (HI) is a mainframe based application that uses COBOL, JCL, DB2, SPUFI, SQL, SAR, Endeavor, VSAM, CICS, Quality Center and File Manager to channel loan origination data to the various support systems and loan servicing functions in WAMU’s mortgage banking line of business. This is the core means from which the HI System provides value to the bank.
The HI System operates in two environments, Online and Batch Processing Environment

Responsibilities:

• Preparing the Test cases for the requirements.
• The test cases will be uploaded into QC and after executing the test cases in different regions like SIT, RSIT and UAT the same will be run in QC
• Defects that are raised during the testing will be tracked in Quality Center.
• Testing status will be reported to on-site coordinator on daily basis

Tools: File-Aid and Mercury Quality Center

Client: Confidential, US Jan 2008 July 2008
Project: Claims TCOE(Claims Testing Center of Excellence)
Location:Cognizant Technology Solutions, India

Confidential, project is a development and enhancement project that ensure data quality of various Claims Applications viz., Dispatch, Impact, Tmate, Travpro, ClaimNet, CCA Conversion etc. Services will be available for interfacing the mentioned Claim Handling applications to access/update/add/delete the data. Those services will incorporate business rules that would apply to the overall enterprise. Cognizant will work with Travelers during the requirement phase to define the requirements of these Claims Applications as well as the requirements for the testing of them.
Following are the three environments for Claims TCoE.
1. Series C: The Application is tested in this Series C once the coding is completed and unit tests are performed by the developers in Series A and Series B. The Application is tested by dedicated testing team in Series C in order to verify the collection of system components post code migration. System testing in this region includes testing of all changed components.
2. Version Region: The Application is tested in MODEL Office region, also known as Version region once the system and system integration testing is completed in Series C and Prior to the Production verification testing (in the Production Environment). The Version region is a pilot rollout to verify if the users can work successfully on the new application/functionality prior to Production.
3. Production: Once the testing is completed in the version region the code will be moved to Production Training region where the high level system testing should be performed. Here the testing will be performed only on the enhanced functionalities just to insure that there is no deviation in the application because of production move and it is working as expected. The code will go live to Production when the Production training testing is 100% success

Responsibilities:

• Preparing the Test Scenario’s, estimations and Test cases for the requirements.
• The test cases will be uploaded into QC and after executing the test cases in different regions like Series C, Version and Production Training the same will be run in QC
• Defects that are raised during the testing will be tracked in Quality Center.
• Testing status will be reported to on-site coordinator on daily basis.

Tools: File Master and Mercury Quality Center

Client: Confidential,US Aug 2006 Dec2008
Project : CLASS (Consolidated Loan Administration and Servicing System)
Location: Cognizant Technology Solutions, India

For more than 30 years, Sallie Mae has been helping students achieve their dreams of higher education by providing funds for educational loans, primarily federally guaranteed student loans originated under the Federal Family Education Loan Program (FFELP). The company currently owns or manages student loans for more than seven million borrowers and is the nation\'s leading provider of education loans.
Sallie Mae as an organization has three different sections:
CLASS, ExportSS and PCI.
CLASS - an acronym for the Consolidated Loan Administration and Servicing System - is an IBM mainframe, DB2 and CICS based system developed by Sallie Mae for the servicing of student loan accounts. The CLASS system was created in response to the need for an automated computer system for processing, servicing, and maintaining student loans at Sallie Mae Servicing Corporation.

The objective of the project is to maintain the application and enhance the application thereby
1) Making CLASS system more reliable
2) Improving the process efficiency of CLASS system
3) Decreasing calls to call center related to repayment/disclosure.

Responsibilities:

• Preparing the Test Specification Document based on the Technical Specification Document received.
• The Test Specification Document includes Test Cases and corresponding Test Results.
• Defects that are raised during the testing are being tracked in Test Director.
• Testing status will be reported to on-site coordinator on daily basis.

Tools: File Master and Test Director

Client: Confidential,Japan May 2006 July 2006
Project : MCP (Mainframe Consolidation Program)
Location: HCL Technologies, India

Confidential, is one of Japan’s leading System Integration Companies.Confidential, operates in various business areas including Financial Services and Insurance.
Confidential,is one of the largest foreign insurance companies operating in Japan. AFLAC’s Information Technology assets consist of Hitachi as well as IBM Mainframes. AFLAC has initiated a “Mainframe Consolidation Program (MCP)”, wherein all the programs and other resources (components) as well as data on the Hitachi Mainframe will be converted and migrated to IBM Mainframe.
AFLAC has awarded the MCP to IBM Japan, who has engagedConfidential, to carry out application conversion portion of the MCP, along with HCL. IBM Japan will be executing other portions of the MCP, either by themselves or through other companies.

Responsibilities:

• Pre conversion testing on Hitachi Mainframe.
• Post conversion testing on IBM Mainframe of the job nets on which pre conversion
• Testing was done.
• Comparison of pre and post conversion results for the identified files/reports
• Updating the TEST Matrix with actual results
• Involved as second level reviewer for many of the deliveries from the team.

Tools: File-Aid and SuperC