Amogh Mudkavi

acegun@r.postjobfree.com

602-***-****

Career Summary:

. Project Lead with 9+ years of experience in Design, Development,

Testing and Implementation of various web based applications for

different business organizations.

. An excellent problem-solver, able to quickly grasp complex systems and

identify opportunities for improvements and resolution of critical

issues.

. Experience in successfully working and adapting with cross

functional/geographical teams.

. Competent in executing projects using both Waterfall and Agile models.

. Proficient in extreme refactoring as part of continuous/Agile delivery

model.

. Expertise in team mentoring, pair programming and test driven

development (TDD).

. Working Knowledge of X12 (similar to HL7).

. Theoretical Knowledge of HealthCare standards like DICOM & Medical

Imaging.

Technical Skills:

Programming Skills : Java/J2EE, C++

Markup Languages : HTML/DHTML/XML, XSLT, CSS

Web Systems : Apache/Tomcat Server 5.0

Scripting Languages : JavaScript, Shell, AJAX

Frameworks : Struts 2.3, Hibernate 4, Spring MVC 4.0

Database : PostgreSQL, SQL Server, MySQL, Oracle

Database Admin Tools : PostgreSQL Admin

Application Server : Apache/Tomcat Server 7.0, Websphere

8.5, JBoss 5.1

Version Control : SVN, CVS

Testing Tools : SAHI testing tool

Build Tools : CruseControl / Maven

IDE : Eclipse, Websphere RAD

Operating Systems : Windows, Unix and Linux flavors

Software Developing Methodologies : Agile, Waterfall

Others : Edit plus, SSH, Tortoise Client, Fire Bug, MS Office, iText

API's,

jOpenDocument API, jQuery, Open Office 3.0, JMS

Education and Certification:

. Master of Computer Applications from Visvesvaraya Technological

University, Belgaum KA, India

. Bachelor of Science from Karnatak University, Dharwad KA, India

Professional Experience:

MphasiS Corp, Phoenix, AZ July 2006 till

date

Role: Project Lead

Project: Javelina

Javelina is an MphasiS owned next generation, browser-based healthcare

claims and benefits platform that addresses the business performance needs

of health plans, third party administrators (TPAs), and insurance carriers

and self-insured organizations. Core Javelina modules include Benefit plan

configurations, Broker and sales commissions, Customer relationship

management, Integrated imaging and workflow, Complex contract, CDHP account

management, Member Setup, COBRA processing etc.

During this time, I have been involved in different parts of the Javelina

application and have developed a very strong Business and Architectural

Knowledge of it. Currently, working on COBRA (Consolidated Omnibus Budget

Reconciliation Act), Correspondence, & Re-Insurance modules which require

integration with several modules in the Javelina application and other

independent softwares like Open Office suite etc.

Provide guidance as an SME to MphasiS/HP customers like Keenan HeathCare,

APWU (American Postal Workers Union) and HCC Medical Insurance Services.

This helps MphasiS /HP get a competitive edge over other suppliers in the

project.

Responsibilities:

. Lead developer and single point of contact for critical Reinsurance

COBRA and Correspondence modules of Javelina Healthcare Claims

Processing platform.

. Proficient in handling View layer of the web application using XTTM

(XML Transaction Tag Mapping), a customized MVC architecture similar

to Spring MVC.

. Working knowledge of Control and Model layers of the Spring MVC

architecture by using a proprietary framework called ecijdk.

. Working knowledge of DataGrape (compares to Hibernate), a high-

performance Object/Relational persistence and query service data layer

framework.

. Experience in JQS (Javelina Queuing System) framework similar to JMS,

a queuing system which aims at automation of business process, in

whole or part, during which documents, information or tasks are passed

from one participant to another for action, according to a set of

procedural rules.

. Extensively used X12 as the API standard to process EDI files (similar

to HL7) such as 834 and 837, which helps in processing member & claim

information.

. Used JDBDiff framework, a database comparison and synchronization

system which seamlessly integrates with the build and deployment

process.

. Used TableSync framework, a master-slave replication system that

includes all features and capabilities needed to replicate large

databases to a reasonably limited number of slave systems.

. Experience in using Javelina Extensible Integration Environment

