The diploma thesis focuses on the usage of Business Intelligence for the analysis of the provided employee data. It describes the process of creating dashboards in the chosen Business Intelligence tools, compares them based on the defined criteria and chooses the most suitable tool. The diploma thesis also contains a description of an implementation process of the created solution and an economic evaluation including costs and benefits.

The aim of this diploma thesis is to summarize existing facts about Business Intelligence and to point out the benefits of using those applications in the company. This thesis therefore contains both theoretical and practical findings regarding Business Intelligence, used technologies and attitudes, and also areas for improvement with suggested solutions. Moreover, there is mapped a practical example with implementation of BI tools.

The aim of this paper is to propose a method for automatic segmentation of dashboards so that they can be analyzed using aesthetic by means of metrics. These metrics analyze the properties of the screen objects by region. This method is based on bottom-up segmentation method and creates objects based on proximity. The main result is a faster and more accurate analysis of dashboards, as there is no need to manually segment the image.

The master thesis deals with the issue of evaluation of efficiency and data collection of lines in production, using the APROL program from B\&R automation. The aim of this work is to create a program completed requirement, which is going to be compared with already implemented projects of the company and will serve to create a company standard. The first part is devoted to the description of the theory of this issue and used software. The second part describes the solution of the line simulator and the whole concept of collection and evaluation.

The thesis deals with the new design of Dashboard application developed for Vodafone Czech Republic company. The application serves for sales monitoring on all direct retail stores of the company. Major goal of this project is to design a brand new application and enhancing its functionality with new analytical tools and motivational indicators. These innovations will empower the performance of salesmen along with providing the new analytical possibilities for store managers.

The thesis deals with the analysis of the usual time and frequency of vehicle mirrors and dashboard observation. Within the theoretical part are summarized the current knowledge of the visual distraction of the driver, or circumstances which affect the conduct and behavior of the driver while driving. Furthermore there is a closer approximation and characterization of devices for recording the driver's eye movement, which is used during the measurement of the usual time of observation. This data is used in the experimental part of the thesis. The results were processed and statistically analyzed to determine the usual time of mirrors and dashboard observation. Conclusions done from the measurement results are contained in the last chapter, which also evaluates contribution of this work to practical use in the field of analysis of road accidents and to improve safety on our roads.

Tesis para optar al grado de Magíster en Tecnologías de la Información / La construcción de software es una actividad compleja, realizada por equipos de personas y que involucra diversas actividades, como planificación, gestión de incidentes, control de versiones, pruebas y codificación, entre otras. Un proceso de desarrollo permite a las organizaciones ordenar la construcción de software definiendo los artefactos y asignando los roles que realizan estas actividades, de forma de mejorar la calidad y la productividad en los proyectos de software. Las actividades de desarrollo y de monitoreo realizadas durante la ejecución de un proyecto, generalmente son apoyadas por diversas herramientas. Este trabajo de tesis se enmarca en las PyMEs de software chilenas, las cuales tienen realidades muy diferentes, pero la gran mayoría de ellas tiene necesidades de monitoreo y control de sus proyectos. A pesar de que la mayoría de las PyMEs posee información de sus actividades de desarrollo en las herramientas que utiliza, la captura de las métricas de sus proyectos la realizan generalmente de forma manual, lo cual es costoso en términos de tiempo y dinero. Una posible solución para este problema es la construcción de un software que integre, recopile y consolide la información de diversas herramientas, permitiendo visualizar mediante un dashboard o panel de control información relevante para la toma de decisiones, apoyando las actividades de monitoreo y control de proyectos. Sin embargo, al aplicar la solución a múltiples PyMEs se observa que existe una complejidad técnica debido a la variabilidad de herramientas utilizadas por las PyMEs. Esta variabilidad se manifiesta tanto en las herramientas, sus tipos y los usos que se les da. Debido a estas complejidades relacionadas con la interoperabilidad, integración y variabilidad, en este trabajo de tesis se propone una arquitectura para un sistema de dashboard, el cual tiene como objetivo proveer de un mecanismo para aprovechar la información disponible en las herramientas de desarrollo de las PyMEs para monitorear, controlar y apoyar la toma de decisiones durante la gestión de los proyectos. Finalmente, con el objetivo de validar la arquitectura propuesta, demostrar la factibilidad de su implementación y encontrar oportunidades de mejora, se realiza la validación mediante dos técnicas: la implementación de un prototipo y la evaluación de la arquitectura por expertos.

