As the software is constantly evolving, licensing choices in complex business environments are becoming more and more sophisticated, since licenses are used to govern software costs, access, and responsibilities. With the right licensing model in place and efficiently utilized licensing flow, organizations are able to ensure that the software is being used according to the licensing agreement which can strongly influence the return on software investment. The main objective of this thesis is to investigate what the process looks like when dealing with licenses that are tailored for a huge and complex software products, focusing on identifying improvement areas and proposing possible solutions in order to improve the license management in general. To achieve defined objective, this research has conducted a case study and qualitative comparison combining both published research and a real business context by performing sixteen interviews in two companies. Some of the main results of the investigation are: (i) license management is affected by the complete software end–to-end flow and such needs to be controlled by providing automated mechanisms for managing licenses through lifecycle changes, starting from the order step, through activation, upgrade, return, etc, (ii) centralized entitlement management (licensing server) should be established with shared and consistent view between all integrated systems to ease the process of tracking of all customer entitlements in one place,(iii) the license key files should not be delivered manually (via email) and in general, manual keys are the bottlenecks in the automated flow, (iv) contracts should be standardized in the first place to avoid manual translations from the customer purchase order into the sales order, (v) blockchain can be considered as a future trend towards software license management in various use cases (vi) usage-based and subscription-based licensing models are becoming more and more popular. The conclusions drawn from this study together with the presented results can help the research community to identify key strategies when exploring license management, but we believe it is also a good starting point to reveal possible directions for future research in this field as well.

The rapidly increasing complexity of safety-critical embedded systems has been the cause of difficulty in assuring the safety of safety-critical embedded systems and managing their documentation. More specifically, current approaches to safety assurance are struggling to keep up with the complex relationships be- tween the ever growing number of components and the sheer amount of code underlying safety-critical embedded systems such as road vehicles. We believe that an approach to safety assurance able to cope with this complexity must: i) have sound mathematical foundations on which safety assurance can be built; and ii) provide a formal framework with precisely defined semantics in which the assurance can be represented. In doing this, assurance can be made less ad-hoc, more precise and more repeatable. Sound mathematical foundations also facilitate the creation of tools that automate many aspects of assurance, which will be invaluable in coping with the complexity of modern-day and future embedded systems. The model-based framework that achieves this is + Workflow . This framework is rigorous, developed on proven notations from model-based methodologies, comprehensively integrates assurance within the development activities, and provides the basis for more formal assurance cases. / Thesis / Master of Applied Science (MASc)

Det här projektet går ut på att utveckla en produkt som ska underlätta för privatpersoner att ha koll på ett fordons temperatur och luftfuktighet på ett snabbt och enkelt sätt. Den utvecklade produkten ger nya uppdateringar om hur insidan av fordonet förändras. Med hjälp av en molntjänst kan man genom mobil, PC eller Linux få en inblick på klimatet inuti ett fordon. Processen startade med en marknadsanalys för att se om marknaden är i behov av en digitaliserad termometer. Därefter började projektgruppen undersöka hur farligt ett varmt fordon kan vara för djur och människor. Undersökningen visade att dagens fordon inte har kapabilitet att mäta klimatförändringar och lufkfuktighetsförändringar. Produkten utvecklas på ett sådant sätt att den kontinuerligt kan förbättras. Denna process gör att projektgruppen kan arbeta med produktens utveckling samtidigt som behovet av en portabel termometer & luftfuktighetsmätare ligger i framkant. Resultatet av produkten är en funktionell prototyp som kan mäta temperatur och luftfuktighet. Information kring temperatur och luftfuktighet matas in i Raspberry Pi och sedan in på molntjänst hemsidan där informationen enkelt visas på en Mobiltelefon eller PC. Värdena uppdateras var tionde sekund. Prototypen motsvarade projektgruppens förväntningar, men den kunde utvecklats ytterligare ifall den material som behövdes fanns tillgängligt. / This project aims to develop a product that will make it easier for private individuals to keep track of a vehicle's temperature and humidity in a quick and easy way. The developed product provides new updates on how the inside of the vehicle changes. With the help of a cloud service, you can get an insight into the climate inside a vehicle via mobile, PC or Linux. The process started with a market analysis to see if the market is in need of a digitized thermometer. The project team then began to investigate how dangerous a hot vehicle can be for animals and humans. The study showed that today's vehicles do not have the capacity to measure climate change and humidity changes. The product is developed in such a way that it can be continuously improved. This process allows the project team to work with product development while the need for a portable thermometer & humidity meter is at the forefront. The result of the product is a functional prototype that can measure temperature and humidity. Information about temperature and humidity is entered into the Raspberry Pi and then into the cloud service website where the information is easily displayed on a Mobile Phone or PC. The values are updated every five seconds. The prototype met the project group's expectations, but it could have been further developed if the material needed was available.

