Cloud computing is still in an early stage of development and Microsoft is now investing considerable amount of resources in the cloud. Microsoft Azure is a cloud platform developed by Microsoft and it is continuously evolving, new features are constantly being added and old features are being updated. Integration Software, which is a company that focuses on products for system integration strongly believes that cloud­-based solutions will have a significant impact on their future. This is why selling and developing solutions and services for the cloud are strategically important for them. The objective of this dissertation is to investigate Microsoft Azure in general and Azure Marketplace in particular. This investigation consisted of an implementation of a Microsoft Azure application and integrating this application with Azure Marketplace and evaluating the expenses for running the application. The purpose for this project is to gain practical experience and to work with new techniques and help Integration Software better understand Azure Marketplace. The application is a Log Agent which fetches data from an external source and resends the data to an external party (Integration Manager). Our first intention was to package and deploy the application to a newly updated Azure Marketplace. The new Azure Marketplace was never released during this dissertation so we decided to deploy the application to the existing version of Azure Marketplace. This was however not fully successful. We encountered some problems in successfully deploying the application to Azure Marketplace. The evaluations for the cost of running an Azure application were not carried out due to lack of time.

Presenta las herramientas de Microsoft Azure aplicadas a entornos como prevención de riesgos y fraudes, reconocimiento facial y de lenguaje, análisis de mercados financieros o de cadenas genéticas, etc.

No description available.

This master’s thesis deals with design of the monitoring solution for the Power BI service. The thesis is divided into theoretical, analytical and design sections. In the theoretical part describes the theoretical fundamentals, used technologies and analytical tools. The analytical part analyzes the company Intelligent Technologies, competitive solutions and data sources for the design part. The design part proposes its own solution for monitoring the Power BI service, including the costs and benefits of the proposed solution.

In a world where software systems are essential for our everyday life, a vast amount of software errors have led to severe consequences, almost causing a nuclear war. Ensuring the quality of software systems has increasingly come into demand due to the rising complexity of technologies used in today´s solutions such as cloud computing, internet of things (IoT). Companies strive to ensure the quality of their softwares and have different approaches to do so. Some companies follow an industry standard such as ISO 9000, others develop their own standards and implement a software to ensure conformance. Quality Assurance (QA) has traditionally been implemented in the later stages of the development process. Research suggests however that early or constant implementation of QA is more likely to provide better end results. Current studies explore the stages of implementation for QA, the effects of QA and approaches for QA. Few studies however investigate how QA is approached within private companies. This study investigates the implementation of QA within private companies, the use of QA and which stage of the development process QA should be implemented. The investigation was done through suggesting a suitable approach to achieve QA for the case company Sogeti. The challenge that Sogeti faced was to ensure the quality of their PaaS components configurations. To further understand the problem, a QA plan was developed with the use of Robert P. Elliots ten steps of developing a QA specification. The QA plan indicated that a software would be a suitable approach due to the specific demands that Sogeti provided, the software would then implemented in the later stages of the QA development process before the components reach the end customer. The final prototype of the software helped discovering the amount of improper configurations that exists (38,46% components with improper configurations). Early QA might have been a better approach, assuming that the problems were discovered early. When the problems are dicovered late, the stage of QA implementation might not matter as the approach for QA is reactive. In order to draw that conclusion however, further research is needed where multiple companies are analyzed to visualize the qualitative and quantitative effects of QA.

Portability of the Internet of Things Solutions is important in today’s society. This is due to the rapid growth of smart devices. More and more companies are choosing to use cloud services for data storage and processing. Halmstad Stadsnät AB is developing and communicating the IoT-platform and using the current state of Nokia IMPACT. The problem with IMPACT is that it does not fully support End-toend solutions. Therefore, Halmstad Stadsnät AB explores other possibilities for IoT-solutions when it comes to software. Microsoft AZURE is a platform that Halmstad Kommun uses for IT-solutions. The overall goal of this project is to test the portability of Microsoft AZURE’s IoT-solutions on IMPACTplatforms. The methods used have created an End-to-end solution for AZURE and then step by step test to transfer it to IMPACT. The project concludes that portability between these two platforms is good, but it requires certain adjustments when transferring / Portabilitet av internet of things lösningar är i dagens samhälle nödvändig. Detta pågrund av den snabba tillväxten av bärbara datorenheter. Allt fler företag väljer att använda molntjänster för lagring och bearbetning av data. Halmstad Kommun håller på att utveckla en kommuntäckande IoT-plattform och använder sig i dagsläget av Nokia IMPACT. Problemet med IMPACT är att den inte har fullt stöd för End-to-end lösningar. Därför undersöker Stadsnätet andra möjligheter för IoT-lösning när det kommer till mjukvara. Microsoft AZURE är en plattform som Halmstad kommun använder för IT lösningar. De övergripande målet med det här projektet är att testa portabiliteten för Microsoft AZUREs IoTlösnignar på IMPACT-plattformen. De metoder som använts har varit att skapa en End-to-end lösning för AZURE och sedan steg för steg testa att överföra den till IMPACT. Slutsatsen av projektet är att portabilitet mellan dessa två plattformar är god, men dock krävs vissa åtgärder vid överföring.

