Stephan H.-Development, Tester

Refactoring the CRM system of an IT service provider This includes a complete refactoring of the legacy application, in particular the migration from JDK 1.6 to JDK 25 and the replacement of self-developed infrastructure components, such as the Object-Relational Mapper (ORM) and the frontend template engine, with current standard components based on Spring Boot. At the same time, the previous close coupling between the back end and front end is being removed and the application is being migrated to a modern microservice architecture. The microservices are implemented as independent, reusable units and operated in autonomous Docker containers. The backend components are provided through REST APIs. As part of the project, CI/CD and deployment processes for the container-based microservice architecture were also established and automated using GitLab CI. At the same time, quality assurance is ensured through the implementation and automation of unit, integration and system tests. The work is supported by AI, particularly through the use of GitHub Copilot and LM Studio (gpt-oss) for code development and prompt engineering. Position: Software development, software quality assurance, tester, test automation engineer

Work performed:

• Analysis of the functional and technical use cases (workflows, involved processes/systems, communication paths, security requirements)
• Code refactoring (code cleanup, optimization)
• Dependency refactoring
• Refactoring of REST services (SpringBoot)
• Refactoring of the ORM layer
• Test execution / test automation (Serenity, Selenium, Playwright, JUnit)
• Establishment and automation of CI/CD pipelines for build, test and deployment steps in a Docker/microservice environment Team size: 2 people IT basis: Technologies: Java (JDK 25), Spring Boot, Hibernate, JPA, SQLServer, MariaDB, Docker, Yaml, Markdown, JSON, HTML/CSS, REST Tools: IntelliJ, DBeaver, Git/GitLab, GitHubCopilot (AI) Work management: Gitlab Tests: Serenity, Selenium, Playwright, JUnit Platform: Linux, Windows Version control: Gitlab Build management: Gitlab CI

• Development of an operational contract information system. This is primarily used as an order management system - for transferring existing contracts as well as creating and providing new contract bundles.

• Sales agents can use it to order new services, modify existing ones and migrate service types, as well as provide customers with pricing information.

• This supports the marketing of new services and the replacement of old services for existing customers in particular.

• Existing data is also imported and processed (ETL) within the system and provided through services for further use in the portal front end.

• Analysis of the functional and technical use cases (workflows, involved processes/systems, communication paths, security requirements)

• Further development / creation of frontend components (React/JavaScript)

• Design and implementation of business logic

• Creation of functional and technical component documentation

• Test execution / test automation (Cypress, test coverage)

• Team size: 8 people

• Technologies: React, JavaScript, Rest (JSon), Yaml, Markdown, MariaDB (SQL), Docker, Swagger, Cypress

• Tools: Webstorm, ReactDeveloperTools, VisualStudioCode, Word, DBeaver, Git/GitLab

• Work management: Gitlab

• Platform: Linux

• Build management: Gitlab

• Anonymization of statistical data. A government authority is required to prevent statistical values from being traced back to original values and thus to ensure their anonymization, among other things.

• Mathematical algorithms using noise factors and overlay matrices are applied for this purpose.

• It must be ensured that the deviations in the overall results to be reported, caused by overriding, remain within a defined range.

• For this purpose, the relevant departments/applications are to be provided with REST and SOAP web services that accept these original values (in some cases up to 1 million records), process them depending on the use case and return the overlaid values.

• In addition, the respective functional behavior must be tested for correctness and performance, and corresponding unit and system tests must be implemented.

• Analysis of the functional and technical use cases (workflows, involved processes/systems, communication paths, security requirements)

• Design and implementation of service interfaces (REST & SOAP services)

• Design and implementation of service objects (XML/XSD, JSON)

• Design and implementation of business logic

• Design and implementation of the persistence layer (data structures, XML, CSV)

• Quality assurance (design and execution of unit and integration tests, test coverage, code QA Sonar, security QA OWASP)

• Test automation (JUnit, Mockito, SoapUI)

• Team size: 4 people (subproject team), 25 people (overall project team)