(JXIE), an architectural approach for creating and using business

processes, enabling enterprise wide interface and integration with

latest technologies.

. Hands on expertise using SAHI testing tool.

. Prepare test plans as defined in GAD QMS that was used during unit and

system integration testing and document the same in Test Manger tool.

. Conduct reviews of all work products in various phases of the project

based on the methodologies and templates defined.

Environment: J2EE, JDBC, JSP, Servlets, HTML, Web services, JQuery,

JavaScript, XML, SQL Server, SOAP, iText API, Apache tomcat, JUnit, JIRA,

CruseControl, Windows, Linux, Unix, Solaris operating systems

WDC, Bangalore (India)

Project 1: Bill Payment and Web Payment Subsystems

Duration: March 2006 till June 2006

Role: Software Engineer

The Bill Aggregator via, Bill Junction, Mumbai person will initiate Bill

payment transaction. This request will be received into the middleware

server using HTTPS protocol. This middleware program stores the bill

invoice details into the data base table. The bill payment subsystem will

be polling the database table for any new invoice details received from the

bill aggregator. If the details are found, then a MT message buffer is

generated and that will be sent to the customer SIM via Gateway. Customer

sends back one message buffer to the bill payment subsystem.

If the customer agrees to pay the amount then Bill Payment subsystem builds

an ISO message and sends it to the bank switch. If the bank switch returns

successful code then bill payment subsystem produces two receipts, one is

sent to customer to mobile, and other receipt is sent to the Bill

Aggregator (BillJunction) server using HTTPS protocol.

Customer uses the 3rd party-shopping (like Amazon.com, ebay.com etc) site

that is integrated with mChq application to purchase some items on the net.

On selecting mChq as payment mode the customer is asked to enter his mobile

number that contains SIM loaded with mChq customer application. As the

customer clicks on the submit button a timer is started. This timer is set

to 5 minutes and it runs backward. With the start of the timer a request is

generated and it is forwarded to middleware Servlet program. This

middleware is responsible for generating the transaction payload that would

be understood by the Web Payment subsystem and it puts the message buffer

into the JMS queue. Web Payment subsystem processes the transaction payload

and stores it into the memory. Meanwhile customer should send a transaction

message to the Web Payment subsystem using the information displayed on the

WEB page. When this customer initiated transaction message is received into

the subsystem, it validates the transaction using the information received

from the customer and information received from the middleware server. If

the validation process yields true then confirmation message is sent to

customer. After receiving confirmation from the customer the Web Payment

subsystem generates the two receipts. The Customer receipt is sent back to

the customer mobile, and other receipt is stored in to the database table

against that transaction. The mChq payment plug-in will be polling the

database table and if it finds the receipts against the particular

transaction it displays the message "Transaction Completed".

Responsibilities:

. Design and Development of the bill payment and web payment subsystems

using Java, J2EE technologies.

. Design and implementation of middleware application using Java, J2EE

technologies.

. Assisted in the development of shopping site for web payment subsystem

demo. This prototype was built using technologies such as JSP,

Servlets, Core Java, HTML, Javascript, CSS and Tomcat Server.

. Extensively used JMS technology to process the transaction payload.

. Actively participated with client and team members to design &

development of client's requirement.

. Hands on experience in preparing technical documents using UML like

Class diagrams, Object diagram, Sequence diagram.

. Extensively used Eclipse IDE to develop and test Java programs.

. Used Unit testing tool JUnit to test the implementation. Integration

testing with different components like Gateway, Switch etc.

Environment: J2EE, JDBC, JSP, Servlets, HTML, Web services, JavaScript,

XML, SOAP, iText API, JBoss Application Server 3.0, Apache tomcat, JUnit,

JIRA, Windows, Linux, Unix, Solaris operating systems

Project 2: PC Merchant

Duration: January 2006 till February 2006

Role: Software Engineer

This is a Swing based module that the merchant will be using instead of a

mobile phone. This module will be installed in the PC at the merchant

outlet along with the SIM card reader device and the SIM card loaded with

mChq merchant application. The application has a login screen and four

menus for three different transaction types, viz. Sale, Void and Refund and

one for reports. Whenever the user (Merchant) performs a Sale transaction,

