Candidates About

 

Aakshi Handa

PROFESSIONAL SUMMARY

·         8.8+ years of hands-on experience in analysis, design, development and testing of web and Core Java Applications using Core Java (1.5,1.6) and J2EE technologies 

·         SCJP 1.5 Certified Programmer.

·         Currently working for Comcast Client in Philadelphia, Pennsylvania.

·         Worked for AT & T Client in Atlanta, Georgia.  

·         Worked for Target Pharmacy Client in Minneapolis.

·         Strong experience on J2SE technologies like Core Java (Collections, Core Object based concepts, Garbage collection and Exception Handling)

·         Well versed with complete Software Life Cycle Development (SDLC) process which includes Analysis, Designing & Developing, Testing, Implementing and documenting the entire life cycle using various methodologies like Waterfall, Agile and Scrum.

·         Proficiency in using design patterns like MVC, Singleton, Factory, Front Controller.

·         Experience in using Core java concepts to get the use of reusability of the code.

·         Expertise in using HTML, DHTML, CSS, Java Script, JSP in designing web pages.

·         Experience in application development using J2EE technologies like Servlets, JSP, JDBC, JNDI, EJB and Web Services.

·         Exposure to XML related technologies like SAX and DOM, JAXB.

·         Experience in working with the Frameworks like Struts and Spring IOC, Spring MVC.

·         Experience in working with O/R- Mapping technology like Hibernate.

·         Strong Experience in databases like Oracle 10g.

·         Expertise with variety of Application Servers like Oracle 10g AS, Weblogic 11 and tomcat.

·         Sound knowledge of IDE tools like RAD, eclipse, WSAD & MyEclipse

·         Experience in developing middle tier applications using JMS.

·         Extensive knowledge in Clear Case, TFS and SVN Configuration Tool, Github

·         Proficiency in using the architecture like MVC2

·         Strong experience in SOA(SOAP), Object Oriented Programming, SDLC, OOAD and UML

·         Possess excellent problem solving and leadership skill

·         Well versed in required project design documentation.

·         Motivated team player with ability to work under minimal supervision possessing excellent communication, interpersonal, analytical and problem solving skills.

·         Strong domain experience in HealthCare, Pharmacy, Retail, Ecommerce, Travel, Telecommunication.

 

TECHNICAL SKILLS

Languages	Java 1.5,1.6
J2EE Technologies	Servlet 2.5, JSP 2.0, JDBC 3.0, JNDI, JSF
Distributed Technologies	EJB 2.0 (session beans), Web Services, SOAP(WSDL)
Databases	Oracle 10g, SQL Server 2005
Web/Application Servers	Oracle 10g AS, Web Logic 11, Web Sphere 6.1, Apache Tomcat 5.0, Jboss4.0.3
Frameworks	Struts 1.2, Spring IOC
Web Development	Ajax, XML 1.0, XSLT, HTML, Java Script, JQUERY
Scripting	Shell script,
O/R Mapping Technologies	Toplink
UML Tools	Microsoft Visio
IDE	Eclipse 3.2, RAD 6.0, My Eclipse 6.0.1, Visual Studio 2010
Version Control	Rational Clear Case, SVN,VSS
Testing Tools	Load Runner, Junit, Mercury Quality Center, Bugzilla's Bugs Tracking Tool, QPASA, JIRA, RALLY
Operating Systems	Windows XP/7, Unix, MS - DOS
Tools	Toad 9.0 for Oracle, SQL Developer, Oracle Access Manager(OAM), Sonar, Hudson, Jira, SPLUNK
SoftwareDevelopment Methodologies	Agile, Waterfall, Iterative

 

 EDUCATION

·         Masters in Computer Applications, INDIA

·         Bachelors in Science (Math/Physics), INDIA

 

 WORK EXPERIENCE

 EMPLOYER: Cognizant Technology Solutions (AUG 2014 –Till Date)

 

Comcast Cable Communications INC, Philadelphia                                                                              Dec 2015 –Present

Project: MERLIN System Implementation

Role: Java Architect

The job of Merlin is to coordinate the ingest of a variety of data from the domains of TV, Movies, Sports, and Music, construct a canonical representation of entities from each of these domains based on multiple data sources, and make this data available via a set of highly available, low latency web services.

Merlin consists of five major components or component groups. These include the Id Manager, the Ingestor, the Combine, the Editorial Component, and the Service Component

The application is primarily used in Comcast to receive data from different providers and send it further to downstream systems. Within the application, we have the following modules

ID Manager

