I am the sole developer responsible for the technical design, development and on-going support and enhancement of a company-wide reporting system. Highlights include:* Front-end GUI application and web-based access allowing users to request & view ad-hoc reports with user-defined parameters* Batch system performing ETL (Extract/Transform/Load) of the required data and enabling the automated production and email dispatch of scheduled reports. * Output produced in HTML, CSV or XLS (Excel) format.* Developed in Java using JavaFX for the GUI, Tomcat and Spring for the web front end and a MYSQL database for configuration and ETL data storage.* Highly configurable, allowing colleagues with no Java expertise to define reports using parameterised SQL, with the output format specified using either predefined HTML table & chart formats or template Excel spreadsheets.Other ad-hoc utilities such as an automated file transfer tool and an email log stats import & analysis tool.

My final role at Cattles was as a Java analyst/programmer, designing and developing software to provide the business with both historical and 'what-if'​ information regarding the historical production of CCA related notices, and to produce replacement notices where needed.Prior to this I performed a lead analysis role on a large data migration project (816 attributes across 31 entities), responsible for the specification of the data sourcing and transformation requirements. The source data consisted of over 174 million transactions across over 2.2 million accounts for over 1.4 million customers, stored in two disparate databases (one on iSeries, one on AIX) with considerable data quality issues making this a challenging role. This project was a great success: in the words of the IT director, it was "on time, under budget and with one of the smoothest migrations I've ever experienced in 33 years of being in IT". Before that I worked on a number of projects, primarily around replacing a legacy back-end loan management system with a new third-party system and subsequent enhancements to this system My primary responsibilities included:Investigating IT systems and producing detailed technical documentation (data flow diagrams, entity relationship diagrams etc.) to enable the ongoing support and maintenance of these systems.Reviewing functional specifications produced by third-party suppliers to ensure proposed solutions will meet the requirements of the business and conform to appropriate technical standards and conventions.Specification of interfaces and data mapping between internal and external systems.Investigating day-to-day production-related issues and proposing solutions, particularly where the problem and/or solution spans multiple systems.Developing ad-hoc reports, data extracts and utilities using Java and SQL.

During my time at E.ON my responsibilities included:Providing support and maintenance for the Credit Management and Finance systems. This includes investigating and resolving bugs and data issues, producing ad-hoc reports, data extracts and data loads, and developing enhancements to the systems.Large client/server system with a HTML/Javascript front-end connecting via XML web services to a server side consisting of Oracle PL/SQL, Pro*C and Korn shell scripts running on HP-UX and Solaris.Developed the ‘Houston’ SLA monitoring system. Houston is a web-based application that provides up-to-date information on the status of various SLA-related parameters, such as batch suite completion, system availability etc.

For the last 3 years of my time at Severn Trent Systems (STS), my responsibilities were:Providing support and enhancements for the MainMan application, used by STW to manage their maintenance work.Large client-server application, over 750,000 lines of code written in a combination of C++, PL/SQL, Pro*C and Korn shell scripts, running on HP-UX and Solaris using Oracle databases, with a Windows NT front-end.Application was originally written by a third-party and suffered from severe performance issues. Severn Trent Water were unhappy with the support they received from the original authors so they purchased a source code licence and passed it on to us.Created and maintained development environment based on source code provided by original authors.Departmental PVCS (version control) administrator.Managed the handover of project work into the support environment.Prior to the above, I was responsible for:Providing support for a customer information and billing system.Large COBOL application running on Digital Tru64 and Solaris using an Oracle database. Joined just prior to the first live implementation, and my first task was therefore to ensure the necessary tools and procedures were in place to enable us to provide support. This task was particularly challenging as our first client was based in Australia.In June 2003 I was made redundant from STS as part of a reorganisation (which involved 90 redundancies, the great majority of which were technical staff) due to a change in business focus.

Provided support and maintenance for a range of systems including stock control, sales order processing, financial reporting and warehouse automation.The majority of these systems were in CICS/COBOL using DB2 on an IBM mainframe, although I was also involved in some UNIX and Oracle work.Responsible for Y2K analysis for ‘RAPIDS’ application, which was written in VB using an Oracle database on UNIX.

Responsible for implementing both new credit application processing systems, and enhancements to existing ones, for several high-street banks.These systems were in both CICS/COBOL and PASS (an in-house 4GL) running on an MVS mainframe.Covered the full development life-cycle, from producing initial specifications to implementing the final system.Responsible for supporting these systems on a day-to-day basis. Extensive contact with the clients, in both a consultancy and support capacity. Co-ordinated the technical development as well as taking ownership of the areas of the code that required a higher degree of technical complexity than usual.

For most of my time at ISL I was the sole member of the software department.Responsible for all aspects of software development, from defining the client’s requirements to producing and installing the completed system.Produced user-guides, demonstrations and end-user training. These systems were written in a variety of 4GLs running on MS-DOS.