From tiny to huge: scalable configuration management for embedded systems
George Mesesan (MicroDoc Computersystems GmbH )
In this talk I will show the path we took from an initial application that ran on a specific embedded platform to a software solution that allows the management of customer configurations and supports software packaging and deployment on a whole range of embedded platforms. This talk is a case study of the path we took from from configurable software to customized software. The following applications were developed by MicroDoc GmbH for SkiData AG. The initial application is called DEI (Device Enabling Interface) and it is an OSGi, embedded Java application that runs on an ARM, embedded-Linux platform. DEI is a hardware centric framework for running Skidata specific components called Modules, Protocols and Ports. A good example for a Module is a RFID reader, a Protocol can be CRC32, a Port implementation can be USB, and so on. DEI controlls the lifecycle, configuration and interaction of the various components and offers services like lookup and automatic discovery to the application. The next step is called MDM (Multi Device Management). MDM deals with devices in a N:1 relation instead of a 1:1 relation as it is the case in DEI. Due to the fact that 3rd party equipment often doesn\'t have enough resources to run DEI on-board, the DEI is run outside of the device on a hardware instance that is powerful enough to run all the necessary instances of DEI. The final step is called SCM (Software Configuration Management) and addresses the typical problems that arise in a multi-customer, multi-device environment: the management the lifecycle of software components, the management of customer configurations, the packaging and deploying of software compilations. A software compilation is a software distribution consisting of several customized software components, which can be deployed on a device.
I am a senior software engineer at MicroDoc GmbH in Munich and I was involved in the introduction of TDD within the MicroDoc development process. I have experience in tools development and automation techniques, in the embedded as well as the enterprise domains.