The id manager is responsible the creation and deletion of Merlin entity ids. It is also responsible for maintaining the association between Merlin IDs and the id spaces provided in a given feed. It can be queries with a forign id form one of the feed providers and it will report back as to whether this entity exists and if so what its Merlin ID is. For entities for which there is no Merlin ID, and ID can be created using the ID Manager. The creation of new IDs will be performed such that a similar creation based on the same foreign key will almost always produce the same Merlin ID. Additionally a Merlin ID service can synchronize with another ID service such that at the end of the sync process any association found in the source service when the process began is identical found in the target service.

Ingestor

The ingestor performs the scheduled download of feeds from third party providers. It analyzes the feed and determines which if any of the meta-data in the feed associated with a particular entity has changed. If the data has changed, then it queries the ID manager to determine what Merlin IDs are associated with the changed feed data. These entities are flagged as changed. The changed row is then persisted to the Cauldron database. Once all feed changes have been persisted, then unique changed IDs are sent to the Combine component via a queue. In the case of new entities in the feed, if this is the primary feed for an entity type then the Ingestor will have the ID Manager create a new ID for this entity and proceed as is done in the case of a metadata change.

Task Queue

The task queue is a simple queue which holds Merlin IDs which need to be processed. It needs to support prioritizing different tasks. This may be implemented as a prioritized queue or as several queues where the higher prioritized queues are processed first. Implementations under consideration include memcacheq, active mq, or possible a custom database backed implementation.

Combine

The Combine component reads Merlin IDs from the queue populated by the Ingestor which have changed due to some change in a source metadata feed. The component then queries the ID Manger to determine the set of associated entities which can be used in the construction of a canonical representation of the entity. The Combine component uses these id associations to query the Cauldron database as well as the editorial database for the feed data needed. It then updates its Mortar database with the newly constructed representation and sends the updated representation to the next stage of processing. The second stage of the Combine determines which of the service end-points feed data needs to be updated based on the Merlin entity that changed. Using the Merlin ID, it queries the Mortar database for any data not in the representation passed to it and updates the service end-points. The service end-points then update their database and invalidate their cache.

Editorial

The editorial can be used to edit existing entities or create new ones. In the case of an edit a Merlin id is provided and the Editorial system queries the IDManager to determine what feed id associates are available for the Merlin entity in questions. The system uses this information to query both the Cauldron and Mortar databases and presents the editor with both normalized representation of entity found in Mortar as well as the representation provided by the feed data. The user can then edit any editable field associated with that entity. When the editor indicates that their edits are complete, then the updates are persisted in the editorial database. The representation of the editorial update captures the Merlin ID, the editor, the table, the field, and the value in Mortar for which this change is the new source. The Combine queue is populated with the Merlin id of the id which has been changed. When this update is processed by the Combine and the other downstream components, the editorial change will propagate to the service end-points.

Responsibilities:

·         Involved in development, testing phases of Software Development Life Cycle (SDLC) in the application.

·         Preparation of HLD design documents and reviewing the LLD's

·         Used Agile Methodology like scrum for Software Development.

·         Used Struts Framework for the model and controller layer.

·         Have specifically worked on Editorial Section.

·         Used log4j for the error logging purpose.

·         Used JIRA for bug logging and tracking for the internal testing.

·         Involved in unit testing.

·         Used SVN as a version tool.

Environment:  Eclipse, Core Java 6.0, JSP, Struts 1.2, EJB 2.0 SOAP UI, SOAP based Web Services, Hibernate, HTML, CSS, XML Java Script, Oracle 10g, WebLogic 11, SVN, Jira, Ajax, JQuery.

 

 

AT & T, Alpharetta                                                                                                                               Aug 2014 –Dec 2015

Project: One Point Universal System (OPUS) System Implementation

Role: Java Architect

One Point Universal System (OPUS) is an AT&T system enabling employees to effectively activate, assist customers with their wireless and wireline accounts, and perform Point-of-Sale (POS) activities.

The application is primarily used in AT&T retail stores; however, other users have access to perform specific functions. Within the application, we have the following modules

·         Welcome Center

·         pCA

·         Activations

·         Customer Service

·         Administration

·         Inventory functions

·         Sales

·         Converged Services (Sell Wireline Products)

·         Link to other applications and Web sites (Quick Links)

·         TITAN

 The purpose of POS module is to sell/ return a pharmacy transaction and collect the payment from the guest. The sale of the product is also the logical end of a transaction.

The purpose of Inventory Management module is to maintain, check, correct On Hands counts of Inventory on the store.

Responsibilities:

·         Involved in development, testing phases of Software Development Life Cycle (SDLC) in the application.

·         Preparation of HLD design documents and reviewing the LLD's

·         Used Agile Methodology like scrum for Software Development.

·         Used Struts Framework for the model and controller layer.

·         Have specifically worked on the following Interfaces Activations, POS and Upgrade Flows.

·         Used SLFlog4j for the error logging purpose.

·         Used Hudson for the Build and deployment on servers.