Der Schwerpunkt dieser Arbeit liegt auf der Konzeption sowie prototypischen Implementierung eines web-basierten Dashboards zur Softwarevisualisierung. Ziel der Arbeit ist es, ein Dashboard zu entwickeln, welches Informationen eines Softwareprojekts dynamisch aus einer Graphdatenbank visualisiert und Projekteitern aufgabenbezogen zur Entscheidungsunterstützung darstellt. Derzeit existiert keine Softwarelösung, die diesen Anforderungen vollumfänglich gerecht wird. Es existieren jedoch bereits Bibliotheken und Softwaresysteme, welche Teilaspekte zu einer möglichen Gesamtlösung beitragen können. Diese können bei der prototypischen Implementierung von Nutzen sein und müssen daher beachtet werden. Um die Ziele der Arbeit zu erreichen, werden verschiedene Forschungsmethoden angewandt. Es wird eine Literaturrecherche durchgeführt, mit dem Ziel, typische Aufgaben von Projektleitern im Bereich Software Engineering zu identifizieren. Um die vom Dashboard zu unterstützenden Aufgaben ableiten zu können, werden außerdem verschiedene existierende Dashboard-Werkzeuge analysiert. Mithilfe der gewonnenen Ergebnisse wird das Dashboard konzipiert und prototypisch implementiert. Durch eine Fallstudie anhand von Open-Source-Projekten wird das Dashboard abschließend evaluiert.:1 Einleitung 1.1 Motivation und Problemstellung 1.2 Zielstellung 1.3 Methodisches Vorgehen 2 Grundlagen 2.1 Softwarevisualisierung 2.2 jQAssistant 2.3 Neo4j 2.4 Webanwendungen und web-basierte Frameworks 2.5 D3.js 2.6 Dashboards 3 Konzeption 3.1 Mission Statement 3.2 Architekturziele 3.3 Kontextabgrenzung 3.3.1 Fachlicher Kontext 3.3.1.1 Literaturrecherche zu typischen Aufgaben von Projektleitern 3.3.1.2 Analyse existierender Dashboard-Werkzeuge 3.3.1.3 Use-Case-Diagramm der zu unterstützenden Aufgaben 3.3.1.4 Mockups der Benutzungsschnittstelle 3.3.2 Technischer Kontext 3.4 Randbedingungen 3.4.1 Technische Randbedingungen 3.4.2 Organisatorische Randbedingungen 3.5 Risiken und technische Schulden 3.6 Entwurfsentscheidungen 3.6.1 Auswahl des Neo4j-Treibers 3.6.2 Vergleich existierender Webframeworks 3.6.2.1 Angular 3.6.2.2 Backbone.js 3.6.2.3 Ember.js 3.6.2.4 Vue.js 3.6.2.5 React 3.7 Lösungsstrategie 4 Implementierung 4.1 Implementierungskomponenten 4.1.1 CoreUI 4.1.2 Nivo 4.2 Dashboard 4.2.1 Startseite 4.2.2 Einstellungen 4.2.3 Benutzerdefinierte Abfragen 4.2.4 Visualisierungskomponenten 4.2.4.1 Struktur 4.2.4.2 Dateitypen 4.2.4.3 Abhängigkeiten 4.2.4.4 Aktivitäten 4.2.4.5 Wissensverteilung 4.2.4.6 Hotspots 4.2.4.7 Statische Quellcodeanalyse 4.2.4.8 Testabdeckung 4.2.4.9 Erstellung 4.3 Eingesetzte Werkzeuge 4.3.1 Entwicklung und Test 4.3.1.1 Jest 4.3.1.2 Codecov 4.3.1.3 Travis CI 4.3.1.4 Prettier 4.3.1.5 Docker 4.3.2 Installation und Wartung 5 Evaluation 6 Fazit und Ausblick

The 4th phase of the industrial revolution is focused on the relationship between the humans and the machines and how they can collaborate. We are going to look deeper into the relationship between autonomy and IoT-based solutions in a line organization with the help of a case study. In this case study, we discovered that the industry and their workers will benefit from using IoT-solutions to maintain more competitiveness to the market. With the use of IoT- based solutions such as a digital Dashboard, they get more reliable information and better ways of communication within the organization. Our study emphasizes the necessity of improving the autonomy within an industrial workplace. The personnel in an organization will be able to use IoTin a way to get more creative, gain more responsibility, keep a higher level of quality and make the work procedures more efficient.

As datasets in general grow in size and complexity over time while the human cognitive ability to interpret said datasets essentially stays the same, it becomes important to enable intuitive visualization methods for analysis. Based on previous research in the field of information visualization and visual analytics, a dashboard visualization prototype handling real-time event based traffic was implemented and evaluated. The real-time data is collected by a script and sent to a self-implemented web server that opens up a websocket connection with the dashboard client where the data is then visualized. Said data consisted of transactions and related metadata of an ecommerce retail site applied to a real customer scenario. The dashboard was developed using an agile method, continuously involving the thesis supervisor in the design and functionality process. The final design also depended on the results of an interview with a representative from one of the two target groups. The two target groups consisted of 5 novice and 5 expert users to the field of information visualization and visual analytics. The intuitiveness of the dashboard visualization prototype was evaluated by conducting two user studies, one for each target group, where the test subjects were asked to interact with the dashboard visualization, answer some questions and lastly solving a predefined set of tasks. The time spent solving said tasks, the amount of serious misinterpretations and the number of wrong answers was recorded and evaluated. The results from the user study showed that the use of colors, icons, level on animation, the choice of visualization method and level of interaction were the most important aspects for carrying out an efficient analytical process according to the test subjects. The test subjects desired to zoom in on each component, to filter the contents of the dashboard and to get additional information about the components on-demand. The most important result produced from developing the dashboard was how to handle the scalability of the application. It is highly important that the websocket connection remain stable when scaling out to handle more concurrent HTTP requests. The research also conclude that the dashboard should handle visualization methods that are intuitive for all users, that the real-time data needs to be put into relation to historical data if one wishes to carry out a valid analytical process and that real-time data can be used to discover trends and patterns in an early-as-possible stage. Lastly, the research provides a set of guidelines for scalability, modularity, intuitiveness and relations between datasets.