• Technologies: JavaEE 8/Jakarta EE 10, SOAP, REST, Groovy, CSV, XML, XSD, Swagger, OpenAPI

• Tools: Eclipse, JBoss AS 7.4 & 8.0, SoapUI, Word, Powerpoint, PDF, Maven, Mockito, Sonar, Jacoco, OWASP

• Work management: Jira, Confluence

• Platform: Windows

• Build management: Jenkins

• Unbundling of railway electricity. An internationally active railway electricity company had to technically separate its market roles (user and supplier) throughout the system.

• The new system was to cover all previously supported business cases, from recording through billing, while also meeting the new requirements and regulations of the BNetzA.

• The newly created system landscape had to undergo continuous QA for all ongoing processes.

• Analysis of the functional and technical use cases (workflows, involved processes/systems, communication channels, security requirements)

• Documentation of the functional use cases and the involved processes/systems

• Design of functional and technical test cases/scenarios (including load and performance tests), focusing on system and system integration tests

• Design of test specifications and test plans (including acceptance documents, QA)

• Design, implementation and automation of tests / regression tests (including logging test results in HP QC)

• Recording of defects in HP ALM / QC

• Team size: 14 people (Supplier stream), 60 people (total project team)

• Technologies: SOAP, Groovy, HP ALM/QC, JMS/TibcoEMS (MDB), Oracle SQL, Java 8

• Tools: SoapUI, Word, PDF, Innovator, Maven, TestRunner framework, JUnit

• Work management: Jira, HP ALM/QC

• Platform: Linux (SLES12), Windows

• Build management: Jenkins

• Shipping Management System. Fundamental redesign of a shipping management system that had reached its technological limits.

• The new system covers all business cases and is upgraded to the current technology level.

• Analysis of the functional use cases (screens, customer requests, support team requirements)

• Analysis of the technical use cases (workflows, involved backend systems, communication channels, security requirements)

• Documentation of the use cases using UML2

• Creation of the system documentation

• Team size: 12 people

• Technologies: Java 7, JEE, REST, JPA/Hibernate, Log4J

• Tools: Word, Powerpoint, Google Docs, Enterprise Architect, Netbeans 7, JBoss 7, BPMN

• Work management: Redmine

• Tests: JUnit

• Platform: Linux, Windows

• Development of a gateway between a classic and an IP-based telephony system. Providing access to the integrated answering machine via a specific gateway with SOAP services.

• Structural and impact analysis of the telephony system interfaces including performance measurements

• Design of the process architecture of the gateway/interface

• Design of the persistence layer

• Design of an infrastructure to ensure high system availability

• Planning and participation in implementation work

• Quality assurance (planning and execution of module, integration and acceptance tests)

• Consulting during system production deployment

• The project was carried out within an iterative agile process model (SCRUM)

• Team size: 5 people

• Technologies: UML, Java 7, JEE, Axis, XML, XSD, SOAP, ShellScripting, JPA/Hibernate, oAuth1, Log4J, SCRUM

• Tools: Enterprise Architect, Netbeans 7, Tomcat 6, XMLSpy, MS-SOAP-Toolkit, Putty, SSH, SoapUI, MS-Access, Apache Commons Configuration

• Work management: Jira, Confluence

• Tests: JUnit

• Platform: Linux

• Build management: Jenkins, Maven

• Mobile webshop frontend. Enabling shop access via an Android app for a multi-tenant shop infrastructure.

• Native app with configurable branding layout.

• Identification and documentation of the relevant use cases

• GUI design

• Design/definition of the software architecture for a configurable GUI layout

• Implementation as a native app in Java

• Planning, execution and documentation of manual system tests

• Team size: 3 people

• Technologies: Java, Web-Service, REST, JSON, OAuth

• Tools: PENCIL, Balsamiq, Netbeans with Android-Plugin

• Work management: Confluence, Jira

• Platform: Android

• Build management: Jenkins, Git

• Development of a system for automated GUI tests. Development of an infrastructure for the automated testing of dynamic user dialogs for GUI-based services.

• Analysis of the applications to be tested

• Design and implementation of a screen and template parser

• Creation of the system documentation

