Kevin Mehio

• Chenega's contract was completed once UAT was finished.
• Took time off to pursue other interests.

• Worked on software development team building application for DOE.
• Used Agile development methodology with Jira by Atlassian to support this process.
• Performed code reviews.
• Estimated work hours and tracked progress using Scrum methodology.
• Performed application demonstrations for customer.
• Assisted with User Acceptance Testing (UAT) by writing test cases and providing support during UAT.

• Worked on the software development team building an application for the military.
• Took over as Software Lead when the previous team lead was moved to another project.
• Ran daily office hours to help other developers with any issues.
• Used Agile development methodology with Jira by Atlassian to support this process.
• Estimated work hours and tracked progress using Scrum methodology.
• Worked on the integration team to integrate the application with multiple outside organizations using a variety of methods – REST, SOAP, GraphQL, File Import/Export.
• Performed code reviews.
• Wrote test scripts for the work done during the sprint.
• Performed sprint deployments from the development to test environments.
• Performed sprint deployments from the test to production environments.

Semi-retirement to address family caregiving and bereavement.

• Provided technical support for a print-on-demand (POD) company that also provides training for starting and running an online eCommerce business
• Updated and maintained multiple websites run by the company
• One website was used to list the best-selling products on the major eCommerce platforms (Amazon, eBay, Etsy, Cafepress, etc.) based on keywords entered by the user
• This website was written in PHP
• Another website was used to create the designs to be printed on the POD products
• Created a prototype web application for the Custom Happy warehouse to track orders throughout the production process
• The web application was written with Microsoft Visual Studio 17 using C#

• Took over the development of an existing financial application. This application was written in Visual Basic 6 with an Oracle 8.17 backend.
• Took over maintenance of the case management module. The application was written in Oracle Forms 6i and Oracle Reports 6i using the same backend as the financial application.
• Participated in the user working groups that defined the case management module requirements.

• Was Software Lead for 6 different projects. Five of the projects used PowerBuilder. The last project was Java front-end connected to a J2EE server
• Authored code fixes and enhancements for inclusion in future code releases and patches.
• Coordinated deployments of new software, feature updates and fixes.

• Developed a PowerBuilder application framework used to prototype a parking revenue tracking system that was presented to the University of North Carolina
• This was the second iteration of the framework first developed for the CCFE project, rewritten in PowerBuilder 6.5
• Framework was the foundation for the AXIS framework
• Responsible for the software architecture of the company web-based application framework
• This Java framework is the third iteration of a framework first developed for the CCFE project

• Took over as lead developer of the TrakR team
• TrakR is used to track delivery revenue and to track amount owed to the drivers
• All drivers are independent consultants
• Written in PowerBuilder 6.5, TrakR uses an Access backend
• Responsible for all development work
• Corrected several key reports, Invoice and Contractor Settlement Detail, and made some minor modifications in preparation for version 1.0 release

• Took over as lead developer of the APSS team
• APSS is the automation of a paper process and is used to schedule people on vans, buses, or aircraft trips and to track their progress
• Written in PowerBuilder 7.0, APSS uses an Informix backend
• Responsible for all development work
• Original development team was three developers, but team was reduced to one developer in November 1999
• Extensive modifications have been completed, hitting every major module in the system, including moving all business logic from database stored procedures and triggers into the APSS application
• APSS went into production in April 2000

• Responsible for writing the technical documentation for a system used to send out several hundred thousand emails daily, support website to take customer orders, and send customer orders to the appropriate clients
• The system was composed of stored procedures, HTML templates, Visual Basic code, JavaScript, Perl script, XML documents, and Active Server Pages
• Used Select Enterprise Modeler to create UML class diagrams, object sequence diagrams, use case diagrams, and object collaboration diagrams

• Lead developer of the AXIS team
• AXIS was a framework used to apply client specific business rules to claims, member, and provider data for import into reporting datawarehouses
• These rules were often too complicated to be performed by other data translation tools
• Written in PowerBuilder 6.5, AXIS used a distributed, multi-tier architecture and an Oracle backend
• Responsible for the design and the development of the AXIS framework
• The AXIS framework used many of the PowerBuider 6.5 advanced capabilities - distributed processing, server push, asynchronous calls
• Assisted other developers in developing AXIS business rules and did the initial application runs for the client
• Some of these processes would take several hours to several days to complete, processing up to 20 million records

• Responsible for Amisys-to-Oracle claims module design document and production run checklist
• These documents were deliverables to the client
• Documents required approval before project was considered complete and payment received

• Designed and developed AXIS framework using an internally developed PowerBuilder application framework
• Responsible for presenting AXIS to development team, to technical staff and managers outside the AXIS team, and for making sure all development fit within the AXIS framework

• Took over as lead developer of the PaSS team
• PaSS was a client/server application used to track payphone revenue, to estimate when a payphone was full, and to schedule payphones for collection
• Written in PowerBuilder 5.0, PaSS used a MS SQL Server backend
• Responsible for setting up the development environment, for year 2K conversion, for several rounds of modifications, and for training two developers to take over system maintenance

• Lead developer of the CCFE team, Cleanser Module
• CCFE was the re-engineering of VBH's claim adjudication process
• Written in PowerBuilder 5.0 and Visual C++ 4.1, CCFE used a multi-tier architecture and an Oracle backend
• The Cleanser module contained the application logic and was written in PowerBuilder
• The Cleanser module also contained several visual components used to display claim data and these components were written in Visual C++
• Responsible for writing 90% of the PowerBuilder code and for coordinating the PowerBuilder and the C++ development
• Used OLE/COM for the communication between the C++ and PowerBuilder components
• Also responsible for CCFE letter generation and printing, using PowerBuilder and Microsoft Word

• Responsible for CCFE Design Document - Cleanser Module
• This was a client deliverable and required approval before development could begin