Dagens samhälle är beroende av ett ständigt flöde av information och data. Företag och organisationer har ofta enorma mängder data som rör allt från kunder och personal till försäljningsstatistik och patientjournaler. Utvecklingen har gått mycket snabbt och många företag och organisationer har inte haft tid eller resurser för att hålla sina system uppdaterade för att hantera dessa enorma mängder data. I detta arbete har uppgiften varit att koppla samman databaser från flera olika system i syfte att göra underhåll och hantering av dessa enklare. Dessa system behandlar i regel samma typ av data (personaldata indelat i grupper i form av enheter) men den benämns på olika sätt, exempelvis med olika ID. Detta leder till att datan saknar relation på så vis att det är mycket svårt att avgöra vilka enheter som korresponderar med varandra då de saknar gemensamma nämnare. Som en lösning på detta skapades ytterligare två databaser sammankopplade med övriga genom ett API, där data kopplas samman genom att tilldelas ett gemensamt ID, ett master-id. På så vis kan användare och utvecklare enkelt söka efter ett objekt från ett system och få tillbaka all data för korresponderande objekt i andra system. Som tillägg skapades också ett semi-automatiserat system i form av ett användargränssnitt som används för sammankoppling av objekt. / Today’s society depends on a constant flow of information and data. Companies and organisations often hold huge amounts of data, ranging from customers and staff to sales statistics and patient records. The pace of change has been very fast and many companies and organisations have not had the time or resources to keep their systems up to date to handle these huge amounts of data. In this thesis, the task has been to link databases from multiple systems to make maintenance and management easier. These systems generally process the same type of data (personnel data divided into groups in the form of units) which are named in different ways, for example with different IDs. As a result, the data is unrelated in a way that makes it very difficult to determine which entities correspond to each other as they have no common denominator. As a solution to this, two additional databases were created and linked to each other through an API, where the data is linked by being assigned a common ID, or a master-ID. In this way, users and developers can easily search for an object from one system and get in return all the data for the corresponding objects in other systems. In addition, a semi-automated system was created in the form of a user interface used for linking objects.

For my thesis work I have done an evaluation of the newly released Microsoft developed web framework Blazor. My methodology is based upon a couple of previous articles about evaluating web frameworks. From these articles I have gathered a number of criteria used in my evaluation: documentation, lines of code,community size, framework usage, framework maturity, framework freshness, browser support and framework cost. Additionally, since Blazor is based on C# instead of JavaScript, I have included a 9th criterion, comparing JavaScript with C#. Many of the criteria need some kind of counterpart for Blazor to be compared with, for this purpose I have mainly used the established web framework Angular, and in some cases Ember.js. When evaluating, I have not expected Blazor to exceed Angular. Rather I have counted all cases where Blazor can at least be considered comparable to Angular (or Ember.js) as favourable.I found that overall Blazor did very well in the comparison as 6 out of the 8 criteria I took from the articles evaluated favourably for Blazor. The two criteria where I found Blazor lacking were framework usage and framework maturity. While there are large numbers of showcases and example sites I did not find any large production websites developed with Blazor, and for obvious reasons the framework that was officially released earlier this year has yet to reach a mature state. Furthermore I found the extra criteria, JavaScript vs C#, was favourable to Blazor.Thus, my conclusion is that Blazor is certainly worth picking up for new projects. I argue that even though the framework is not yet fully mature it has come far in its short lifespan, and that even though Blazor is not widely used yet it is unlikely to go away considering that it is developed and supported by a large company like Microsoft.