the transaction details are fed to the SIM card to get a MO message. This

merchant message buffer will be put into the JBoss queue and from that

Gateway picks it up and sends the message buffer to the customer SIM. A

timer is started and waits for the receipt back from the backend

transaction processing system. If within two minutes the module does not

get any receipt or error messages then it displays the time out message on

the screen. It also provides facility to get report of all the transaction

between two specific dates, last month's, current month's etc.

Responsibilities

. Design and implementation using Java Swing technology.

. Assisted in the development of report generation tool using iText API.

Extensively used JMS technology to process the message transactions.

. Actively participated in team discussions regarding client's

requirement.

. Hands on experience in preparing technical documents as per company

standards using UML like Class diagrams, Object diagram, Sequence

diagram.

. Extensively used Eclipse IDE to develop and test Java programs.

. Used Unit testing tool JUnit and participated in integration testing

of the system with the VTAS bundle

Environment: Java Swings, JDBC, JSP, Servlets, JavaBeans, HTML, JMS,

JavaScript, SQL Server, iText API, Apache tomcat, JUnit, JIRA, Windows,

Linux, Unix, Solaris operating systems

Project 3: mChq (Mobile Cheese) Application

Duration: November 2005 till December 2005

Role: Software Engineer

mChq is mobile financial application being developed with the idea of large-

scale use of mobile-to-mobile payment between two parties (Customer -

Merchant).

mChq merchant initiates the transaction by sending a payment request. The

message is sent to VTAS the mChq backend system through the gateway. The

customer and merchant validations are done here and the request is sent to

the customer. The customer replies to the merchant's request through a pin

based confirmation. Upon receiving the customer confirmation VTAS verifies

the sensitive data like pan and track2. If the verification is successful

then initiates the funds flow. Now VTAS prepares an ISO message and sends

it to the bank switch. When the module gets transaction successful message

from the bank switch then it generates and sends the transaction receipts

to both the customer and the merchant mobile.

Responsibilities:

. Worked on the VTAS Module handling the new requirements and altering

the module to suite the changing requirements.

. Actively participated in team discussions regarding client's

requirement.

. Hands on experience in preparing technical documents as per company

standards using UML like Class diagrams, Object diagram, Sequence

diagram.

. Extensively used Eclipse IDE to develop and test Java programs.

. Unit testing and integration testing with other components of the mChq

system like Gateway, Perso SIM etc.

Environment: J2EE, JDBC, JSP, Servlets, HTML, Web services, JQuery,

JavaScript, XML, SQL Server, SOAP, iText API, Apache tomcat, JUnit, JIRA,

Windows, Linux, Unix, Solaris operating systems

Project 4: Design and Implementation of DB Fa ade

Duration: July 2005 till October 2005

Role: Software Engineer

This is a subproject for VTAS. In VTAS 1.6 version all the queries are

embedded in the source files, and the VTAS bundle was using JDBC statements

to do record manipulation. To remove these two from the VTAS bundle this

subproject was initiated. Here I made a separate XML file for writing

queries. This XML file will be parsed and the required query will be taken

into the application and a prepared statement out of this query is

generated. This statement is executed for the desired output. The output to

the calling method will be returned as a Vector object. For parsing the

"queries.xml" file JAXP API's SAX parser is used and for Database

connection-pooling c3p0 Database connection pooling is used.

Responsibilities:

. Complete designing and implementation of the DB Facade system.

. Used XML parsing API - JAXP to process the XML file which contains SQL

queries.

. Experienced in using c3p0 database connection pooling for database

connectivity and transaction.

. Actively participated in team discussions regarding client's

requirement.

. Hands on experience in preparing technical documents as per company

standards using UML like Class diagrams, Object diagram, Sequence

diagram.

. Extensively used Eclipse IDE to develop and test Java programs.

. Unit testing and integration testing of the system with the VTAS

bundle

Environment: Java, JDK, Eclipse, EditPlus, JDBC, XML, SQL Server, SAX

Parser, JAXP API, JUnit, JIRA, Windows, Linux, Unix, Solaris operating

systems

Hew Software Technology, Bangalore, India

Project 1: Hew Support Application

Duration: April 2005 till July 2005

Role: Software Engineer

