SUDHA MURTHY TEEGAVARAPU
Email:*****.******@*****.*** Contact Number: +1-512-***-****
SUMMARY
Seeking position as a Mainframe development professional, I have 4+ years of experience with Mainframe
operations in Infosys. Primarily, I have dealt with Healthcare and Financial clients like Aetna, WellPoint
American Express and Citibank. With extensive work on COBOL, JCL, DB2, IMSDB, CICS, Fileaid,
Endevor, Changeman, TSO, JobTrac, Control - M and Xpeditor, I’ve a good command over SDLC 2.0
model, and Agile methodology
SUMMARY OF EXPERIENCE
Infosys Technologies Limited, Pune, India
I have extensively worked with JCL, COBOL, and DB2 in a Data warehouse project.
•
I also have a good exposure to the ETL tool, Informatica, to extract data from Teradata.
•
Dealing projects with a “Software Development Life Cycle” approach:
•
Requirement Gathering Analysis Design Development Testing Implementation and
Warranty Support.
An effective communicator with good interpersonal skills.
•
Experience in preparing Use Cases, Sequence diagrams, Activity diagrams, Class diagrams.
•
Skilled at reviewing test cases and making sure they are in accordance with requirements, and to
•
assist the overall testing process by Change and Defect Management methods.
Strong understanding of various SDLC methodologies such as Waterfall, Agile with hands on
•
experience in both of them.
Good analytical skills in understanding the business process, the functional requirements and
•
translating them to system requirement specifications.
- Attended various in-house soft skill and management development programs.
CAREER SKILLS
Domain Experience
HealthCare
•
Banking
•
Trainings/Seminars/Certifications
Completed 6 months of intensive training and coaching program at Infosys, India with overall
•
CGPA of 4.5 out of 5
o Completed training in Mainframe technology at Infosys, India
Completed STAR certification at Infosys, India.
•
433 TS- Microsoft SQL SERVER 2008 Database Development Certification.
•
IBM certified database associate.
•
Completed Infosys internal certifications, every semester, to keep up with the developments in
•
Software industry.
Trained to have the GDM (Global Delivery model) perspective towards our projects.
•
Microsoft Certified Technology Specialist.
•
Oracle 9I and Advanced/Core Java programming certification
•
TECHNICAL SKILLS
Languages
Proficient in: COBOL, JCL, REXX
•
I have also dealt with Java, C# (dot net) and Selenium tool in certain projects.
•
Software
Databases: DB2, IMSDB
•
Platforms: Z/OS, Windows XP/2000, Windows 7
•
Mainframe Technologies: JCL, VSAM, Easytrieve
•
Online Transaction Processor: CICS, IMSDC
•
Special Utility Software: FileAid, File Manager, Xpeditor, SPUFI, Endevor
•
Schedulers: CA7, JobTrac, Control – M
•
Claims processing System: NASCO
•
File transfer methods: NDM (mf to mf), FTP (mf to other systems), SFT (Secured), XCOM
•
Client systems: Citrix, Clarity, SharePoint, IMR (Incident Management Request), CMR (Change
•
Management Request), Manage Now, IM Plans
Other
Environment: Client – Server (Mainframes MVS/OS390)
•
Client regions: EMEA market, France, Italy markets
•
FUNCTIONAL SKILLS
Management and Leadership Skills
I have experience in creating realistic software schedules/estimations, Strategic/ Tactical Planning and
•
Business Analysis.
Motivated professional and a good Team player.
•
I have handled a team of 2-3 members for small and medium size projects.
•
Training & Development Skills
I can train and troubleshoot most of the technologies present in my skill set.
•
EDUCATIONAL BACKGROUOND
Qualifications:
Diploma in Management with an aggregate of 70% from IGNOU in June 2013.
•
B. Tech. (Biomedical Engineering) with 85% aggregate in 2009 from University of Mumbai, India
•
12th standard with 75% aggregate from ISC Board in 2004 from Smt. Sulochanadevi Singhania
•
School, Mumbai.
10th standard with 88% aggregate from ICSE Board in 2002 from Smt. Sulochanadevi Singhania
•
School, Mumbai.
PROJECT DETAILS
Multiple user stories Citibank
1.
Client : Citibank, U.S.
o
Team Size :5
o
Designation : Sr. Programmer
o
Period : December 2014 – Till Date
o
Description:
Act as interface between Rainbow systems and Legacy systems using Agile methodology. Functioning
systems which are expected to retire would involve minimal code changes so that the logic would be
provided by the interfacing system.
My Role:
Work with team to do Impact Analysis, Unit Testing, providing support for System Integration testing
•
and Implementation Activities.
Extensive calls with stakeholders of the change under concern.
•
Code a program to accomplish the change.
•
Coordinate with offshore to complete the construction of the code.
•
I am involved in both development and testing.
•
Responsible for creating SNOW requests when required to create packages.
•
Handle defects.
•
Working on RTC and RDZ.
•
Jobtrac to Control M migration AMEX
2.
Client : American Express, U.K.
o
Team Size : 15
o
Designation : Systems Analyst
o
Period : October 2013
o
Description:
Earlier, schedules were controlled using the scheduler Jobtrac and the new project required migration of
all the schedules and jobs to a different scheduler, Control-M and verify if the schedules are functioning
correctly on Control-M. Version control under use was ChangeMan.
My Role:
Work with team to do Impact Analysis, Unit Testing, providing support for System Integration testing
•
and Implementation Activities.
Extensive calls with other vendors of Amex for this project to coordinate the precise responsibilities to
•
shared.
Code a program to identify the redundant programs in Jobtrac to exclude them from migrating to
•
Control M
Automate the insertion of the vital parameters in each job on Jobtrac to be interpreted by Control M
•
Migrate a batch of 5000 dummy jobs in a mock batch execution and fix all the errors.
•
Responsible for the first set of jobs in live migration by maintaining an excel to monitor the migration,
•
hold the jobs which fail, analyze them to take a call to either fix or reschedule that job in the next
migration.
Led a team of two members of the team to handle subsequent migrations.
•
Warranty support to ensure that migrated jobs are not abending in Control M.
•
I was involved in both development and testing.
•
Responsible for monitoring the Incident management queue and flagging an abended job before the
•
client support team flags it. Fix the issue according to the criticality to ensure that scores stay high.
Responsible for directing other system jobs to their respective queues. This involved clear
•
understanding of other involved system and their footprint jobs.
Worked on managing clarity timesheets. Involved follow up with the erroneous time sheets from other
•
folks, rectifying them and after a sign off it would be sent across on a weekly basis.
ICD10 WellPoint
3.
Client : WellPoint, U.S.
o
Team Size : 04
o
Designation : Systems Analyst
o
Period : Feb 2012 – August 2012
o
Description:
This project basically involves changes in the Diagnosis Code and Inpatient Hospital Procedure Code
whose length needs to be increased to include new set of codes and detailed description of body parts
respectively. The team was involved in analysis and coding of impacted programs as per the new
functionalities and verifying the impact of the enhancements at the customer level. Version control
under use was Endevor.
My Role:
Involved in analysis coding and testing and also maintaining the quality of the project in each phase
•
Conduct analysis of alternatives and develop recommendations.
•
HMO to PPO Migration (Company ID) WellPoint
4.
Client : WellPoint, U.S.
o
Team Size : 08
o
Designation : Systems Analyst
o
Period : March 2011 – July 2012
o
Description:
The main job was to move the HMO groups to PPO groups because the VA HMO Amisys platform is
an old version of a vendor package. This system runs in an MPe/iX operating system on an HP3000
platform, which cannot be remediated for compliance with the ICD10 federal mandate.
The team was involved in coding the programs as per the new functionalities, testing them as per client
needs and verifying the impact of the enhancements at the customer level.
My Role:
One of the 3 members in the project who supported it till the last phase of the project.
•
Later WellPoint projects were purchased by another vendor and I was actively involved in
•
transitioning all the knowledge, in great detail.
Received appreciation for a neat and professional transition of the knowledge to the new vendor.
•
Extensive documentation according to the CMMI standards, was one of my key learnings in this
•
project.
Classifying and taking a call on some of the unmarked jobs as HMO or PPO was very challenging. It
•
involved in depth code study of the existing HMO and PPO jobs and all their possible variations.
Maintaining an excel sheet to perform extensive unit testing on the modified jobs.
•
Fix job failures which would abend due to Db2 bind issues as well.
•
Use QMF to extract the required data for appropriate analysis.
•
Learnt how to use IMS from other teams of WellPoint since it was essential to understand if the job
•
was failing due to which kind of data issue and thus make changes.
Create DB2 Packages and DCLGEN in a DCLGEN PDS for most DB2 tables to save overhead on the
•
last minute creation of the copybooks. With the same name as table for the DCLgen the coder merely
needed to call the PDS with the member name in brackets. Later we automated the process of
DCLGEN creation as well.
Resources were eventually released in short numbers according to the decaying work in this project as
•
it was reaching completion and I was actively involved in routing the work distribution among the
teammates, to my team lead
Document all our Design and test documents in VSS for future reference internally.
•
Learnt how to handle situations where client would suggest modifications even after the requirements
•
were frozen.
I was an active participant in the actual migration of jobs in batches.
•
I was involved in both development and testing.
•
SSCR (Small Service Change Request) – WellPoint
5.
Client : WellPoint, U.S.
o
Team Size : 01
o
Designation : Systems Analyst
o
Period : Feb 2011 – May 2011
o
Description:
This change request involved was to ensure proper working of premium payment to resolve the
issues related to non-payment of premium.
My Role:
Involved in analysis coding and testing and also maintaining the quality of the project in each phase
•
SSCRs were challenging in the sense of their short delivery time, some having just 4 days to design,
•
code and execute testing as well.
Managing time to complete these adhoc requests along with the actual work in hand was work that
•
required adaptation.
SSCRs were numbered and I was responsible to keep a track to pile them in accordance for better
•
understanding of the occurrence of these SSCRs and suggest a long term fix to my onsite who would
then propose it to the client to make it a full-fledged project.
A2C (ID Cards) WellPoint
6.
Client : WellPoint, U.S.
o
Team Size : 02
o
Designation : Systems Analyst
o
Period : Jun 2011 – Sept 2011
o
Description:
This project involves movement of complete Amysis platform to Chips platform where in Chips
platform we have to make changes in the logic so as to include HMO groups ID Cards request as
well with PPO groups in the existing PPO system.
My Role:
Involved in analysis, coding, testing and also maintaining the quality of the project in each phase.
•
Both development and testing were an integral part of this project.
•
Mainframe systems and SSCRs Aetna
7.
Client : Aetna, U.S.
o
Team Size : 04
o
Designation : Systems Analyst
o
Period : Jun 2010 – Jan 2011
o
Description:
Adhoc requests for processing records were the unique behavior of this project. Round the clock
availability, I was on a beeper support for at least once a week per month on a rotation basis with
my other team members. Version control under use was Endevor.
My Role:
Involved in analysis, coding and testing and also maintaining the quality of the project in each phase
•
My first project ever was in a controlled environment called Aetna ODC where the system norms were
•
different from my regular Infosys work stations.
Adhering to all the rules and following the standards as per the ODC norms took time.
•
Analyze job failures and fix them or escalate them.
•
Document all the fixes to save time on the repeated job failures.
•