• Team size: 2 people

• Technologies: PHP, Perl, JavaScript, HTML5, CSS3, JQuery

• Tools: Zend Studio

• Work management: Jira, Confluence

• Platform: Linux

• Build management: Jenkins, Ant

• Development of a mobile frontend for a project controlling system. Enabling the recording of actual expenses via mobile devices for field service employees.

• Identification of the key use cases

• GUI design using mockups

• Design and implementation of the REST services

• Implementation of the iOS app

• Application testing, software distribution

• Team size: 1 person

• Technologies: Objective C, REST, JSON

• Tools: XCode 4, iPhone/iPad emulator

• Work management: Jira, Confluence

• Platform: OSX

• Migration of telecommunications backend services to the OSGI platform. Conversion to an OSGI-compliant architecture to simplify operation and service updates without a restart.

• Analysis of the existing services, gathering requirements for the migration

• Technical project management

• Design and implementation of the new software components

• Planning and execution of tests on the acceptance system

• Packaging and delivery

• Consulting on software delivery/distribution/quality assurance

• Creation of the system documentation

• Team size: 3 people

• Technologies: Java, Axis, XML/SOAP, OSGI, Spring-Framework

• Tools: Enterprise Architect, Eclipse, Tomcat 6

• Work management: Jira, Confluence

• Platform: Linux

• Build management: Jenkins, Ant

• Redesign of an existing SOAP-based communication platform to achieve WS-I compliance. Modification of the email service API according to the standards of the Web Services Interoperability Organization (WS-I).

• Technical analysis of service requests and their parameter structures

• Redesign of the services into a WS-I-compliant SOAP structure

• Generation of the technical service interfaces using SOAP toolkits

• Validation, testing, and documentation of the new service interfaces

• Implementation of extended services

• Team size: 2 people

• Technologies: Java, Axis, XML/SOAP

• Tools: Enterprise Architect, JBuilder, Eclipse, XML-Spy, MS-SOAP-Toolkit, Tomcat 6, Jetty, Putty, SSH, SoapUI

• Work management: Jira, Confluence

• Platform: Linux

• Build management: Jenkins, Ant

• Migration of a reporting system (DWH). Migration of the DWH and data provisioning processes from Debian-Linux/Oracle to AIX/DB2.

• AS-IS analysis of the existing system

• Design and implementation of data transformations for AIX & DB2

• Deployment to the test system and packaging for the production system

• Design of the ETL for the staging area

• Implementation of an application for controlling external processes and data compression

• Execution of tests and creation of reports

• Consulting during production system commissioning and user training

• Team size: 8 people

• Technologies: Java, Axis, XML/SOAP, JSON

• Tools: Enterprise Architect, Netbeans, XML-Spy, MS-SOAP-Toolkit, Tomcat, Jetty, Putty, SSH, SoapUI, MS-Access, DB2, Oracle, Informatica

• Work management: Confluence, Jira

• Platform: Linux, AIX

• Build management: Hudson, Ant

• Conversion of existing communication service components to a Service-Oriented Architecture (SOA) and an Enterprise Service Bus (ESB). Redesign of the message-based communication infrastructure.

• Technical analysis of the existing services and identification of weaknesses

• Validation and testing of existing service interfaces and their documentation

• Redesign of the services into a WS-I-compliant SOAP structure

• Leading workshops to develop the new service structure

• Team size: 6 people

• Technologies: Java, Axis, XML/SOAP

• Tools: Enterprise Architect, Eclipse, XML-Spy, MS-SOAP-Toolkit, Tomcat, Jetty, Putty, SSH, SoapUI

• Work management: Jira, Confluence

• Platform: Linux

• Build management: Hudson, Ant

• Development of a central WEB service platform as the central access point to the services of a portal operator.

• Implementation of the central service platform as a SOAP web service

• Design and implementation of the rights concept and management

• Design and implementation of access to distributed backend systems

• Design and implementation of data mapping and consolidation

• Testing on the acceptance system and migration to the live system

• Team size: 2 people

• Technologies: Java, Axis, XML/SOAP