HEW Support application is helpful for the companies that under take the

support activities.

When any customer calls for the support like spare parts replacement or the

regular maintenance service then the service desk person receives the call

and enters the relevant information into the application. One more thing

here is that the service desk person tries to solve the problem at hand by

giving some suggestions to the customer to try and solve the problem. For

this the KEDB that is "Known Error Database" can be referred. This contains

some known errors and the possible solutions to those errors on the

particular machine type. If the problem is not solved at service desk then

it is escalated to Service engineer.

The Problem management team is module that helps a group of engineers who

are specialized in one area. There will be a head among the problem

management team. The service engineer escalates the call to the problem

management team head when he founds the problem cannot be solved by him.

The head assigns the problem management engineer to guide the service

engineer. If the problem can be solved by only replacing the part then

problem management engineer requests the part replacement that needs to be

approved by the team head. If approved then it is transferred to the CAB

(Change Advisory Board). The change advisory board is the final authority

to approve or disapprove the change request. If request is approved then it

is escalated to the logistics to release the part to be replaced.

The architecture of the application conforms to the Design Patterns,

STRUTS, EJB and RDBMS.

Responsibilities

. Involved in the analysis and design of the whole application.

. Assisted in Database design for the application.

. Development of modules;

o Service Desk

o KEDB

. Problem Management Team

. Change Advisory Board (Under development)

. Manual testing of each module.

Environment: J2EE, JDBC, JSP, Servlets, HTML, Web services, JQuery,

JavaScript, XML, SQL Server, SOAP, iText API, Apache tomcat, JUnit, JIRA,

Windows, Linux, Unix, Solaris operating systems

Project 2: Hew Sales Windsor

Duration: January 2005 till March 2005

Role: Software Engineer

HEWSales is a Sales Force Automation solution that helps enterprises in

efficient sales follow-ups and can help contribute towards enhanced

sales effectiveness. HEWSales provides access to information in real time

across the functional areas of Sales and Marketing. In all HEWSales helps

geographically dispersed sales teams to seamlessly integrate and

collaborate to shorten sales cycles, resulting in higher sales.

HEWSales Windsor is a web based sales force automation product with the

help of which the sales person can be in touch with his sales related data

irrespective of the geography he is present.

The architecture of the application conforms to the Design Patterns, STRUTS

and RDBMS.

Responsibilities:

. Developed Products Module.

. Extensively used design patterns such as Singleton, Factory.

. Actively participated in team discussions regarding client's

requirement.

. Hands on experience in preparing technical documents as per company

standards using UML like Class diagrams, Object diagram, Sequence

diagram.

. Extensively used Eclipse IDE to develop and test Java programs.

. Manual testing and bug fixing of Contacts & Products module

Environment: Java, J2EE, JDBC, JSP, Servlets, HTML, Web services,

JavaScript, XML, SQL Server, SOAP, JBoss application server, JUnit, JIRA,

Windows, Linux, operating systems

Project 3: Expenditure Manager

Duration: September 2004 till December 2004

Role: Software Engineer

The product- Expenditure Manager has been developed for tracking the

expenditure incurred by the organization. This product has three modules;

. Administrative Module

- This module is used to handle the user information like creation,

update and deletion of users for different departments.

. User Level Module

- Users from different departments use this module to update the

expenditure incurred by the respective departments.

. Reports Module

- Based on the privileges the users can access the different reports

like yearly, monthly, in between two dates.

Responsibilities:

. Involved in Analysis and design of the application.

. Development of all the modules.

. Extensively used design patterns such as Singleton, Factory.

. Actively participated in team discussions regarding client's

requirement.

. Hands on experience in preparing technical documents as per company

standards using UML like Class diagrams, Object diagram, Sequence

diagram.

. Extensively used Eclipse IDE to develop and test Java programs.

. Extensively used iText API's to generate PDF reports.

. Unit testing and complete manual testing of the application.

Environment: Java, JDK, J2EE, JDBC, JSP, Servlets, HTML, JavaScript, XML,

SQL Server, iText API, JBoss application server, JUnit, JIRA, Windows,

Linux, operating systems

Personal Information:

Visa Class: H-1B

Expiry Date: March 2017

Contact this candidate