Software Quality Assurance (SQA) is a critical aspect of the software development life cycle, ensuring the delivery of high-quality software products. This systematic literature review provides an overview of product, process and people metrics used in SQA, as well as the relationship between different metrics. Product Metrics focus on evaluating the characteristics and attributes of the software product itself. Pro- cess Metrics centre around the software development and testing processes. People Metrics focuses on evaluating the performance, skills, and collaboration of the indi- viduals involved in the software development team.  This study not only synthesizes existing knowledge on SQA measurements, but also elucidates the complicated interactions between these many metrics, offering a comprehensive understanding of their interaction. Furthermore, it methodically finds and addresses discrepancies in the identification and description of various in- dicators, helping to standardize SQA methods.  The paper also covers a range of technologies used for the quantification of the defined metrics with the goal of measurement accuracy and efficiency. The exami- nation of these tools not only aids in the practical comprehension of metric measure- ment but also the selection of appropriate instruments for certain SQA scenarios.  As software systems grow in complexity and size, the findings of this study are a significant resource for practitioners, researchers, and stakeholders alike, providing a nuanced viewpoint on improving software quality through strong SQA techniques.  Keywords: Product metrics, Process metrics, people metrics, Software quality as- surance, Development cycle Software Quality Assurance (SQA) Metrics Evaluation Product Metrics Process Metrics People Metrics Software Development Life Cycle (SDLC).

Software Quality Assurance (SQA) is a critical aspect of the software development life cycle, ensuring the delivery of high-quality software products. This systematic literature review provides an overview of product, process and people metrics used in SQA, as well as the relationship between different metrics. Product Metrics focus on evaluating the characteristics and attributes of the software product itself. Process Metrics centre around the software development and testing processes. PeopleMetrics focuses on evaluating the performance, skills, and collaboration of the individuals involved in the software development team. This study not only synthesizes existing knowledge on SQA measurements but also elucidates the complicated interactions between these many metrics, offering a comprehensive understanding of their interaction. Furthermore, it methodically finds and addresses discrepancies in the identification and description of various indicators, helping to standardize SQA methods. The paper also covers a range of technologies used for the quantification of the defined metrics with the goal of measurement accuracy and efficiency. The examination of these tools not only aids in the practical comprehension of metric measurement but also in the selection of appropriate instruments for certain SQA scenarios. As software systems grow in complexity and size, the findings of this study are significant resources for practitioners, researchers, and stakeholders alike, providing nuanced viewpoints on improving software quality through strong SQA techniques. Keywords: Product metrics, Process metrics, people metrics, Software quality assurance, Development cycle Software Quality Assurance (SQA) Metrics evaluation metrics Process Metrics People Metrics Software Development Life Cycle(SDLC).

In a software life-cycle Source code repositories serve as vast storage areas for program code, ensuring its maintenance and version control throughout the development process. It is not uncommon for these repositories to house programs with hidden errors, which only manifest under specific input conditions, causing the program to deviate from its intended functionality. The growing intricacy of software design has amplified the time and resources required to pinpoint and rectify these issues. These errors, often unintended by developers, can be challenging to identify and correct. While there are techniques to auto-correct faulty code, the expansive realm of potential solutions for a single bug means there's a scarcity of tools and datasets for effective evaluation of the corrected code. This study presents FIXEVAL, a benchmark that includes flawed code entries from competitive coding challenges and their corresponding corrections. FIXEVAL offers an extensive test suite that not only gauges the accuracy of fixes generated by models but also allows for the assessment of a program's functional correctness. This suite further sheds light on time, memory limits, and acceptance based on specific outcomes. We utilize cutting-edge language models, trained on coding languages, as our reference point and juxtapose them using match-based (essentially token similarity) and execution-based (focusing on functional assessment) criteria. Our research indicates that while match-based criteria might not truly represent the functional precision of fixes generated by models, execution-based approaches offer a comprehensive evaluation tailored to the solution. Consequently, we posit that FIXEVAL paves the way for practical automated error correction and assessment of code generated by models. Dataset and models for all of our experiments are made publicly available at https://github.com/mahimanzum/FixEval. / Master of Science / Think of source code repositories as big digital libraries where computer programs are kept safe and updated. Sometimes, these programs have hidden mistakes that only show up under certain conditions, making the program act differently than planned which we call bugs or errors. As software gets more complex, it takes more time and effort to find and fix these mistakes. Even though there are ways to automatically fix these errors, finding the best solution can be like looking for a needle in a haystack. That's why there aren't many tools to check if the automatic fixes are right. Enter FIXEVAL: our new tool that tests and compares faulty computer code from coding competitions and their fixes. It has a set of tests to see how well the fixed code works and gives insights into its performance and results. We used the latest computer language tools to see how well they fix code, comparing them in two ways: by looking at the code's structure and by testing its function. Our findings? Just looking at the code's structure isn't enough; we need to test how it works in action. We believe FIXEVAL is a big step forward in making sure automatic code fixes are spot-on. Dataset and models for all of our experiments are made publicly available at https://github.com/mahimanzum/FixEval.

