Denna rapport gjordes som en del av kursen TDDD96 och beskriver det arbete som gjorts åt Teknikåttan under våren 2021. Projektets mål var att skapa ett väldokumenterat tävlingssystem som skulle vara lätt för andra att utöka vilket gruppen också lyckades med. Tävlingssystemets syfte var att ge Teknikåttan ett modernt och användarvänligt sätt att skapa, administrera och köra sina tävlingar. Systemet konstruerades som en webbapplikation med databas, server och klient. Databasen och servern skrevs med programspråket Python och klienten med Typescript. De viktigaste biblioteken som användes var Flask för servern, SQLAlchemy för databasen samt React och Material-UI för klienten.

Rapporten beskriver ett projektarbete i kursen TDDD96 - Kandidatprojekt i programvaruutveckling. Arbetet genomfördes under våren 2023 på Linköpings universitet. I kursenhar tio studenter inom civilingenjörsprogrammen i data- eller mjukvaruteknik framställten applikation (HÄST) åt den externa kunden Personalkollen. Syftet med arbetet var attdokumentera och utvärdera applikationen och utvecklingsmetodiken för att dra slutsatserkring framtida arbeten. Syftet med applikationen var att presentera statistik av kundservice medarbetare och därmed skapa värde för kund. Resultatet visar att utvecklingen effektiviserades genom en tydlig rolluppdelning, kontinuerliga möten samt användning avarbetsmetoden Scrum.

Mobile application development and testing involves even greater challenges than traditional software development, given that the large number of existing devices, each with unique hardware configuration and operating system needs to be considered. Software testing constitutes a big and important part of development, where the majority of the tests are performed manually. This is time consuming and expensive. The purpose of this thesis project is therefor to examine the current test process at the company Dewire, in an effort to find ways to improve it by introducing automated tests for the Android mobile platform. The automation frameworks Appium and Espresso will be evaluated and combined with existing systems like Jenkins that already applied in Dewires agile work procedure. A test environment been implemented during this thesis project as a proof of concept, where tests are run on a real device as the application is being built. Test cases from an ongoing development project has been implemented and the results evaluated. This thesis project has shown that the framework Espresso together with a Jenkins build-server has great potential to reduce manual testing and streamline the test process. It has also shown that test automation should be implemented from start of a project, where tests are continuously kept up to date during development to be profitable. At the same time results show that test automation involves a significant time investment before time and money can be saved. / Mobilapplikationsutveckling och testning innebär en större utmaning än traditionell mjukvaruutveckling eftersom hänsyn måste tas till ett stort antal enheter, alla med unik hårdvara, skärmstorlek och operativsystem. Mjukvarutestning utgör en viktig och stor del av utvecklingen av applikationer där majoriteten av testerna idag genomförs manuellt. Detta är tidskrävande och ekonomiskt kostsamt. Syftet med detta examensarbete är därför att undersöka nuvarande testprocess hos företaget Dewire och hitta möjliga förbättringar genom att införa automatiserade tester för mobilplattformen Android. Automatiseringsverktygen Appium och Espresso utvärderas i kombination med befintliga system som Jenkins som redan används i Dewires agila arbetssätt. Under examensarbetet har en testmiljö implementerats som ett sätt för visa att konceptet fungerar, där tester körs på en testenhet i samband med att applikationen byggs. Testfall från pågående utvecklingsprojekt har implementerats och resultaten av denna automatisering har utvärderats. Examensarbetet har visat att verktyget Espresso tillsammans med en Jenkins byggserver har stor potential att effektivisera och minska manuellt testande. Arbetet visar också att testautomatisering bör implementeras från projektstart och att tester aktivt underhålls under utvecklingen för att vara lönsamt. Resultatet visar samtidigt att testautomatisering till en början innebär en väsentlig tidsinvestering innan tid och pengar kan sparas.

