This thesis presents my work at the company Fatshark AB in Stockholm. My supervisor Rikard Blomberg, who works as a chief technology officer at Fatshark and is one of the owners of the company, explained that they had experienced weaknesses in the methodology used when developing heads up displays (HUD) for their games. In the latest production, Lead  and Gold, the HUD had been redesigned a number of times, becoming an unnecessarily big expense due to the number of work hours invested. In modern software development, an iterative workflow is commonly encouraged. Despite this fact, the work efficiency could likely be increased by setting up guidelines as a help in the process of developing HUDs and reviewing the solutions. There was also a need for a way to estimate a particular redesign’s impact on the game before the actual  implementation had been made, and ways to define the pros and cons of each redesign. My task was to come up with standards for how the different elements in a UI could be structured and reviewed, in order to improve the developing process of the UI and facilitate the communication between employees. These standards were to be designed by a team consisting of Fatshark employees from different work disciplines and myself. / Den här rapporten beskriver mitt exjobb på företaget Fatshark AB i Stockholm. Min handledare Rikard Blomberg, som är chefsprogrammerare och delägare i företaget, förklarade att det fanns brister i deras metodik för utveckling av HUD i deras produktioner. I den senaste titeln, Lead and Gold, hade HUD:en designats om väldigt många gånger, och därför, räknat i arbetstimmar, kostat orimliga summor pengar. Samtidigt som man i modern mjukvaruutveckling ofta främjar en iterativ arbetsmetodik, skulle processen kunna effektiviseras om det sattes upp ramar och planer för hur man ska gå tillväga för att utveckla och mäta kvaliteten på resultatet. Vidare var det önskvärt att i någon utsträckning kunna förutspå vad som kan bli bra innan det läggs in, och att kunna definiera på vilket eller vilka sätt någonting är ”bra”. Mitt uppdrag handlade om att tillsammans med några på företaget ta fram standarder för hur olika delar av spelets HUD (senare omformulerat till att inbegripa UI i allmänhet) ska struktureras och hur man ska kunna använda detta för att effektivisera utvecklingen för att nå snabbare och bättre resultat.

Wireless technology has been advancing a lot over the years and it has become mature enough to be used in industrial process control. Wireless sensor networks have overtaken the wired devices and are vastly adapted across the industry. Using wireless technologies in industrial process control results in easy installation and configuration of network and helps in reduction of overall cost. Applying wireless technologies has greater benefits but on the other hand it provides challenges due to harsh industrial environments. Nowadays, wireless sensor devices are smart enough to detect the problems within the network and are capable of producing health reports. To use the capabilities of these smart devices a centralized management is required.  A centralized network manager can manage these smart devices to improve the overall network. Network manager plays a pivotal role because it is a central part of the network and a bad network manager results in network performance degradation. This thesis work addresses the need of centralized network management and proposes a design for the network manager based on the WirelessHART standard. Several algorithms are developed based on the layered architecture of WirelessHART  and a user-friendly graphical user interface is designed for the network manager which is capable of displaying real-time performance and statistics of the network, adding and configuring the nodes, creating routes for the nodes, showing routing tables and neighbour tables and display the network topology. Any change in the network is reflected and displayed by the GUI at run time. The designed network manager is implemented and tested using both simulated packets and real hardware and the work is evaluated using Average Packet Delivery Ratio, Average End to End Delay and by comparing the work to already designed network managers.

The main goal of this master’s thesis is to over study, reconsider and make a program, which will be capable to interpose information from GPS module, different markers and necessary information’s, geographic coordinates obtained from GPS will be projected in its interface and also on map. This project contains of 3 parts. The first one exactly describes GPS, its history, structure, principle, competitive types of navigations systems and also GPS’ services and technical parameters. The second part of this project describes GPS hardware, used receiver of this signal. There is also mentioned its technical parameters and communication with outside world. The third part is in scripted the software for communication with GPS receiver. We can also see the description of code, in which is mentioned communication protocol and imaging the position on the map. It was programmed in C# language on platform Microsoft Visual Studio 2008 Express Edition.

