Continues Integration has been a vital part of software development process in order to make the development process fast and reliable. There are number of actors which play an important role with support of third party tools that helps the development process to be effective and productive in nature. The CI- toolchain is capable of doing much more than the compilation of the software project which covers the daily life tasks of the developers like testing, documentation etc. The important part of automated toolchain is the conversion of source code artifacts into executables with the help of the build system. The selection of proper build system is a matter of subjective in nature and it depends upon the number of factors that should be analyzed before proceeding forward towards the selection mechanism. This thesis focuses on software rebuilding and proves practically with experiments that could help developers and managers to decide between two important software build systems SCons and CMake. It has been experimentally proved that what are the conditions and situations where SCons performs better and what are the moments where it is wise to select CMake as a build tool. At first, individual build tools are evaluated in terms of scalability, conveniency, consistency, correctness, performance (in terms of speed and targets) and later, the build systems are experimented by automating the workflow by increasing the source code artifacts to evaluate the performance when there is limited user interaction. The behavior of the build systems are also tried with other third party tools like Tessy for testing purposes, Jenkins as CI server, and Polarion as requirement engineering tool to show how much effort is required to integrate third party tools with the build system in order to increase the functionality. The evaluation of the build systems is important because that will highlights the areas where potential candidates are better and where there is lack of functional specifications. Generally speaking, SCons has an advantage of being Pythonic in nature and provides the developer ease of use to specify the build configurations using programmatic skills. CMake on other hand are on top of shelves where there is no need to understanding and caring about the underlying platform and where developers want to generate the native build tool solutions which are readily available for exporting them into IDEs. Though both of the build systems has different goals, for example SCons is ready to sacrifices the performance while providing user correctness of the build while CMake focuses on generating native build tools by understanding the underlying platform. All of these types of situations are discussed with experiments in this thesis and serves as the practical guides for high level managers to decide the build tools among others. After evaluation, this thesis firstly suggests the general techniques where the bottlenecks could be covered and then build tool specific optimizations and recommendations are discussed to speed-up the development process.

Continues Integration has been a vital part of software development process in order to make the development process fast and reliable. There are number of actors which play an important role with support of third party tools that helps the development process to be effective and productive in nature. The CI- toolchain is capable of doing much more than the compilation of the software project which covers the daily life tasks of the developers like testing, documentation etc. The important part of automated toolchain is the conversion of source code artifacts into executables with the help of the build system. The selection of proper build system is a matter of subjective in nature and it depends upon the number of factors that should be analyzed before proceeding forward towards the selection mechanism. This thesis focuses on software rebuilding and proves practically with experiments that could help developers and managers to decide between two important software build systems SCons and CMake. It has been experimentally proved that what are the conditions and situations where SCons performs better and what are the moments where it is wise to select CMake as a build tool. At first, individual build tools are evaluated in terms of scalability, conveniency, consistency, correctness, performance (in terms of speed and targets) and later, the build systems are experimented by automating the workflow by increasing the source code artifacts to evaluate the performance when there is limited user interaction. The behavior of the build systems are also tried with other third party tools like Tessy for testing purposes, Jenkins as CI server, and Polarion as requirement engineering tool to show how much effort is required to integrate third party tools with the build system in order to increase the functionality. The evaluation of the build systems is important because that will highlights the areas where potential candidates are better and where there is lack of functional specifications. Generally speaking, SCons has an advantage of being Pythonic in nature and provides the developer ease of use to specify the build configurations using programmatic skills. CMake on other hand are on top of shelves where there is no need to understanding and caring about the underlying platform and where developers want to generate the native build tool solutions which are readily available for exporting them into IDEs. Though both of the build systems has different goals, for example SCons is ready to sacrifices the performance while providing user correctness of the build while CMake focuses on generating native build tools by understanding the underlying platform. All of these types of situations are discussed with experiments in this thesis and serves as the practical guides for high level managers to decide the build tools among others. After evaluation, this thesis firstly suggests the general techniques where the bottlenecks could be covered and then build tool specific optimizations and recommendations are discussed to speed-up the development process.

This diploma thesis deals with the creation of a general communication interface between the smart product and process cells within test bed Barman. The aim is to create distributed production according to the Industry 4.0 concept, where each product manages it’s production itself. The first part deals with the analysis of test bed, where are discussed requirements and method of production. Then with the selection of a communication protocol that would meet Industry 4.0 and distributed control requirements. The result of the research was OPC UA communication protocol. Using this protocol, the product and the process cell will communicate with each other. I chose the appropriate implementation for the selected protocol to be used for creating communication modules of the product and the process cell. Production data will be stored in an RFID chip located in the product. Part of the work is devoted to creation this data structure, which contains the recipe as well as production state data. Creation of RFID reader is the work of another student, with whom I solved the method of data exchange between application of the reader and the communication module of the product. When creating a communication module of the process cell, I solved the design of an information model that describes the entire process cell, and the dynamic creation of nodes in the address space. I have mentioned a few examples of how I worked with a selected implementation of OPC UA and how I used it in both applications. I implemented decentralized search of another process cells in the local network. This feature was easy to implement with OPC UA, specifically with the LDS-ME service. I solved the control of production for the communication module of the product and method of communication with the process cell. And in the last part I deal with manual, which describes how to compile projects correctly, specifically on the Linux operating system, and I have described a way to test the whole solution together with the results.

Image segmentation is a process to identify regions of interest from digital images. Image segmentation plays an important role in medical image processing which enables a variety of clinical applications. It is also a tool to facilitate the detection of abnormalities such as cancerous lesions in the brain. Although numerous efforts in recent years have advanced this technique, no single approach solves the problem of segmentation for the large variety of image modalities existing today. Consequently, brain MRI segmentation remains a challenging task. The purpose of this thesis is to demonstrate brain MRI segmentation for delineation of tumors, ventricles and other anatomical structures using Insight Segmentation and Registration Toolkit (ITK) routines as the foundation. ITK is an open-source software system to support the Visible Human Project. Visible Human Project is the creation of complete, anatomically detailed, three-dimensional representations of the normal male and female human bodies. Currently under active development, ITK employs leading-edge segmentation and registration algorithms in two, three, and more dimensions. A goal of this thesis is to implement those algorithms to facilitate brain segmentation for a brain cancer research scientist.

This thesis is focused on application development with ARM processor architecture and Linux operating system. It uses cloud hosting services to build, test and deploy applications with container-based virtualization. The application communicates with smart meters on serial buses. It stores measurements in a database. It provides access to devices and measurements in internet network.

The thesis deals with OpenCV library and its implementation into scripting language Lua. The first part of the thesis concentrates on description of the course Computer vision MPOV and description of mathematical basics needed for further understandings. The second part describes OpenCV library and its potential usage in the MPOV. Next chapter examines the programming scripting language Lua. The description of the implementation of binding the OpenCV library to Lua language along with its overall functionality is included in the practical part of the thesis. The use of LuaCV is more comfortable thanks to Open Source projects for cross-platform compilation and distribution. Part of the thesis is also generator of Latex documentation for LuaCV binding. The last chapter deals with testing LuaCV in course MPOV and analysis of criticism from students.