This bachelor thesis focuses on distributed version control systems and workflows used when working with such systems. The thesis will investigate benefits and disadvantages in using distributed version control in software development using a literature review of the available articles on the subject as well as a post-mortem analysis (with questionnaires and data collected from the build environment) of a student run software engineering project. We find that the migration costs are high, but that the advantages may outweigh its drawbacks for some. We conclude that many projects would benefit from migrating, but in particular, that new projects would not only benefit, but also not have high migration costs. / En undersökning om hur man kan arbeta med moderna, distribuerade, versionshanteringssystem. Baserat på dels en literaturstudie, och dels en frågeundersökning bland studenter på BTH dras slutsatsen att det både finns för- och nackdelar, men att fördelarna verkar väga över i det generella fallet. / Jag (Olof Johansson) är nåbar främst per e-post, men även på telefonnummer +46739467135.

Huvuduppgiften i detta examensarbete har varit att programmera en Android smart-telefon så att den kan kommunicera med en bio-sensor med syfte att skapa automatiska larm vid till exempel hjärtproblem. Hur lösningen har vuxit fram har dokumenterats tillsammans med resultatet av den informationssökning som utförts parallellt inom angränsande ämnesområden. Vid programmeringen har en Service använts för att upprätthålla en prioriterad kommunikationsprocess mellan bio-sensor och telefon. Programprototypen använder även en Widget – en mini applikation på skrivbordet - som är ett snyggt sätt att presentera mätdata. När denna produkt börjar säljas på marknaden kommer den vara klassificerad som en medicinteknisk produkt. Detta innebär att det finns ett speciellt regelverk för leverantören av produkten att följa. Applikationen är enkel att hantera för användarna men det innebär inte att den alltid är lämplig för alla. Hjärtsjuka är oftast inte i form humörmässigt så det är att föredra om patienterna själva kan fås att inse och uppskatta de fördelar som finns med den automatiska kontroll av individens status som applikationen erbjuder. / The main task during this degree project has been code design for an Android Smartphone making it able to communicate with a Bio Sensor to create an automatic alert if for example a heart problem arises. How this application has been developed has been documented together with the result of an information search that has been conducted in adjoining branches of science. The application program uses a Service to maintain high priority for the communication process between the bio-sensor and the phone. The application prototype also uses a Widget – a mini application on the Home Screen – which is a neat way to display data from the sensor. When this product is launched onto the market it will be classified as a medical device. This means that there is a special set of rules that the supplier of the product must follow. This application is easy to use but that does not mean that it always will suit everybody. Persons who suffer from heart disease mostly also suffer from low spirits. Therefore, it is desirable that the patient can be made to realize and to appreciate the advantages of automatic monitoring of the individual status that this application offers.

Today, traditional mechanical and electrical systems are replaced with special ICT (Information and communication technology) based solutions and with the invention of new technologies; this trend is increasing further more. This special ICT-based domain is called Real-time systems and today’s driveby-wire, electronic stability programs in car, control software in vehicles are just a few examples of real time systems. The task is a fundamental element of the software in a real-time system, and it is always necessary to know the longest execution time of a task, since missing a task’s deadline is a not allowed in a time critical hard real-time system. The longest execution time of a task or the Worst Case Execution Time (WCET) is estimated by WCET analysis. This estimation should be tight and safe to ensure the proper timing behavior of the real time system. But this WCET analysis is not always easy to perform, as the execution time of a task can vary by software characteristics like program flow or input data and also by hardware characteristics like speed of CPU, cache, pipeline and others. There are several methods and tools for WCET analysis. Some of them are commercial products and other are research prototypes. To verify and validate WCET analysis tools, evaluations of the tool’s properties are important, and thus WCET benchmark programs has emerged in recent years. These are intended for comparison between these tools properties and associated methods. The Mälardalen WCET benchmark suite has been maintained to evaluate the properties of various tool sets. In this thesis these benchmarks programs have been analyzed by SWEET (Swedish WCET Analysis Tool), the main tool used in this thesis. SWEET is a research prototype for WCET analysis. The main goal of this thesis work was to extend existing benchmark programs for WCET tools. It was obvious that most work load will be on benchmark program extension and at the beginning the work has been started by analyzing different small WCET benchmark programs. The evaluation of SWEET’s properties has been taken into a further extent by analyzing another benchmark program which is called PapaBench, a free real-time benchmark from Paparazzi project that represents a real-time application, developed to be embedded on different Unmanned Aerial Vehicles (UAV). Lots of time was required to complete the analyzing of PapaBench. The main reason behind this extensive work was that we decided to participate with SWEET in WCET Challenge 2011 (WCC 2011). So the purpose of the thesis ultimately turned into analyzing PapaBench instead of extending the WCET benchmark programs. The result of the thesis work is therefore mainly the analysis results from the analysis of PapaBench, which were reported to WCC 2011. The results from WCC 2011 are included in a paper presented at the WCET 2011 workshop, which took place in July 2011 in Porto, Portugal. Another part of the work was to examine real-time train control software which was provided by Bombardier. The main reason behind getting these industrial codes was to possibly add new benchmark programs to the Mälardalen WCET benchmark suite. A thorough manual study of this code has been performed to find out whether new benchmark programs could be found. However, due  to its structure and size, we decided that this code was not suitable to add to the Mälardalen WCET benchmark suite.