Today stereotactic neurosurgery is a demanding and time-consuming procedure. To help the surgeons different tools are used. Elekta has developed a frame called the Leksell Vantage Stereotactic System (LVSS). The problem with the frame that Elekta has created is that for some inputs the system is blocking trajectories. Elekta tasked the author with producing a prototype app that evaluates pre-planned trajectories for possible collisions.  The prototype app is written in Rust using the Bevy game engine, the software simulates stereotactic coordinates and angles for evaluating neurosurgery trajectories. Testing reveals accurate X, Y, and Z scale movements, with some collision detection inconsistencies and alignment issues. Hardware requirements emphasize moderate specifications for RAM, CPU, and GPU utilization. The LVSS Simulator prototype app, facilitates coordinate manipulation, collision detection, and visual feedback. While patient-specific planning tools exist, the LVSS Simulator serves as a general application for trajectory planning based on equipment specifications.  The developed software shows strengths and weaknesses, with improvements suggested for collision handling and alignment. The software's reliability metrics are of small size, 794 lines of code (LOC) and moderate complexity because of McCabe's Cyclomatic Complexity (MCC).

No description available.

Dokumentet är en rapport om skrubbning i livevideo från drönare. Beställare av produkten är Fredrik Falkman på Remote Aero. Utförandet gjordes av åtta studenter från Linköpings universitet i kursen Kandidatprojekt i programvaruutveckling-TDDD96 år 2024.Målet med projektet var att skapa ett användargränssnitt för en drönare. I användargräns-snittet skulle det vara möjligt att ta ut bilder från drönarens livevideo. Detta i syfte attunderlätta Svenska Sjöräddningssällskapets livräddningar genom att kringgå risken attbesättningen blint ser på liveströmmen istället för att ha ögonen ute på vattnet. Gruppen utvecklade en webbapplikation som gjorde det möjligt att ta emot en live-ström från en server, plocka ut stillbilder och skicka dem vidare. I texten beskrivs också hur gruppen arbetat med det agila ramverket Scrum, vilka för- och nackdelar det haft, hur sprintar planerades och hur en systemanatomi var till hjälp.

Följande dokument är en rapport gällande projektet Webbapplikation för terminering avdrönarflygning. Projektet beställdes av OutSmart AB samt Sjöräddningssällskapet och utfördesav åtta studenter vid Linköpings universitet som kandidatprojekt i programvaruutvecklingunder våren 2024. Rapporten redogör för hur värde skapades för kunden, vilkaerfarenheter som gruppen tar med sig, samt hur en systemanatomi användes för att få stödunder utvecklingen. Projektets mål var att skapa en användarvänlig webbapplikation somnyttjade OutSmarts befintliga system, som kommunicerar mellan drönaren och systemetsom utvecklas. Syftet med webbapplikationen var att kommunicera med GPS-enheter föratt terminera en drönares flygning. Projektet skapade värde för kunden genom applikationensom projektet resulterade i, samt förslag för hur det redan befintliga systemet kanförbättras. Flera erfarenheter dokumenterades, exempelvis hur nyttjandet av kontinuerligintegration leder till färre merge-konflikter. Systemanatomin användes både under planeringsfasenför att strukturera arbetsflödet och kontinuerligt under utvecklingen för attskapa en fördjupad förståelse av den aktuella statusen.