The main goal of this master’s thesis is to over study, reconsider and make a program, which will be capable to interpose information from GPS module, different markers and necessary information’s, geographic coordinates obtained from GPS will be projected in its interface and also on map. This project contains of 3 parts. The first one exactly describes GPS, its history, structure, principle, competitive types of navigations systems and also GPS’ services and technical parameters. The second part of this project describes GPS hardware, used receiver of this signal. There is also mentioned its technical parameters and communication with outside world. The third part is in scripted the software for communication with GPS receiver. We can also see the description of code, in which is mentioned communication protocol and imaging the position on the map. It was programmed in C# language on platform Microsoft Visual Studio 2008 Express Edition.

Master of Science / Department of Mechanical and Nuclear Engineering / Daniel V. Swenson / This thesis provides a description of Visual EMU, a graphical user interface for the peridynamic EMU code. The peridynamic model is a fundamental method for computational mechanical analysis that makes no assumption of continuous or small deformation behavior and has no requirement for the concepts of stress and strain. The model does not require spatial derivatives and instead uses integral equations. A force density function, called the pairwise force function, is postulated to act between each pair of infinitesimally small particles if the particles are closer together than some finite distance. A spatial integration process is employed to determine the total force acting upon each particle and a time integration process is employed to track the positions of the particles due to the applied body forces and applied displacements. EMU is a computer code developed by Sandia National Laboratories that implements the peridynamic model. Visual EMU is a pre-processor for the EMU code that allows any user to enter all parameters and visualize the resulting material regions, peridynamic grid, and a preview of resulting nodes. Visual EMU can be used before starting a lengthy solution with potential errors. The language, visual layout, and code design of Visual EMU are described along with two examples and their results.

Testning är en nödvändig men kostsam del av mjukvaruutveckling. Test utförs på olika abstraktionsnivåer och kan vara manuella eller automatiserade. På lägsta abstraktionsnivå, enhetsnivå, är automatiserad testning vanligt och relativt okomplicerat, medan systemtester är svårare att automatisera. I synnerhet gäller detta tester på ett grafiskt användargränssnitt (GUI) som kräver speciella verktyg.   Triona vill undersöka möjligheterna att automatisera regressionstester från GUI:t av sin produkt C-Load, en molnbaserad webbtjänst för avtalsbaserad transportbokning.    Det primära syftet med denna fallstudie är att med en anpassad urvalsprocess utvärdera ett möjligt verktyg i förhållande till C-Load-förvaltningens förväntningar på automatiserad GUI testning (AGT) och att utifrån resultatet föreslå hur C-Loadförvaltningen kan gå vidare med val av verktyg för AGT. För att uppfylla syftet användes litteraturstudier, intervjuer och observationer av praktiska test.    Verktyg för GUI-testning kan delas in i tre huvudkategorier: skriptbaserade, modellbaserade och skriptlösa. Baserat på tidigare forskning drogs slutsatsen att ett skriptbaserat verktyg där koden i testskripten skrivs manuell bäst passar C-Loadförvaltningens krav och förutsättningar. Det mest använda verktyget av denna typ, Selenium WebDriver, utvärderades kvalitativt gentemot identifierade krav.    Av tidigare forskning framgår att vanliga utmaningar med skriptbaserade GUI-tester är att arbetsinsatsen för att skapa och underhålla testskript är stor och att testen kan vara opålitliga. Dessa problem framkom också i studiens intervjuer och observationer.   Slutsatsen är att det vore möjligt att automatisera regressionstester av C-Load med hjälp av Selenium Webdriver, och att det på sikt skulle kunna frigöra tid. Initialt krävs dock en omfattande insats för att implementera automatiserade tester i förvaltningen och Selenium Webdriver uppfyller bara delvis C-Load-förvaltningens förväntningar på AGT. C-Load-förvaltningen rekommenderas att utvärdera fler verktyg innan beslut fattas. I en kommande urvalsprocess bör Triona beakta hur väl olika verktyg fungerar i förhållande till moderna webbramverk. / Testing is a necessary but costly part of software development. Tests are performed at different abstraction levels and can be either manual or automated. On the lowest level of abstraction, where unit testing is performed, automated testing is commonplace and relatively uncomplicated, whereas system testing is more difficult to automate. This is especially true for GUI-testing, which requires special tools.      Triona wished to investigate possibilities to automate regression testing of the GUI for its C-load product, which is a Cloud-based web-service for contract-based transport booking.      The purpose of this case study was to evaluate one tool for automated GUI-testing (AGT) against the C-Load team’s expectations on AGT, and based on the result recommend Triona how to proceed in the process of implementing AGT. Literature studies, observations and interviews were conducted to fulfil the purpose.      GUI-testing tools can be classified into three categories: script-based, model-based and scriptless. One conclusion was that a script-based tool, where test scripts are manually coded would best suit Triona’s needs. The most used tool in that category, Selenium WebDriver, was tested and evaluated against requirements.       Prior research shows that common challenges encountered when using script-based GUItests are the workload required to create and maintain test scripts and that the tests can deliver inconsistent or “flaky” results. These challenges were confirmed during our analysis.       Our conclusion is that it is possible to automate C-Load regression tests with Selenium WebDriver, and that it would eventually free up time. However, a considerable effort is initially required to implement automated testing. Selenium Webdriver only partly fulfills the C-Load team’s expectations on AGT. Before a decision is taken, the C-Load team should evaluate more tools. When evaluating tools for AGT, Triona should take note that Selenium Webdriver can be deficient when it comes to testing applications based on modern web frameworks.