·         Used MQC, JIRA for bug logging and tracking for the internal testing.

·         Involved in unit testing.

·         Used SVN as a version tool.

Environment:  Eclipse, Core Java 6.0, JSP, Struts 1.2, EJB 2.0 SOAP UI, SOAP based Web Services, Hibernate, HTML, CSS, XML, XLST, Java Script, Oracle 10g, Shell Scripting, WebLogic 11 ,SVN, Jira ,Ajax, Handlebars, JQuery.

 

 

EMPLOYER: TATA Consultancy Services (NOV 2010 –AUG 2014)

 TARGET, Minneapolis                                                                                                                          Aug 2012 –Aug 2014

Project: Target Pharmacy (PDX - EPS) Enterprise Pharmacy System Implementation

Role: Technical Lead

The PDX EPS software system is being built to meet the Target Pharmacy Store operation's needs. It is an online transactional software system; enabling pharmacy to fulfill the needs of prescription filling, drug dispensing and verification activities.

EPS continues the PDX legacy with its intuitive design, agile processing power, enhanced safety features, ease-of-use, and flexible architecture. PDX Enterprise Pharmacy System (EPS) features a Java-based technology platform and Oracle database technology and delivers a host of advanced features and powerful integrations. Built on a robust, scalable platform, EPS is available in two implementations Rapid Fill and Workflow—each offering pharmacies the flexibility that suits their in-store needs. And now, EPS is available within a hosted environment, giving pharmacies a choice that matches their infrastructure requirements.

PDX EPS Rapid Fill

EPS Rapid Fill organizes prescription filling tasks into Data Entry, Fill (optional) that provides NDC verification, Pharmacist Verification and Will Call. The pharmacy user chooses, based on their user role, what task to perform next. From the Data Entry window, users can process prescriptions one at a time as they receive them from patients or select the next available prescription from the Rx Filling Queue.

Users can also use the Rx Filling queue to enter multiple prescriptions for one patient at one time. Further, prescriptions received via IVR and the web interfaces are placed into the Rx Filling Queue.

PDX EPS Workflow

EPS Workflow was developed based on the principle that the system should deliver the next, highest priority task to the right individual designated to receive the work at the right time. Each task is in the prescription filling process is segmented to allow you to create workstations in the pharmacy where staff members are responsible for only those tasks that are required to their skill set. Based on the promised time of the task, the user role, and the workstation configuration, the system delivers the right task at the right time to the appropriate user. The system helps ensure the pharmacy staff is always working on the highest priority tasks. Also, it allows configuring the workstation based on the business needs, staff level, and the layout of the store, and it can quickly change the configuration throughout the day.

 The purpose of POS interface is to sell/ return a pharmacy transaction and collect the payment from the guest. The sale of the product is also the logical end of a pharmacy transaction. In order for the pharmacy system EPS to be in sync with the POS system, this interface provides two way integration between POS and EPS. The integration provides the necessary financial controls in place, restricts some mistakes for the store user and increases productivity by automating the sale/ return process.

 The purpose of Inventory Management Interface is to maintain correct On Hands counts of Inventory on the store. Order and receive /vendor Credits /Unsalables are the sub modules that help in maintaing the correct On Hands Count on the store.

Responsibilities:

·         Involved in development, testing phases of Software Development Life Cycle (SDLC) in the application.

·         Preparation of HLD design documents and reviewing the LLD's

·         Used Agile Methodology like scrum for Software Development.

·         Used Struts Framework for the model and controller layer.

·         Used Spring MVC Framework.

·         Have specifically worked on the following Interfaces POS, eprescribe, Drug File, Vendor Credit, Unsalable, On Hand Count.

·         Used SOAP UI for testing EPS POS Communication.

·         Created hibernate mapping files, Configuration file and POJOs for the database interaction.

·         Used SLFlog4j for the error logging purpose.

·         Used Hudson for the Build and deployment on servers.

·         Used Sonar for the code analysis and to maintain the code quality.

·         Used MQC for bug logging and tracking for the internal testing.

·         Involved in unit testing.

·         Involved in Performance testing using testing tools like Load Runner.

·         Used TFS and SVN as a version tool.

·         Awarded with the Pharmacy Inventory Management Creativity award from target client.

Environment:  MyEclipse, Core Java 6.0, JSP, Struts 1.2, Spring MVC, SOAP UI, SOAP based Web Services, Hibernate, HTML, CSS, XML, XLST, Java Script, Oracle 10g, Shell Scripting, Jboss 4.0.3, Sonar, TFS, SVN.

 

CVS Caremark, Rhode Island                                                                                                                  Nov 2010 –Aug 2012

Project: RxConnect-PSI2 Implementation

Role:  Sr. JAVA Programmer

