Inom denna rapport så kommer det gås igenom vilka tekniker och metoder som har används för att skapa en implementation en ny sorts webbaserat API. Det nya API't heter GraphQL och upfyller samma syfte som det mer traditionella REST API som används mycket utav företag och organisationer i dagsläget. Det som skiljer GraphQL mot REST är att GraphQL använder sig av "Query Language" för att kommunicera med API't genom att hämta eller skicka information. Implementationen har utförts inom .NET Framework hos företaget Quicksearch. Utvecklingen har skett inom företagets datasystem och API't kan hämta information från deras databas och skicka det vidare till användaren. Verktygen som har använts för att skapa applikationen är utvecklingsprogrammet Visual Studio tillsammans med programmeringsspråket C\#. Programmet Postman har använts till hjälp för utveckling och testning av API't. Relevanta metoder för att skapa API't inkluderar bibliotek riktat mot GraphQL och sammankoppling mot databasen. Designmönster har varit viktiga i projektet och dessa är "Dependency Injection" och "Model-View-Controller" för att skapa en web applikation. Slutresultatet är ett GraphQL API som kan forma enkla förfrågningar riktat mot en data-modell eller objekt. Även en jämförelse av GraphQL mot REST API har utförts med resultatet att det finns distinkta skillnader mellan de två konceptenför men för att komma fram till en övergripandeslutsats över vilket API som är ett bättre alternativ så behövs ytterligare tester. / This report will walkthrough several techniques and methods that have been used to create a new kind of web-based API. This new kind of API is called GraphQL and fullfils the same purpose as the more traditionally used REST API. What differs between these two types of API is that GraphQL uses a ”Query Language” when the user communicates with the API. The implementation is done in .NET Framework together with a company named Quicksearch. The development has been done within Quicksearch’s computer system and the API can request information from the company’s database and send it back to the user of the API. The tools that have been used to develop the API are Visual Studio as the development enviroment, along with the programming language C#. Postman is a software that have also been used to help develop and test the GraphQL API. Relevant methods used in the development includes libraries directed to create a GraphQL API and libraries used to create the connection to the database. Design patterns have also be important in the development and the most noticeable ones have been ”Dependency Injection” and ”Model-View-Controller” to create the application. The end result is an API that is able to recieve simple queries directed against a simple data-model or object. Aditionally a comparison between GraphQL and REST have been done and the result is that there are distinct differences between the two types of API but there is a lack of scientific reasarch and knowledge to make the conclusion of which is the better alternative and additional tests are required.

The aim of this work is to design and develop mobile iOS application for portal Mojilidi - platform iPhone. Design and control of this app must be similar to android application. During application's development was used tool called Sketch to create design for the application. Swift version 4.2 was used to program application. For communication was used URLSession library to communicate with server. Application also is using technoglogies such as MapKit for location entry, MessageKit for chat or CoreData for local storage.

This diploma thesis deals with the design, implementation and deployment of a hybrid application that is based on maps. This hybrid application was created on the basis of an already existing web application with the use of modern technologies. It should be used for easy traffic monitoring of selected parts of cycle routes. Part of this thesis is also development of REST API for retrieving data from database server.

Software documentation is one of the most important aspects of the software development process, as it allows the transfer of knowledge between individuals, regardless of their background and their technical knowledge. In particular, Application Programming Interfaces provide the basic structure for the communication and integration between different software systems. Therefore, providing solid API documentation is fundamental for the software development process as it represents one of the main learning tools for developers trying to learn new technologies. While researchers have studied the fundamentals of good API documentation design for over twenty years, most studies only focused on the point of view of developers. However, with the rising amount of companies offering Software-as-a-Service products, it has also become important to produce documentation that is accessible to people with limited technical knowledge, i.e. customer representatives.  In order to fill this research gap, a case study was conducted in collaboration with a software company. By using a design science approach, this project focused on creating an API playground environment where users could interact with various APIs offered by the company. The results were evaluated through a questionnaire for user feedback and with an interview conducted with developers from the company. While the outcome of the evaluation was positive, the limited scope of the project prevented some important aspects of API documentation such as navigation from being thoroughly examined, therefore more extensive research is needed in the future.