The main goal of this master’s thesis is to over study, reconsider and make a program, which will be capable to interpose information from GPS module, different markers and necessary information’s, geographic coordinates obtained from GPS will be projected in its interface and also on map. This project contains of 3 parts. The first one exactly describes GPS, its history, structure, principle, competitive types of navigations systems and also GPS’ services and technical parameters. The second part of this project describes GPS hardware, used receiver of this signal. There is also mentioned its technical parameters and communication with outside world. The third part is in scripted the software for communication with GPS receiver. We can also see the description of code, in which is mentioned communication protocol and imaging the position on the map. It was programmed in C# language on platform Microsoft Visual Studio 2008 Express Edition.

Mixing audio is not only an aural activity, but also, becoming increasingly more visual, and connections between the engineer’s action and interface are not yet fully understood. This study aimed to investigate how different amounts and types of data displayed in parametric equalizers impact mix decisions and workflow. A usability test with audio engineer students were conducted. The test consisted of three different interfaces with variable information displayed and subjects were to perform six common equalization tasks. Two categories of stimuli were used, surgical and aesthetic. The parameters that were measured was effectiveness, efficiency, workflow, and preference. A post session questionnaire was also conducted. Each interface and category were compared and a t-test for each comparison were conducted. Task completion and time for task completion were determined and calculated. Eight t-tests were also conducted between interfaces. Parameters adjusted, order of adjustment, and most used parameter were determined. Preference ratings were categorized and analyzed. The results show that the EQ with graphic display performed better for the surgical category. Significant differences were also found for the surgical category between interfaces with most dissimilarities. The workflow tended to alternate between interface designs. The preference rating showed a clear preference for the interface with graphic display.

This project aimed to create a simple open-source embedded graphical user interface library that could be used on more or less any microcontroller platform. The programming language was intended to be C++ for the GUI but as the project evolved C was chosen above C++. This was a decision based primarily on the fact that STM's development environment, STMCubeIDE, is less compatible with C++. The IDE offers great hardware support which in the end was more important than the advantages given by C++. The hardware used in this project was an STM32F469 microcontroller. It has an ARM CortexM4 processor core and 2 Mbyte of flash memory and 384 Kbytes of RAM. Wrapper functions for the Board Support Package, BSP, were written as a part of the library to allow easy access tothe BSP needed for the hardware configuration. The first part of the project goal was achieved, a simple GUI library was created. The resulting GUI library supports user interaction through buttons, it can display the current time andvisualizes given data in graphs. The graph function can display the data live, as a scatter plot, a bar plot and a line plot. The library also supports an alarm function that allows the user to decide what will happen after the alarm time is up. However, even though the GUI library was written to be device-independent, the product has not been tested on other platforms. For further development, this GUI library could be tested on another microcontroller. This would provide answers to how much software changes are needed to make the product as hardwareindependent as possible. To make the library lighter and faster, there is a possibility of optimizing the GUI core.

I dagens utveckling av webbapplikationer, vilka blir alltmer komplexa, är det viktigt att testa sina webbapplikationer grundligt. En kort exekveringstid av testerna är särskilt viktigt, då de komplexa webbapplikationerna tar allt längre tid att testa manuellt. Det är angeläget att använda automatiserade GUI tester, för att stödja Agila arbetssätt med korta tider för leverans av nya versioner. För att säkerställa att de kan användas vid varje hopslagning av grenar i utvecklingsspåren inför en leverans av den kommande versionen. Ett problem med automatiserade GUI tester är att det alltid har varit svårt att underhålla testfallen när webbapplikationen har ändrats. Därför är det viktigt att det är lätt att underhålla testfallen i testverktygen. I den här studien har två testverktyg för automatiserade GUI tester utvärderats avseende underhållbarhet och exekveringstid. Fördelar och utmaningar med att introducerade automatiserade GUI tester har även de lyfts fram och analyserats. För att undersöka vilka fördelar och utmaningar som finns med att introducera automatiserade GUI tester utfördes en litteraturstudie på tidigare studier. Ett antal fördelar och utmaningar med automatiserade GUI tester har lyfts fram. Den genomgående största utmaningen med automatiserade GUI tester är underhållbarheten av testfallen. När webbapplikationen vidareutvecklas och framförallt i ett tidigt stadium i dess livscykel när mycket ändrar sig är det kostsamt att underhålla testfallen. Det är även en utmaning att implementera testfallen på ett sådant sätt att det blir lätta att underhålla. Vad gäller fördelar är den absolut främsta tidsvinsten i exekveringstid av testfall samt ökad kvalitet genom att tester utförs oftare. Det första experimentet som har utförts var att jämföra exekveringstiden mellan Cypress och Selenium Webdriver. Ett antal testfall har skapats som återspeglar hur webbapplikationen används. Experimentet visar att Selenium Webdriver presterar bättre än Cypress när det exekveras på en utvecklingsdator. Ytterligare jämförelse av prestandan i en CI miljö bör utföras för att se hur Cypress presterar med parallell exekvering av testfall. Det andra experimentet som utförts jämför underhållbarhet mellan Cypress och Selenium Webdriver. Resultatet av det här experimentet har visat att det finns fördelar och nackdelar med båda testverktygen och hur testfallen är skrivna. Cypress är i det här fallet något mer robust när strukturen på sidan ändras. Cypress klarade av ändringen utan några uppdateringar i testkoden. Selenium Webdriver visades vara lite bättre på att hantera när texten på elementen ändras. Det här beror primärt på hur testfallen är skrivna. Experimentet ger ingen tydlig indikation på vilket testverktyg som är bäst. Det visar mest hur olika svårt det är att skriva testfallen och att komma igång med dem i de båda testverktygen. Problemet med underhållbarhet finns fortfarande kvar. Cypress som ett nytt testverktyg lyckas inte lösa det fullständigt. Resultatet av experimentet visar att det inte finns ett testverktyg som kan klassas som bäst. Däremot har Cypress en lovande framtid som ett testverktyg, det är lättare att komma igång med och har bra verktyg vilket underlättar arbetet som testare.