The RxConnect software system is being built to meet the CVS Store operation's needs. It is an online transactional software system; enabling pharmacy to fulfill the needs of prescription filling, drug dispensing and verification activities. The system captures all interactions with the CVS customer and provides functionality to fill the prescription in an easy and efficient manner. The system will support the CVS enterprise organization consisting of multiple pharmacies dispersed across a large geographically area.

The overall objectives of the PSI2(Pharmacy Service Initiative) project are:

·         Improve pharmacy service and customer experience

·         Make sure we are capitalizing on our current upside opportunities

·         Ensure we have capacity, capabilities, and processes to successfully deliver 
future initiatives

·         Where possible, improve productivity and reduce costs

 

Responsibilities:

·         Involved in development, handling deliverables, tracking status phases of Software Development Life Cycle (SDLC) in the application.

·         Used Struts Framework which is based on MVC architecture Used Ajax and java script validation on the client side.

·         Used Waterfall Methodology for Software Development.

·         Used log4j for the error logging purpose.

·         Created Day end complex batch processes for the end of the day processes on the database with keeping them performance tuned.

·         Involved in using all core Java Concepts into the application for the reusability of the code.

·         Experience in using the Collections in java E.g. ArrayList, HashMaps etc.

·         Created database triggers for the trading scripts on the database to reduce the load on the application.

·         Used Ant script for building the project.

·         Worked on bug fixing and enhancements on change requests.

·         Participated in ensuring quality through code reviews and testing

·         Involved in unit testing.

·         Performed code reviews and supervised junior developers

Environment:  Eclipse 3.0.1, Core Java 5.0, JSP, Swings, Struts1.2, AJAX, HTML, CSS, XML, XLST, Java Script, Microsoft Visio, Ant, Oracle 10g, Web Logic 9.2, Microsoft VSS.

 

EMPLOYER:  HCL Technologies (JAN 2007 –OCT 2010)

 

PEARSON EDUCATION, NJ                                                                                                                    Oct 2009 - Oct 2010

Project: PTG (Pearson Technology Group) Implementation

Role: JAVA Developer

Pearson PLC have Publishing Control System, which is a distributed business system supporting the information needs of Marketing, Editorial, Art & Design, Production, Manufacturing, and Business Management. PCS contains applications that automate various stages of publishing business flow. These applications process product and business information to support tactical and strategic functions of the target business unit. These applications interact with each other to provide the complete business flow.

The Application Pearson Technology Group Module (PTG) is made by HCL Technologies for Pearson.

The intent of this project is to customize the existing applications of PCS suit such that PTG business unit can use them to effectively perform their day to day publishing activities. PTG currently uses CES and IMS applications for their Manufacturing and Inventory functions respectively. As part of this project, a Web based Editorial, Production and Marketing solution is being developed for PTG. This will include rewriting PPS into a Web Based application, customizing existing PIMS application and adding new Manufacturing & Inventory features currently missing in CES and IMS.

Responsibilities:

·         Involved development, handling deliverables, tracking status phases of Software Development Life Cycle (SDLC) in the application.

·         Involved in using all core Java Concepts into the application for the reusability of the code.

·         Used Agile Methodology like scrum for Software Development.

·         Experience in using the Collections elements in java E.g. Array List, Hash Maps etc.

·         Involved with BA for the requirement modeling

·         Involved in development & testing.

·         Developed and implemented the MVC Architectural Pattern using Struts Framework including JSP, Servlets, Form Bean and Action classes.

·         Implemented Struts Action classes using Struts controller component.

·         Used Ajax/JavaScript for validation.

·         Used Stateless session EJBs for the various distributed components used in the application.

·         Used JDBC (connection pooling) to access data from database servers.

·         Used Toplink as ORM tool and wrote Toplink mapping files.

·         Worked with QA team for testing and resolve defects.

·         Used Tortoise SVN as Version control.

·         Participated in ensuring quality through design, code reviews and testing

Environment:  MyEclipse 6.0.1, Core Java 5.0, JSP, Struts 1.2, EJB, HTML, XML, XLST, Java Script, Microsoft Visio, Sybase 12.5.6, Windows 2000 Professional

 

 

 

AIR CANADA, Toronto                                                                                                                        Feb 2009 - Sep 2009

Project: Air Canada-JTB

Role: Java Programmer

ITA Software is an airline IT services solution provider to help leading airlines and travel distributors dramatically reduce costs, drive revenues, simplify their business, and improve customer service. ITA is currently involved in developing airline reservation system in partnership with Air Canada (Canada's official carrier) which will offer an enhanced reservation system, improved inventory control, and an advanced departure control system.

Java Test Bed is a proprietary framework developed by ITA Software for the automation testing of an Airline Reservation System. The tool allows the users to create test scripts in Java for testing the GUI and XML interfaces.

Responsibilities: