From March 2008 - November 2008 I worked as an Intermediate Project Manager at Weka Publishing House. In this position I was responsible for planning, co-ordination and approval of a software framework project, called "Weka Document Manager".

The Software Framework enables Weka to develop and maintain own software products in the area of spezialized technical information.

The Framework consists of an authoring component as well as a runtime environment and provides a customizable default user interface. Technologies used in software development are Spring, Hibernate, Ajax, Freemarker and BIRT. It supports virtually any JEE Application Server as well as a set of different databases like PostgreSQL, MySQL and Oracle.

The framework itself is developped in co-operation with the Munich based technical service provider IDV AG

During my work period at MindMatics I was responsible for the development of the "Content Manager" application.

This software enables registered customers to upload content, adapt it to all known formats and publish it under a short code/keyword, in a subscription context or in wap portals.

At download time the platform determines the downloading device and delivers the best fitting content. The connected device database is self-updating by fetching and interpreting unknown handset profiles. Missing content formats are post generated additionally.

The platform supports all popular mobile content formats from monophonic ringtones to realsounds, from bitmap graphics to video and java games, themes etc.

The platform is implemented in Java and supports SOAP Webservices and RMI. It consists of a rich client application and a JEE middle and persistence tier.

My role was the team lead, software architecture, resource planning and quality assurance.

Find out more at the Mindmatics website.

At Apollis I was responsible for design and development of a software system for device detection and administration.

The Java based J2EE component detects a device at a wap request by its user agent or UAProf reference and returns the belonging capabilities to the calling application, which processed the request with device specific content. Device capabilities were determined by parsing the UAProf information.

The component was designed in the modular webservice approach of the Apollis software stack.

I worked on this project as a Software Engineer and was responsible for design and implementation and maintenance of the component.

After the company closed down, the software component was sold to a major German Telco.

The implementation and usage of messaging components were part of my work at Apollis (2003-2004) as well as at Mindmatics (2004-2007). Content encoding, bulk message processing, scheduled delivery were common tasks.

The handling of inbound traffic and its processing in SMS dialogs as used for lotteries, order and chat applications are core business processes of both companies.

Synchronous handling for on-request interfaces as well as asynchronous handling for mass traffic are the common issues in those cases.

The big amount of data that one has to cope with especially in the area of mass messaging is a common issue.

At Apollis I designed and implemented a service component for handling of operational data. The component was implemented as SOAP service using J2EE technologies. On the persistence layer JDBC calls as well as Oracle Stored procedures were used.