Choosing which framework to work with is a long-term commitment and should not be taken easily. New web frameworks are developed almost every day, and for IT consulting companies, delivering high quality applications within time and budget is the key to success. This study examines the different factors IT consulting companies should consider before adopting a new web framework. This by proposing an adoption model for web frameworks including what technical and non-technical factors practitioners values the most. The aim of this study was to advice and help improve how an IT consulting company in a structured and reliable way can determine their choice of web framework, to gain the best cost efficiency and deliver high quality web applications. This was done by interviewing IT consultants along with implementation of prototypes and reading literature. The results showed that it is mainly the non-technical factors that practitioners consider to be most important, for instance the customer and company value. Other important factors are the popularity of the framework, its community, maturity but also team factors such as previous knowledge and that it should be motivating. Even if the technical factors are not what the interviewees primarily mentioned, it is still essential to choose a framework that meets the project requirements in terms of performance and in security. Other important technical factors are also its architecture and maintainability. Based on the results, this study presents an adoption model that allow practitioners to choose web frameworks that best meet their requirements and greatest number of advantages for a given project.

Blazor WebAssembly is a new framework that was released in May 2020 that makes it possible to build client-side web applications using C# instead of using JavaScript for its frontend. The most popular web frameworks today are JavaScript based frameworks. This study aims to find out if Blazor is a viable option to use for developing web applications and if it is a well-established framework compared to JavaScript frameworks. To evaluate Blazor, a comparison is performed between Blazor and React on six criteria. The criteria are lines of code, cyclomatic complexity, state management, debugging tools, community, and libraries. To answer the criteria two applications was developed, one in the React framework and one in the Blazor framework. Besides the two applications, literature was gathered to answer the criteria. The results from the comparison showed Blazor was a Viable option to use for the development of web applications and that it has become established as a framework when taken its age in to consideration.

This master's thesis deals with analysis, design and implementation of a web-based information system for support in searching in Parish Books. The given information system automatically generates notes according to imported GEDCOM file. These notes are stored in database and can be edited or removed. At the same time, the possible way to display geographic data of specific Parish Books on the map was analysed and designed, and will~be later implemented in cooperation with existing information system Geowiki .

Introduction: Blazor is a new framework and current research show that there is a lack of performance comparisons. Therefore, a need to compare and evaluate this new Blazor framework is ought to be requested to show if it can compete with one of the best and most used frameworks, Angular. It is also one of the few web developing frameworks that has moved away from using JavaScript and therefore a comparison with a framework that uses JavaScript will be very interesting. Aim: The aim of this study is to make a performance comparison between two web applications using the Angular and Blazor frameworks. I will evaluate the performance and present the results to see if Blazor can compete with Angular as a modern web development framework. More specifically, the study aims to answer the following research question: Based on a performance evaluation would it be favorable for a developer or company to consider usingthe Blazor framework over the Angular framework when developing web applications? Method: I started by doing a literature review of the field I wanted to research. I used du.se library search engine, which had access to the DiVa portal, Google scholar, Summon and Libris etc. The literature was found using the keywords “Blazor”, “Angular”, “Web application”, “Framework”, “Comparison” and “Evaluation”. Thereafter, two web applications were developed for the purpose of performance evaluation of the two frameworks. An evaluation tool was used to create the report based on the measurement criterions: “First Contentful Paint”, “Time to Interactive”, “Speed Index”, “Total Blocking Time”, “Largest Contentful Paint” and “Cumulative Layout Shift”. When evaluating I summed up which framework that was more favorable in each category and displayed it in tables and graphs. Results: I found that the Angular framework was more favourable in 4 out of the 6 criterions. Even though Angular performed better overall it showed some very unstable performance results during the twenty tests. Blazor displayed a stable performance throughout all twenty tests in all categories and was very fast and responsive once the initial load of the client was done. Conclusions: Based on the results Angular was the more favourable framework during my tests, due to overall performance. But the Angular framework showed too many inconsistencies during the tests to call it superior, meanwhile Blazor performed very stable results. This indicates that the Blazor framework can possibly compete with the Angular framework as a modern web development framework. Thus, my conclusion is that it would be favourable for developers and companies to consider using the Blazor framework for new projects, especially if they have previous experience with the C# language or are new to web developement.