iSmart Taxi är en Android mobilapplikation (app) för taxiförarna på iSmart Taxi AB. Förarna kan med hjälp av denna applikation rapportera deras körningar. Denna applikation har skapats med hjälp av ett REST-API för att interagera med databasen.   Rapporten innehåller beskrivning om hur applikationen skapades och hur återkoppling från testfall som genomfördes av användarna påverkade applikationens design. / iSmart Taxi is a mobile application (app) for taxi drivers at iSmart TaxiAB. The application helps the drivers to register their fares on an Android mobile. A REST-API was build to interact with the database.   The report contains a description of how the application was created and how the feedback from the tests conducted by the users affected application design.

This diploma thesis deals with creating a container for the migration components that are used on the Android operating system, how they operate and distribute, the life cycle of the container, and the ability to customize other components for this container. The work deals with the analysis of the Android operating system, existing solutions, the design of the own container and the way of distributing the components on the devices where the container is used. The next section describes the implementation of the server component that distributes components. It also deals with the implementation of container-containing library and a sample application that illustrates how it is possible to link all these elements together.

In this thesis, a centralized hardware monitoring system for HP servers is developed at Ericsson in Linköping. The centralized system is then evaluated and compared to the current decentralized monitoring system. The results show that not only is the information displayed by the centralized system more detailed, but the configuration process for new servers is also simplified. Cost savings are also identified, since the same monitoring plugin and configuration script can be used for all server generations. Interviews with employees who work with monitoring on a daily basis also shows that they prefer the centralized monitoring system over the current decentralized system, however a high availability solution needs to be implemented for the central part of the monitoring system since it otherwise can become a single point of failure.

Leeroy Group AB är ett IT-produktbolag i Sundsvall som även sköter support för sina produkter. Detta görs i ett egenutvecklat ärendehanteringssystem som under tid utvecklats och skräddarsytts efter verksamhetens behov. Leeroy är nu ute efter ett kraftfullare ärendehanteringssystem som skall ge möjlighet att ta hand om fler ärenden ju mer företaget växer. Detta examensarbete har inkluderat en grundlig förstudie bland de anställda på Leeroy. En kartläggning av krav och behov som finns för Leeroys' supporthantering har gjorts och sammanställts till en kravspecifikation. Leeroy har valt att titta på två stycken utvalda ärendehanteringssystem: Jira Service Desk och Zendesk. Utifrån den kravspecifikation som framkommit görs en dokumentations-inhämtning baserat på dessa krav och behov, för att sedan kunna presentera ett lämpligt alternativ för Leeroy. För att sedan ytterligare göra detta byta till en smidigare process har ett REST API och enklare webbapplikation utvecklats för att kunna hämta in kund-data från den befintliga kund-databasen. Webb-applikationen kommer att fungera som en koncept-applikation där man med sökning mot butiksnamn eller butiksnummer får ut all relevant information som Leeroys' supportanställda behöver.

This work deals with communicating issues in public space from citizens to municipalities. The main objective is the creation of a system for reporting those issues using smartphone. The first chapter contains the analysis of existing foreign and domestic projects focused on issues mapping. The second chapter focuses on analysis and design of a new system. The third chapter discuses variants of technologies available for each part of the system. The fourth chapter describes choice of technologies and development of individual parts of the system.

In this work, a web application has been developed for the company Moverline with the server software Node.js and the database management program MySQL. Moverline's vision with this application is that it will be a long development project and therefore it is important that the usability is high. During this project, a qualitative empirical study was performed regarding the usability of the REST API. This qualitative information is gathered through interviews and discussions with Moverline employees. The API functions of the produced application were in most cases easy to understand and knowledge of the underlying implementation did not need to be possessed. Problems of the REST API were ambiguities about how the endpoint of the URL should look like and in most call functions the calls are answered with an HTML answer. This is not optimal from a usability perspective as it becomes more difficult to know if the operations went through and what kind of data has been sent. One development step to prevent this problem would be to implement a client part of the application that acts as an intermediary between the Node.js server and the HTML files.