Germar Heinicke - Resume

Resume as of 2024-03-01

Contact

Germar Heinicke

Address: St.-Cajetan-Str. 30, 81669 München, Germany
Phone: +49. 172. 899 22 69
Email: gh at germarheinicke dot de
Web: www.germarheinicke.de

Area of Expertise

Freelance software developer since 1981. Experience:

  • more than 15 years in IT and telecommunication industries
  • about 10 years in aviation and railway industries
  • team size: very small teams and up to more than 300 members
  • team structure: multicultural teams, multiple time zones
  • project sizes: some weeks up to more than 1000 person years

Since 2002 I focus on software development infrastructure and on information logistics:

  • change request management
  • configuration management
  • document management
  • information architecture
  • problem reporting
  • review processes
  • revision control
  • software production and deployment

Preferred working environment:

  • development of complex products
  • international teams (teams in different countries and time zones)
  • multicultural teams

Languages:

  • German (first language)
  • English (fluent)

Education

Fachhochschule München, Informatik (Computer Science) 1978 - 1983

Degree: Diplom-Informatiker (FH)

Thesis: Implementation of the Graphical Kernel System (GKS)

Experiences: Tools, Languages, Frameworks

Programming and Data Description Languages

In alphabetical order:

awk, C, CSS, HAML, HTML, Java, Markdown, Python, Ruby, SASS, shell (bash, csh), SQL, TeX/LaTeX, UML, XML, XSD, XSLT, YAML

Languages I used more than 10 years ago:

Ada, ASN.1, Assembler (Z80, S370), Basic (including VBA), C++, DCL, Delphi, Fortran, GDMO, lex, Modula, m4, Pascal, Perl, PL/M, PL/1, PostScript, Rexx, TCL/TK, yacc

Tools

In alphabetical order:

Ant, Apache, Clearcase, Docker, git, Graphviz (dot), Jekyll, Jira, Keynote, MindManager, MS Office, MySQL, OmniGraffle, OmniFocus, Oxygen, PostgreSQL, Rake, Rubymine, Saxon (XSLT), Scrivener, Subversion (svn), TeX/LaTeX, Vi, VirtualBox, Visio, VMware, Xcode, Xmind

Tools I used more than 10 years ago:

DialogBuilder, Eclipse, FrameMaker, ISPF, KMS-R, KMS-X, make, Netbeans, Oracle, Passenger, PTC Integrity, PTC Integrity Source, PVCS, Rhapsody, RCS, SCCS, Selenium, TWiki, XMLspy

Operating Systems

Linux, OS X (Apple), Unix System V, Windows (Microsoft)

Operating systems I used more than 10 years ago:

Apollo Domain, BS2000 (Siemens), NOS (CDC), CP/M, ISIS-II (Intel), MVS (IBM), Primos (Prime), Sinix (Siemens), Solaris (Sun), Unix System III, VM/CMS (IBM), VMS (DEC), VxWorks

Frameworks, Libraries

Blueprint (CSS), Bootstrap (CSS), log4j, log4r, PTC Integrity API, Ruby On Rails (RoR), Sinatra

Frameworks I used more than 10 years ago:

Diatools, GDMO, Motif, X-Window

Network, Communication

AFDX, CAN, CORBA, HTTP, LDAP, QD2 (SISA), Q.2931, Q.2971, Q3, RPC, TCH (proprietary), TCP/IP

Miscellaneous

Fagan Reviews, GTD, Mindmapping, UML

Patent DE000019640291C1

Personal Interests/Activities

Architecture, aviation (PPL-A, AZF rated, but not current), astronomy, design, photography, typography.

Last Projects

This list covers only the years since 2012. A complete list of my projects is available upon request.

2023/05 - 2024/01: Development of Testscripts

Challenge

The client develops software for an embedded control subsystem in cars.

Context

Software is developed according to AutomotiveSpice, functional safety is a key requirement.

Action

Review of requirements and test cases. Developing test cases in Python.

2022/10 - 2023/03: Test and Support of an Intranet Application

Challenge

The client has a large intranet application serving 200.000 users.

Context

Due to the large user base the availability of the application has a high priority.

Action

I was member of a team that is responsible for testing of new versions of the application. User support.

2015/06 - 2022/09: Development of a Document Publishing Tool

Challenge

The client has a large set of documents that have to be published on a webpage in the corporate intranet. The webpage must also be published as ZIP archive to an assessment organization for review.

The webpage must also contain overview and index pages.

Context

Due to the requirement of a static webpage neither a webserver nor a database is allowed. It is required that all deliveries can be stored in into a repository.

Action

I developed a publishing tool that generates a static website out of a set of templates and definiton files.

For several reasons the data definiton and the webpage templates are not written in YAML or XML. Instead I defined a domain specific data definition language that is more user friendly as XML and more robust than YAML or JSON.

Result

Currently (mid 2016) the generated site consists of about 1200 webpages and contains about 1000 document files. Several index lists are generated automatically. The generator also performs several consistency checks.

Main part of the development was finished in December 2015, improvements are still ongoing.

Tools

Ruby, Rubymine, HTML, CSS, Bootstrap (with Javascript), Subversion (SVN), git

2012/06 - 2022/09: Support for Documentation

Challenge

The client has several document types (e.g. requirement specifications, user manuals). Some of the documents are for the development team only, others are published inside the company. A subset of all documents is used for an assessment process with TÜV Süd.

Context

The client has development teams in several countries (including India, Italy and Hungary).

Action

My tasks are:

  • analyze software updates and update documents accordingly
  • document updates
  • document management (reviews, config und version management)
  • improvement of documentation processes
  • publish documents inside the organization
  • construct meta documents for navigation in document sets

Result

Documents are updated, reviewed and published permanently. New publishing processes are established.

Tools

MS Office, XMLSpy, Subversion (SVN), PVCS

2012/01 - 2022/09: Improvement of Documentation Tools

Challenge

The customer writes documentation in XML files. These XML files are compiled into HTML and PDF documents.

The existing toolchain as well as XML schemas had to be improved:

  • layout and the structure of the documents must be adjusted
  • toolchain must be improved to add information generated by doxygen
  • tools had to be developed for document deployment

Context

The client uses a toolchain which consists of tools like saxon (XSLT processor), XEP (processor for XSL-FO) and Doxygen. All tools had to run on Windows 7.

Action

My tasks are:

  • improvement of the toolchain.
  • improvement of the document schemas (XSD)
  • development of new scripts for deployment
  • user support

Result

The toolchain has new deployment scripts. The document layout was improved according to new requirements. Doxygen is now used to extract information from C source code and this information is transformed into XML according to the customers document structure.

Tools

Ruby, Saxon, XEP, YAML, XML (including XSD and XSLT), XmlSpy, Subversion (SVN), PVCS