This report aims to address the design of a web server with Blazor Server for the company FunRock and their mobile strategy game MMA Manager. The web server is intended to administer settings of the game's different components, where staff can, for example, search for a user or a user's belongings. The report is limited to the design of specific pages from the most frequently used ones on the web server. Furthermore, the report wishes to address usability and accessibility analysis of the previous web server due to the basis for the design of the new Blazor Server application. The purpose of converting to Blazor Server has been to contribute to more flexible hosting, faster development and better performance than their previous one, written in ASP.NET 4.8. Finally, the later part of the report addresses a more subjective analysis of the author around the work performed where reflections on the project's results are treated. / Denna rapport önskar behandla utformningen av en webbserver med Blazor Server åt företaget FunRock och deras mobila strategispel MMA Manager. Webbservern ämnar till att administrera inställningar av spelets beståndsdelar, där personal kan exempelvis söka efter en användare eller en användares tillhörigheter. Rapporten erhåller avgränsning till utformning av specifika sidor från den tidigare webbservern som används mest frekvent. Vidare önskar rapporten behandla användbarhets- och tillgänglighetsanalys av den tidigare webbservern med anledning att agera grund till den nya Blazor Server applikationens design. Syftet med utformningen av den nya webbservern har varit att bidra till mer flexibel hostning, snabbare utveckling och bättre prestanda än deras tidigare som var skriven i ASP.NET 4.8. Slutligen tar rapportens senare del upp en mer subjektiv analys av författaren kring det utförda arbetet där reflektioner över projektets resultat behandlas.

The goal of this thesis is to design and implement coding conventions management system for project. Prior to the creation of the system itself, the research of coding conventions benefits, the analysis of used technologies in open source projects at GitHub service, and the analysis of existing technologies managing coding conventions was done. On the basis of that, usage scenarios were designed, requirements were specified and system architecture was determined. Then the system was implemented as web application based on Blazor and EditorConfig technologies. The main aim was to create a system that would allow to store all types of programming conventions and at the same time allows users to automatically control and generate them. It is published under an open source license within the GitHub service and deployed on the Azure cloud platform.

This study is conducted to evaluate the Blazor WebAssembly framework for the Progressive Web Application (PWA) methodology. A comparative study is conducted with a ReactJS PWA as a baseline. The two frameworks are evaluated in their front-end performance and documentation of PWA-focused subjects. Front-end performance is measured between two experimental applications that test the loading times, heap memory usage and loading consistency during layout generation. It is found that a Blazor WebAssembly PWA takes on average a range of 0.34, 0.18, and 0.06 seconds less time to generate a layout than a ReactJS PWA. The Blazor WebAssembly PWA was less consistent in its loading times when handling many elements. Documentation that covers Progressive Web Application terminology was found to be different between the frameworks. The Blazor WebAssembly documentation covers more topics and provides first-hand knowledge while the ReactJS documentation covers fewer topics and relies on external sources to provide the necessary explanations. These findings indicate that Blazor WebAssembly is a faster framework when updating large amounts of elements in comparison to ReactJS. However, the ReactJS PWA was found to be overall more consistent in its loading times. Documentation varied between the two frameworks. Documentation in Blazor WebAssembly covers more Progressive Web Application subjects and is more in-depth than ReactJS.  This study only evaluates applications developed in ReactJS and Blazor WebAssembly. Both are tested on Google Chrome in a desktop environment.

This thesis aims to clarify the use of Excel for capacity planning, how an excel-based capacityplanning tool works, and to present a way to implement a web system suitable for ad-hoc capacity and release planning. Capacity design is a critical part of flexible software development teams. Excel spreadsheets are flexible but not ideal for large organizations where many users have access to and can change planning concurrently. The existing tool received low ratings in terms of helpfulness, robustness to the inappropriate user, universality, flexibility, and aesthetics but performed quite well in clarity, consistency, memorability, overall efficiency, and third-party safety. The tool had some additional benefits, including calculating team capacity, preventing overplanning of individual development teams, and the ability to register the outcome of past planning periods. We implemented a web system based on Blazor Web to support the tasks provided by the existing tool, including capacity planning and release planning. The web system also supported role-based authorization. This web system was evaluated in a usability survey and maintained most of the provided functionality of the existing tool while avoiding some of the tool’s usability-related problems.