• Tools: Enterprise Architect, JBuilder, XML-Spy, MS-SOAP-Toolkit, Tomcat, Jetty, Putty, SSH, SoapUI, MS-ACCESS

• Work management: Confluence, Jira

• Platform: Linux

• Build management: Hudson, Ant

• Development of WEB services for a VOIP system. Connecting existing backend systems to a VOIP system via a specific gateway.

• Integration of a multi-subscriber database

• Design and implementation of data mapping

• Design of the relevant use cases (data dependencies)

• Design of a response matrix as an automaton

• Conducting acceptance tests

• Creation of the system documentation and migration to the live system

• Team size: 8 people

• Technologies: Java, Axis, XML/SOAP

• Tools: JBuilder, MySQL, Apache, Putty, SSH, MS-SOAP-Toolkit, Tomcat, MS-Access

• Work management: Jira, Confluence

• Platform: Linux

• Build management: Jenkins, Ant

• Development of WEB services for a VOIP system. Connecting existing backend systems to a VOIP system via a specific gateway.

• Analysis of incoming data

• Identification of relevant use cases

• Design and implementation of data transformations

• Design of a response matrix as an automaton

• Execution of acceptance tests and creation of system documentation

• Migration to the production system

• Team size: 6 people

• Technologies: Java, Axis, XML/SOAP

• Tools: JBuilder, MySQL, Apache, Putty, SSH, MS-SOAP-Toolkit, Tomcat, MS-Access

• Project management: Confluence, Jira

• Platform: Linux

• Creation of a workforce planning system. Providing planning and controlling tools for service teams based on the Cognos suite.

• Analysis of the available operational data

• Design and implementation of the data model for the OLAP data storage system

• Design of cube models and data extraction processes

• Development of automations for cube creation (including fail-safe mechanisms)

• Design of audit reports (Report-Net)

• Creation of documentation for the OLAP datastore and analytical cube models

• Conducting user training

• Team size: 10 people

• Technologies: Data Warehousing, Business Intelligence, ETL

• Tools: Cognos Transformer, Cognos Contributor, Cognos Analyst, Cognos Connection, Cognos Report-Studio, Powerdesigner, Toad, Oracle 10.1

• Project management: Clearcase

• Platform: Windows

• Development of test scenarios for a customer database. Development of automated regression tests for a customer database with a WEB service API.

• Analysis of the existing access functions for the customer database

• Documentation of typical use cases for interaction according to the developer concept

• Development of test scripts for a generic simulator

• Execution and documentation of tests (pass/fail scenarios)

• Bug reporting

• Team size: 2 people

• Technologies: Java, Axis, XML/SOAP

• Tools: JBuilder, MS-SOAP-Toolkit, Apache, Putty, SSH, Tomcat

• Project management: Confluence, Jira

• Platform: Linux

• Extension of a CRM/HR system.

• Design of GUI templates (HTML)

• Script development to extend the GUI templates

• Analysis and restructuring of existing functionality

• Implementation of new functions

• Creation of the user manual

• Team size: 4 people

• Technologies: Java

• Tools: Powerdesigner, Eclipse, MS-SQL-Server

• Work management: Confluence, Jira

• Platform: Windows

• Redesign of the transaction module for a mobile payment system. Solution for correctly processing the payment reference in the backend of a payment system.

• Analysis and documentation of the existing system architecture

• Specification/documentation of the new target architecture with extended functionality

• Team size: 1 person

• Technologies: PL/SQL

• Tools: Oracle 8i, Toad

• Platform: Unix

• Development of a universal and flexible rating system.

• Management of an international development team

• Training and coaching in Java, OO, relational databases

• Design, implementation and testing of the application framework in Java

• Design and implementation of the data storage system

• Team size: 10 people

• Technologies: Java, PL/SQL, HTML, CSS, UML, JSP, JavaScript, XML

• Tools: PowerDesigner, Enterprise Architect, Oracle 8i, Toad, Visual Age for Java, JBuilder, JUnit, Tomcat, MS-Project

• Work management: Confluence, Jira

• Platform: Unix