SUMMARY:

• Around 8+ years of rich experience in design & development of computer software applications using IBM 370/390 ESA architecture and implementation using COBOL, JCL, VSAM, DB2, TSO, and MVS.
• Along with my broad experience with the software development life cycle, I am also experienced with stakeholder management and ensuring that project goals and business outcomes are delivered in an effective and timely manner.
• My particular strengths lie in being a fast learner, pro - active, sociable and organized.
• Key involvement in Mainframe development(COBOL/DB2) and testing, setting up the testing processes, Preparation of test plan and test reports, CAR Audit and doing reviews, defect prevention, handling maintenance monthly & quarterly releases successfully and other quality related work
• A very good focus on SDLC.
• Worked for Confidential 500 companies like Confidential.
• Customer facing onsite exposure in US and Italy for insurance/banking projects.
• Received customer appreciation.

FUNCTIONAL AREAS:

Designing, Development, implementation and enhancements of: Insurance Domain, Finance Domain, Banking Domain Applications in Mainframe.

TECHNICAL SKILLS:

Skills: TSO/ISPF, MVS, JCL, COBOL, CICS, DB2 XML, XSLT, UNIX, MS-DOS, WINDOWS 98

Tools: Micro focus COBOL, XML SPY, Quality Center, Expeditor, File-AID, Abend-AID, Endeavor, TWS

Rational Tools: Clear Case, Clear Quest, Rational Requisite pro

Testing Tools: Animator, Hiperstation, Test Director, SOA-tester, Desktop Tester, CA7

PROFESSIONAL EXPERIENCE:

Confidential

Subject Matter Expert

Responsibilities:

• Understanding functional & technical Confidential in detail
• Keeping track of all the Confidential activities for Confidential application
• Analysis, Coding, Testing, Review and Documentation of all the tasks assigned by Onshore
• Creation of HLD & LLD
• Involved in executing the test cases in Unit region & in QA
• Creation of UTP, ATP & Documents
• Major involvements in the Confidential to new resources
• Meet SLA s for all the requests assigned to me.
• Helping all the team members to complete their tasks
• Daily status report to onshore
• Point of contact of all functional & technical issues in the Project
• Organizing Client meetings, Parties and Outing activities

Technologies Used: - COBOL, TSO, ISPF, Abend-Aid, Quality Center, Endeavor, TWS, CA7, QMF, SPUFI

Confidential

SME and onshore coordinator

Technologies Used: - COBOL, ISPF, Abend-Aid, XSLT, XML, Hiperstation, and Quality Center.

Responsibilities:

• Involved in the ADBT phase o SDLC Analysis of the work request (code changes requested by the client), find the COBOL program impacted, Labeling of the program as per the release date, analyze an existing flow of the program & include the new code changes as per the requirement during each release.
• Involved in mapping of the COBOL programs with XSLT used during the translation of XML to AL3 & AL3 to XML.
• Worked on the creation of the XML s used to run the COBOL programs.
• Involve in executing the test cases in Unit region & in QA region.
• Creation of the Unit test plans for the work requests handled during each release.
• Major involvement in Release day activity Testing in production region & monitors & handles the abends if any.
• Major involvements in the Confidential given to the new team members.
• Key involvement in the Regression testing phase used to be carried out during each release in mainframe.
• Direct interaction with the client.
• Daily status report to onshore.
• A very good exposure to basic insurance term such as a Policy, Policy life cycle, Underwriter, terms of the policy etc.
• Request Quote
• Issue (Add a Policy)
• Policy change (midterm & inception)
• Renewal
• Cancellation
• Reinstate
• Reissue
• Inquiry

Confidential

Technologies Used:Cobol, JCl, UNIX (Perl Scripting), Rational Clear case, Rational Clear Quest, Rational Requisite pro, Animator.

Responsibilities:

• Analysis of SNUMBS coded in Bull Mainframe to create the Data files for the applications handled.
• Preparation of Low Level Design based on the data file created.
• Worked on the Code base lining for the applications handled.
• Worked on Labelling of the COBOL codes and JCS present in the client side clear case.
• Worked on COBOL build that involves the modification of the codes to get compiled on UNIX environment.
• Worked on the modification of the Auto System flow based on the change requests formatted by the client.
• Worked on the creation of the JCS (JOB CONTROL STRUCTURE), analyzing the SNUMBS in bull mainframe. This JCS is the job that executes the COBOL programs in UNIX ENVIRONMENT.
• Worked on Auto System specifications that play a major role in the submission of jobs during the Assemble Testing.
• Worked on the File Management Systems for the files that are used in the execution of jobs in UNIX ENVIRONMENT.
• Worked on the preparation of Delivery note for the applications worked on.
• Worked on Unit Testing, Assembly Testing.
• Created Unit Test Plan for the applications.
• Involved in executing the test cases in Rational Test Manager.
• Involved in the generation of reports for the UTP's of each application.
• Involved in the documentation of prerequisite procedures for the testing to be carried on in UNIX environment.
• Created Entry/Exit criteria for the testing phases - Unit Testing.
• Exposure to Software Development Life Cycle.
• Business and environment knowledge transfer to new team members.

Confidential

Technologies Used: COBOL, DB2, JCL, ISPF, TSO, Test-Director, Hiperstation, QTP.

Responsibilities:

• I was involved in a Regression testing in which I required to test the enhancement code developed by the developers. It includes below major factors.
• Testing for the enhancement and developments.
• Understanding the system spec and preparing DOU, Low Level Test outline and Low Level test plan.
• Logging the defects in Test Director and tracking through the same.
• Coordination with the clients and the offshore team, Status calls with client.
• Day to day management, daily status reporting to onshore regression team lead.
• Involved in the unit testing.
• Defined and suggest the solutions to the defects found.
• Reduced the overall issues down to the several root causes.
• Helping the team in testing the module.