Att använda sig utav automatiserade processer blir allt viktigare då företag alltid strävar efter att vara så effektiva som möjligt och för att kunna mäta sig med varandra. I den här rapporten har Microsoft verktyg Azure DevOps studerats och hur ett konsultföretag i Linköping kan dra nytta av automatiserade processer på bästa möjliga sätt. Målet var att ge företaget en bredare synvinkel på hur verktyget kan användas i framtida projekt för att maximera chanserna till en mer lönsam utvecklingsprocess än de har i dagsläget. För att mäta resultatet och framgångsfaktorn har olika kriterier kopplat till mjukvaruutveckling analyserats och jämförts med utvecklingsmetoder som kräver mer manuella handlingar. Resultatet visar på hur företaget praktiskt bör använda Azure DevOps och dess pipeline för att underlätta utvecklingen och lanseringen till olika miljöer.

Cloud technologies are spearheading today’s innovation and automation efforts. With the use of Azure Policy it is possible to govern Azure resources and services through customized Azure policy definitions. This project aims to simplify the creation process for the Azure policy definition by creating a web application that removes the need to construct the JSON structure. Instead of code-based, it uses click&add to create the code blocks. The web application was created through the library React and with the use of Typescript as the main programming language. The result is a web application that removes the need to construct the JSON structure and instead produces this JSON structure for the user. The project concludes that the result web application did not fully achieve simplification through click&add. However, it creates a good basis for further development of policy simplification. In its current form, the app can be viewed as an alternative method for creating an Azure policy definition. / Molnteknologierna står i spetsen för dagens innovations- och automatiseringsinsatser. Med användning av Azure Policy är det möjligt att styra Azure-resurser och tjänster genom anpassade Azure-policy definitioner. Detta projekt syftar till att förenkla skapandeprocessen fär Azure-policy definitionen genom att skapa en webbapplikation som tar bort behovet av att konstruera JSON struktur. Istället för att strukturera JSON via kod använder den click&add för att skapa kodblocken. Webapplikationen skapades genom biblioteket React med programmeringsspråket TypeScript. Resultatet är en webbapplikation som tar bort behovet av att konstruera JSON strukturen och istället producerar den här JSON-strukturen för användaren. Projektet drar slutsatsen att resultatapplikationen inte helt nådde förenkling genom användning av klicka&lägg till. Det skapar dock en bra grund för vidareutveckling av förenkling för Azure-princip definition. I sin nuvarande form kan appen ses som en alternativ metod för att skapa en Azure-princip definition.

System integration is the given solution to connecting and making different softwares and applications of today to collaborate without the need to create completely new programs or systems.       In this thesis, a component created for system integration with the purpose of being run on-premise will be the base on how a cloud based solution could be constructed and what benefits this would present, both in matters of scalability, elasticity and distribution as well as expenses. The cloud platform provider will be Microsoft Azure with the resources that are provided within and the presented solutions will primarily follow the cloud service model PaaS, presenting the benefits this provides for development within system integration.

Introduction. Particle Swarm Optimization (PSO) is a heavy-duty algorithm that is used to identify the optimum (maximum or minimum) solution of a formula with multiple unknown factors. PSO algorithms are used widely for various optimization problems, and all face the same challenge. Being iterative algorithms that in each iteration perform a mathematical formula, PSO algorithms demand a high capacity of physical resources and are often time consuming. This combination is even more challenging when executing a PSO algorithm on the cloud since expensive resources used over a long time come at a high cost and cheaper resources struggle to perform the task. To avoid high costs and achieve the best possible performance, one needs to choose the correct computational resources and configure them accordingly. Objectives. The goal of this study is to identify the optimum tools and configurations to execute a PSO algorithm on Microsoft’s cloud platform, Azure. To achieve that, we choose the Azure resources that are designed to perform deterministic tasks and to be distributed and scaled automatically by Azure. Those are Azure Functions and Azure Durable Functions. We experiment with various configurations, and we collect and compare the results to draw conclusions about which combination performs best. Methods. To identify which combination of Azure resources and configuration performs best in the cloud (Microsoft Azure), we perform experiments and collect metrics which we then aggregate and compare with each other, as well as with the metrics collected by executing the same combination on-premises. During those experiments, we execute the same PSO algorithm using the same variables, the values of which were calculated before performing the experiments. Results. Upon performing the experiments, we collected the results of each experiment, which consist of the time it took to execute, the number of zeros (beyond the decimal point) found in the result, as well as the Global Priority percentage which lead to that result. The results indicate differences both between the on-premises and on-cloud execution and between the various configurations and Azure resources. Conclusion. We succeeded in finding a combination using Azure Durable Functions with the appropriate configuration, which vastly outperforms all others. Concluding, the outcome of this study is that heavy-duty algorithms, such as PSO, can indeed be executed on Azure, with significantly improved performance, when using the right configuration and exploiting the resources to their whole extent. Additionally, we learned that an appropriately configured Azure resource can even outperform an identical execution on-premises (using equal resources).