IT Consultant

Requirements engineering & technical analysis
Within all my projects I analysed, defined, maintained and documented requirements for various technologies and processes, for instance:

• Processing logic and data analysis for various inbound and outbound interfaces based on ETL (IBM InfoSphere Datastage) for a credit risk management application.
• Analysing, advancing and maintaining a reporting data mart and its data model for credit risk monitoring in Oracle DB.
• Analysing, modelling and implementing a logical data model for a data hub in Oracle DB, holding customer data, rating information, currency exchange rates and financial products.
• Implementing data quality checks and exception handling for the loading procedure of the above-mentioned data hub.
• Analysing and specifying of technical workflows in UC4, including workflow sequence, defaulting rules for late or incomplete data deliveries, data quality checks and error handling
• Analysing and specifying KPI for early warning indicators with respect to data quality and the respective processes in case of an early warning
• A reporting platform enabling the senior management to monitor the status of daily operations in terms of efficiency and effectiveness based on Qlik Sense.
• Reporting platform for operational risks allowing ‘slicing and dicing’ based on SAP Crystal Reports.
• In-house developed data quality monitoring based on Oracle SQL, shell scripting and Qlik Sense.
• Workflow for contract lifecycle management using ARIS Express, BPMN and EPC, for modelling and documentation.
• Analysing a cross-division processes for limit excesses monitoring, handling and escalation, as well as assessment of possible support via information systems.
• Analysing performance issues and data quality issues within an IBM credit limit management solution.

• Test staging on different environments (unit test, integration test, system test, user acceptance test) as well as the setup for those environments.
• Development of customized data sets to keep processing time short but still test all essential parts.
• Timeline for each testing phase in alignment with the SCRUM sprints.
• Test reporting to the project management and stakeholder.
• Standard test cases and their minimum acceptance criteria and dependencies.
• Minimum standards for test documentation using Confluence and JIRA.
• Test automatization for daily interface/data consistency checks based on Oracle SQL which were sent to all involved testers via UC4 controlled jobs.

• Running a system with an availability of 24/5 (SLA level); however, continuous improvements lead to de-facto availability of 24/7. Within the last 13 months the nightly on-call duty had to intervene only two times.
• Introducing new interface architecture, based on Oracle DB and IBM InfoSphere Datastage, which reduced the processing time of data transformation drastically and therefore increased the system availability.
• Designing successfully a procedure to automatically upgrade and extract the software parametrisation on demand (based on Oracle DB, UC4 and in-house developed ETL). According to the software manufacturer this was only possible manually.
• Defining new standards for documentation of operational tasks, using Confluence and JIRA, which was advanced to an internal wiki and set new guidelines for the whole IT department.
• Introducing e-mail notifications for users and management based on ORACLE SQL, shell scripting and UC4. This e-mail notifications decreased the processing speed of credit applications by 75 %.
• All releases to production where successful, without introducing additional bugs and fully documented (change log, sprint history, acceptance testing protocol, roll-back scenarios and smoke tests results).