Development Lead Resume Profile
Brief Experience Details
- Over 13 years of industrial experience demonstrating great software design and development skills
- Managing Leading various projects as dev. lead which includes both FTE and vendor teams
- Having working experience of Software development on Legal, Telecom and Banking domains
Work experience includes
- Web, Windows, Windows Services, Windows Phone 7.5 and 8.0 applications development using .NET C .NET
- SQL SERVER application development which includes database, SSIS, SSRS
- Delivering sessions in IT Showcase and DPE events on new technologies namely: SQL SERVER, Windows Phone 8 application at various colleges and developer community
- Good interaction ability, required for onsite/offshore application development model
Software Expertise:
- Development Skills : C .NET, VB.NET, VB, PL/SQL, ADO.NET, SSIS
- Web Technology Scripting : ASP.NET, ASP 3.0, VBScript, Java Script HTML
- Framework : .NET 1.1, 2.0, 3.0, 3.5, 4.0, 4.5 , Web Api, OData Services
- Database : MS SQL Server 2014 CTP, 2012, 2008 R2 , 2005, 2000, MS-Access
- Report Generations : SSRS 2014 CTP, 2012, 2008 R2 , 2005 , Data Dynamics Active Reports 2. 0
- Software Tools:
- Development Tools : Visual Studio 2013/ 2012/ 2010 /2008 SP1 /2005 /2003, ER Win, DB Pro
- Configuration Control Tools : Visual Studio Team Foundation, Visual Safe Source, Clear Case
- Build Deployment Tools : Microsoft Octopus, Cruise Control, TFS Build Controller
- Other Tools : Microsoft Office, MS VISO, Microsoft Project Plan, FxCop, StyleCop, Sitrion 2.0, WSE,
Project Experience:
Confidential
Position: Senior Development Lead
- EAS maintains a SOA based service layer on top of SAP function modules to enable integration with external systems. This is required as external applications MS needs data from SAP or wants to store data in SAP. This is achieved though the development of SAP data Integration service, this service is used to perform various task at SAP. C application are developed and used to connect and executed various functional modules in SAP for completing the required work flow. These C application are primarily divided into following categories:
- Generation 2 Servers Web services
- This is an old style of designing which was created to support web service for the external application. A typical .NET web services is created by using SAP RFC details. In this process various RFCs required by external application are mapped to respective web method, with various complex and generic parameters are mapped to respective generic data types or collection of generic data types.
- Generation 3 WCF serveries
- WCF is currently being used for all the new developments, we develop these services using Sitrion ServiceStudio. Sitrion ServiceStudio is a visual studio add-in which provides various project templates to create WCF. It provided a structured way of connecting to SAP, getting relevant RFCs and parameter details. Once these details are obtained necessary mapping of these RFCs and parameters to a meaningful names is done using visual studio addin. Finally necessary code base for WCF is generated by Sitiron. We use sapBinding and expose this as the endpoint to be consumed by various application.
- Generation 4 Web API-RESTFul serveries
- These are new generation services designed and developed to support mobile scenarios and any system-to-system integration that requires a services that provides/ receives data using RESTFul and OData style services. This is used to provide light weight data with very high performance. Currently in this type of services the application content is set to use only JSON. These services are developed as ASP.NET Web API applications.
- This layer uses SAP BizTalk Adapter Pack 2013/2012/2010 to manage connectivity to SAP and RFC libraries Low level SAP connectivity library used by SAP BizTalk adaptor .
Technology Landscape:
- ASP.NET, C .NET, OData Services
- Tools: VSTF, VS 2013 WEB API, WCF, WS projects , Sitrion 2.0, Fiddler, WCFTestClient, WCFConfiguration, WS-WS testing tool
- Framework/ SDK: .Net 4.5, 3.5, WCF LOB Adapter SDK, Microsoft BizTalk Adapter for SAP, 64-bit Unicode SAP RFC SDK
- Build and Deployment: Automated Build using TFS Build Controller and Deployment using Octopus
- Duration: On Going
Contributions:
Designs and developed solutions
- Lead vendor and FTE team size 2 in completing the project, partnered with various cross teams for collaborations of project and development integration testing
- Developed Automated Unit test, build and deployment scripts.
- SIT/ UAT/ Production support to Application Support Teams
- Prepared various SDLC documents and work items namely Technical Specification Documents, deployment operation Guide, Logged various Dev Risks
Confidential |
Data Mediation Layer DML applications are designed and developed for gathering, aggregating and transforming source data from velocity data store into consumable format for Convergent Charge CC which is fed into SAP. These application are currently running in older version of OS Windows SERVER 2008 R2 and SQL server 2008 R2 making it out of compliance. So as part of engineering stay current initiative we are upgrading these applications. This upgrade will allow us to standardize platforms to Windows 20012/ SQL Server 2014. As part of upgrade analysis phase we used SQL advisor, SQL Profiler trace to come up with various SQL server 2014 compliant issue list. This included both SQL announcement and final support issue details. This project also included various integration level testing e.g. Source/ Destination/ BODS/ File generation connectivity testing. Project included tasks for pre and post upgrade performance analysis to ensure that there is no visible degradation of performance.
- Technology Landscape: SQL SERVER 2014 CTP , SSIS, SSRS, SQL Jobs
- Tools: VSTF, VS 2012, SSDT 2013 for creating DB projects
- Build and Deployment: Automated Build using TFS Build Controller and Deployment using Octopus
- Duration: On Going
- Contributions:
- Designs and developed upgrade solution
- Create all the dev. related activities and task list. Maintained project tracker to manage various task and completion status by various team member
- Lead vendor and FTE team size 4 in completing the project, partnered with Redmond team for various cross team collaborations
- Developed Automated Unit test, build and deployment scripts.
- SIT/ UAT/ Production support to Application Support Teams
- Prepared various SDLC documents and work items namely Technical Specification Documents, deployment operation Guide, Logged various Dev Risks
Confidential |
Fortress web site provides various external application with screening functionality against denied-party list maintained by MS. It screens customer details against a Denied-Party List DPL to determine whether to apply a trade sanctions on the customer. This project was done to support the SAP GTS R3 system upgrade from 8.0 to 10.1. This web site was developed as a wrapper to WCF layer. The Subscriber details was sent to this web site as part of HTTP request. Fortress web site use to parse this http request XML Format and depending on the allowed request screening type, either Real Single or Batch Multiple it use to either call sync WCF Service or stored request in the form of XML in file share for async request processing. These requests based on the request type were process at GTS SAP R3 system and results were sent accordingly.
- Technology Landscape: ASP.NET, C .NET
- Tools: VSTF, VS 2013
- Framework/ SDK: .Net 4.5
- Build and Deployment: Automated Build using TFS Build Controller and Deployment using Octopus
- Duration: On Going
- Contributions:
- Designs and developed end to end solution
- Lead vendor and FTE team size 2 in completing the project, partnered with Redmond team for various cross team collaborations
- Developed Automated Unit test, build and deployment scripts.
- Create Unit testing tool that was used by SIT/ UAT team
- SIT/ UAT/ Production support to Application Support Teams
- Prepared various SDLC documents and work items namely Technical Specification Documents, deployment operation Guide, Logged various Dev Risks
Confidential |
This project is related to migrating product related data from Microsoft Product application MS Product, a legacy application to ERP System SAP . This allows MS to manage their products in much more systematic way. As the product data migration to SAP will be done in stages phases, therefore there is need to maintain MSProduct until data migration is complete. During this transition phase, products data will be available at both sources and has to be made available to MS centralized corporate data f location Feedstore and allow various downstream application to use it. PDSPlus was designed and developed so that data from both the sources could be merged, filtered from MSProduct and SAP sourced data to create full consolidate Product table data for Feedstore to consume it. This project implemented delta and full feed logic to support data processing mechanism to improve end to end data processing performance. In delta mechanism both MSP and SAP was allowing PDSPlus to pull differential data. PDSPlus had the logic which used differential data, to find insert/ updates/ deletes from both the sources, merge the both source data, perform necessary look up for various domain values and finally populating various table and views for Feedstore to pick up the data.
- Technology Landscape: MS SQL Server 2008/2000 R2 , SSIS
- Tools: VSTF, VS 2012/ 2008, SSDT for DB project, Batch Scripting
- Build and Deployment: Automated Build using TFS Build Controller and Deployment using Octopus
- Duration: 6 Months
- Contributions:
- Designs and developed various solution and worked on various quarterly CRs/ enhancements
- Create all the dev related activities and task list. Maintained project tracker to manage various task and completion status
- Lead vendor and FTE team size 2 in completing the project, partnered with Redmond team for various cross team collaborations
- Developed Automated Unit test, build and deployment scripts.
- SIT/ UAT/ Production support to Application Support Teams
- Prepared various SDLC documents and work items namely Technical Specification Documents, deployment operation Guide, Logged various Dev Risks
Confidential |
- PDS is related to Microsoft Pricing processes, these process are undergoing constant changes and expansion. This included fundamental modifications to Pricing systems, data structures and flow. This changes included shift in pricing source data systems from MS Pricing and MS Product to SAP. So this project was developed and designed to do the following:
- Resolve differences where possible to provide interim continuity in downstream consumption of pricing data.
- To reach future-state schema that will any new and enhanced downstream pricing data requirements.
- PDS provides a degree of back-compatibility to insulate end-of-life applications and to allow long-term applications greater flexibility in planning development efforts required for alignment.
- Technology Landscape: SQL SERVER 2008 R2
- Tools: VSTF, VS 2008 with SSDT for DB projects
- Build and Deployment: Automated Build using TFS Build Controller and Deployment using Octopus
- Duration: 3 Months
- Contributions:
- Designs and developed solution for a critical production issue
- Developed Automated Unit test, build and deployment scripts
- Cross Team collaboration to get necessary sign-off for SIT and UAT
- SIT/ UAT/ Production support to Application Support Teams
- Prepared various SDLC documents and work items namely Technical Specification Documents, deployment operation Guide, Logged various Dev Risks
Confidential |
- Feedstore is primarily a data store for moving large volume of data sourced from publishers to downstream subscribers. It provides a central location for storing corporate data. Data is published to Feedstore via flat files, SQL Replication, Linked Servers pull and/or SSIS push/pull . The data from publishers is imported, scrubbed, transformed and finally accumulated to the Feedstore data warehouse as per dataset collection of publisher data specific to business rules. This works on subscriber/ publisher model. Feedstore provides standardized data interfaces for downstream subscribers to access data thus providing single interfaces between multiple applications. Corpnet subscribers can pull data from Feedstore using 3DAPI Direct Data Delivery which are simple stored procedure calls. 3DAPI subscribers have a choice to retrieve full snapshots or deltas. Data is delivered to extranet subscribers using SQL Server Push Replication using another process call SCM3D as 3DAPI does not work across firewall. Feedstore includes lots of components which are used for various reasons, following are the details of various components used by the entire system.
- Feedstore Layer This layer includes Staging, Accumulate, Feedstore updates and distribution process. These process is followed so that at each level specific set of data is processed.
- FeedStore PreStaging Layer: Pre-staging is a stage when the data is loaded in a specific database by the publisher either via replication or via DTS or via custom process that needs to be either normalized or de-normalized or merge various sources or even simple pull the data from various sources so that data is ready for FeedStore for data distribution. Dataset- DTE01, PDSPlus , ERECO1, SCC101, COLL01
- FeedStore Service Platform: This framework allows the data to be presented in the format in which BizTalk gateway could consume it. This provides data in XML format. Here the data volume is less in comparison to Feedstore data pull. Many downstream application use this method to pull the data from FeedStore Warehouse
- FeedStore Empowerment Tools:
- Web Site Development: EnterpriseData, InsideEDS
- Web Service: PersonPosition
- Windows Services: SubscriptionBak, KickerStaging
- Warehouse/ Distribution/ Web Server Upgrade projects: As part of stay current we upgraded most of the warehouse DBs used across Feedstore to latest version OS Windows Server 2008 R2 and DB SQL Server 2008 R2 data centre
- SP.NET Web API.s type of services the ication.tudio addin and finally generating necessary code base required for WCF. We use S
- Technology Landscape: ASP.NET, C 2.0, 3.0 , SSRS, SSIS, MS SQL Server 2008/2000 R2
- Tools: VSTF, VS 2012/ 2008, SSDT
- Build and Deployment: Automated Build using TFS Build Controller and Deployment using Octopus
- Duration: 6 Months
- Contributions:
- Designs and developed this solution
- Worked on various quarterly CRs, and enhancements,
- Lead vendor teams in completing some of the quarterly releases
- Developed Automated Unit test scripts
- Developed scripts to automate build and deployment.
- SIT/ UAT/ Production support to Application Support Teams
- Prepared various SDLC documents and work items namely Technical Specification Documents, deployment operation Guide, Logged various Dev Risks