In my thesis I focus on providing a foundation of data on whichdecision makers can base refactoring decisions. For this, I examine therelationship between software complexity and maintenance eort. Tomake the data a stronger basis for refactoring decisions, I present anew approach of correlating le metrics to maintenance eort, whereI look at the relation between changes in le metrics over multiplereleases and changes in the maintenance eort spent on these les. Ido this using a broadened and, more complete notion of maintenanceeort. I measure maintenance eort in 4 ways: the amount of lines ofcode that had to be changed to resolve tasks, the amount of discus-sion that tasks generated, the amount of atomic changes to a le thatwere required to resolve a task, and the amount of bugs per month.To test this framework, I extracted data from 3 open source projects,where I measured the variation of both complexity and maintenanceeort, using this new notion of eort, over multiple releases, and in-vestigated their correlation. I found that 21 of the tested metrics weresignicantly correlated to the eort measures, where complexity basedmetrics and incoming propagation cost show the highest correlation.Of the proposed measures for maintenance eort, the amount of dis-cussion to resolve an issue shows the highest correlation to the chosenmetrics.

This thesis provides insight in the further development of an application for managing speed skating events, based on the previous developed application by a group of students in fall 2010. The application was implemented for the Karlstad Speed Skating Club, which before used a program from the 90's. After finishing the implementation, all basic functionality requested by the Karlstad Speed Skating Club can be used for managing speed skating events. The first part of the thesis presents a short summary of our work, comparing what we wanted to implement and what we achieved. A short background on speed skating, the old system, developed by a group of students, and the project requirements are presented. An introduction to the used tools, languages, techniques and development processes is given along with details concerning the implementation of the requirements. Finally, the design of the new user interface is explained and the results are presented, containing an evaluation of the implementation, occured problems and what could be added in the future.

No description available.

Noways the majority of all trading with financial assets are committed via electronictrading platforms (ETP). Nasdaq is a major ETP provider and powers over 100markets worldwide. Because operational disruptions and software bugs can causesignificant economic losses, software testing is a key part of Nasdaqs operations. Thefirst part of this project was to analyze how Nasdaq works with software testing of itsETP called Genium Inet Trading. Based on this analysis a system aimed at simplifyingand streamlining the process of automating functional tests was developed. Functionaltests are a vital part of Nasdaqs quality assurance efforts. The project resulted in a overall conceptual model and a ”proof of concept”implementation called Scenario Runner. The conceptual model describes howfunctional tests specifications can be represented in an abstract level that isindependent of which techniques that are used for implementation. Scenario Runnerwas developed as a plugin to Nasdaqs internal ETP testing software called NeXTWorkstation and uses MS Excel as input format for the functional test specifications.Scenario Runner reads and executes tests in the MS Excel document and presents theresults both in the NeXT Workstation GUI and as an output MS Excel file. Theproject was successful and Scenario Runner can be used to run simple functionaltests, but more importantly, to demonstrate how the conceptual model can be usedfor automating functional tests in practice.