This paper focuses on the importance of effective software development processes and a foundational understanding of success factors in the public sector. Although there has been significant investment in information technology, not all public sector software projects result in a successful return on investment. This study explores the crucial factors, referred to as Critical Success Factors (CSFs), that enable the success of public sector software development projects. Additionally, this study aims to discover if the CSFs, the Software Development Life Cycle (SDLC), or its methodologies are more impactful for the success of software projects. This study aims to also identify the challenges public sector developers face during their efforts. By analyzing empirical data collected from a US Department of Defense Research and Development organization, this research aims to provide essential information for improving the likelihood of successful software project outcomes. Ultimately, this research can enable decision-makers to create better training opportunities, standard operating procedures, and hiring processes for public sector software projects.

Information system development (ISD) project is a knowledge-intensive teamwork process which requires members to coordinate their expertise to generate the final outcome. Breakdown or coordination and insufficient knowledge integration have been reported as critical factors which lead to ISD project failure. Most existing coordination literature focus on the effect of administrative coordination mechanisms toward project performance which hints that more efforts are needed to understand expertise coordination and explore ways to improve it. Addressing the above issues, two studies in this dissertation attempt to understand expertise coordination within the IS development team based on social capital perspective. The first study, based on intention-behavior literature, knowledge management research, and Gerwin's (2004) coordination model, investigates relationships among willingness, competence, and actual expertise coordination. The relationships between expertise coordination and teamwork outcomes are also examined. The second study incorporates social capital theory and examines (1) dependencies among three dimensions of social capital and (2) linkage between social capital and expertise coordination. Data collected from more than five hundred information systems project team members was used to test the proposed hypotheses. The analysis results confirmed most of the hypotheses. This dissertation contributes to coordination, project management, and team mental model research through many perspectives. In each study, directions for management practice and future research are discussed.

Since 1970, high project failure rate and low user satisfaction has elicited research on users and their role in the process. It is believed that users' physical participation or psychological involvement in the development process can improve user satisfaction and/or system quality. Previous research treats users as a source of requirements and hypothesizes satisfaction to increase when requirements are fulfilled. However, inconsistent conclusions lead to confusion. Recently, a co-production concept has been proposed to understand consumer participation in product development process. In this reconceptualization, users, instead of requirement generator, should be part of the production. In this study, based on co-production concept, we view users as one knowledge source and study how knowledge can be coordinated through the co-production process. After collecting data from 97 system users, most of the hypothesized relationships have been confirmed. IS-user co-production has a positive effect on expertise coordination and, in turn, improves teamwork outcomes. The only relationship that is not significant is between "bring expertise to bear" and "creativity." Implications for practitioner and suggestion for future research are provided. Co-production was found to be a second-order construct comprised of multiple formative constructs. Higher levels of coproduction behavior were expected and were found to produce better outcomes of collaborative efforts. For future study, this relationship is expected to hold true when pairs of information systems developers and information systems users who have worked together on the same information systems development project are surveyed at the end of their projects (or just before it ends or recently thereafter).

High-speed laser triangulation 3D cameras, such as the Ranger3 from SICK, transmit image data to a PC for processing. The camera’s operational speed is constrained by the capabilities of the transmission link. By compressing the data, the bandwidth requirements of the camera is reduced. This thesis presents the development of a lossless image compression format developed for this purpose. The proposed image compression format features a single-pass encoder that utilizes run-length and delta encoding. It is designed to be suitable for implementation on field-programmable gate arrays (FPGAs) within high-speed laser-scanning cameras. Furthermore, the format offers configurability through parameters, enabling optimization for diverse types of image data to achieve more efficient compression. The compression ratio of the image compression format was evaluated using a range oftypical images captured by a Ranger3 camera. The compression ratio was measured across different configurations of the format and subsequently compared with that of PNG. The compression ratio achieved by the proposed format is on par with that of the PNG format, despite having a much simpler encoding process.

A significant part of the software development effort is spent on detecting deviations between software implementations and specifications, and subsequently locating the sources of such errors. This thesis illustrates that is possible to identify a significant number of errors during static analysis of declarative object-oriented equation-based modeling languages that are typically used for system modeling and simulation. Detecting anomalies in the source code without actually solving the underlying system of equations provides a significant advantage: a modeling error can be corrected before trying to get the model compiled or embarking on a computationally expensive symbolic or numerical solution process. The overall objective of this work is to demonstrate that debugging based on static analysis techniques can considerably improve the error location and error correcting process when modeling with equation-based languages. A new method is proposed for debugging of over- and under-constrained systems of equations. The improved approach described in this thesis is to perform the debugging process on the flattened intermediate form of the source code and to use filtering criteria generated from program annotations and from the translation rules. Each time when an error is detected in the intermediate code and the error fixing solution is elaborated, the debugger queries for the original source code before presenting any information to the user. In this way, the user is exposed to the original language source code and not burdened with additional information from the translation process or required to inspect the intermediate code. We present the design and implementation of debugging kernel prototypes, tightly integrated with the core of the optimizer module of a Modelica compiler, including details of the novel framework required for automatic debugging of equation-based languages. This thesis establishes that structural static analysis performed on the underlying system of equations from object-oriented mathematical models can effectively be used to statically debug real Modelica programs. Most of our conclusions developed in this thesis are also valid for other equation-based modeling languages. / <p>Report code: LiU-Tek-Lic-2002:37.</p>

Many websites and products rely heavily on consumers’ usage habits to maximize profit. Therefore, this project aims to aid product development by analyzing server traffic logs. The proposed solution is a monitoring system focusing on user analytics. The website for this monitoring system contains graphical presentations of statistics on user activity, browser usage, OS usage, browser version usage and OS version usage, most common requests, and the slowest requests over a chosen time interval. Statistical calculations are made in the backend code through connections to two databases. One database contains server traffic logs and is connected to the second database through indexing. Testing on the application proved proper functionality and fulfilled the requirements. The performance testing on the application showed effectiveness with relatively low latency for most statistics methods. This latency was further reduced by 50% using indexing. / Många webbplatser och produkter är mycket beroende av konsumenter och deras användningsvanor för att maximera vinsten. Därför syftar detta projekt till att hjälpa produktutvecklingen genom att analysera servertrafikloggar. Den föreslagna lösningen är ett övervakningssystem med fokus på användaranalys. Hemsidan för detta övervakningssystem innehåller grafiska presentationer av statistik över användaraktivitet, webbläsaranvändning, OS-användning, webbläsarversionsanvändning och OS-versionsanvändning, vanligaste förfrågningar och de långsammaste förfrågningarna under ett valt tidsintervall. Statistiska beräkningar görs i backend-koden genom kopplingar till två databaser. En databas innehåller servertrafikloggar och är kopplad till den andra databasen genom indexering. Testning på applikationen visade att den fungerade korrekt och uppfyllde kraven. Prestandatestningen på applikationen visade effektivitet med relativt låg latens för de flesta statistikberäknande metoder. Denna latens reducerades ytterligare med 50 % med hjälp av indexering.

No description available.

Software is present in almost all aspects of our lives, and with more parts of life beingdriven by code, the importance of limiting bugs is critical. Studies have shown that thelonger a bug is present in a system increases the complexity of finding and handlingthe bug. Tools aimed to find bugs before they enter a system exist, but usually requiressignificant amount of data before working. This thesis aims to investigate if the stateof-the-art bug detection tool, JITLine, can be used on projects from the start. Thiswas investigated by performing cross project bug predictions, by training on an alreadyexisting system and then using the trained model on a new system. Different iterationswere done to simulate varying scenarios. It was quickly shown that a good matchbetween the project where data was gathered from and JITLine was crucial. But evenfor the best match that was evaluated, the result was significantly lower than what isto be considered a good result in the Machine Learning (ML) world. Therefor it wasconcluded that JITLine was not suited for cross project bug predictions, and therefornot suited for new projects

As part of a push for renewal by radio and communications-based company Ericsson, the company launched a new brand identity called Brand 2.0 and began to construct the Ericsson Design System (EDS), a toolbox of digital design and development resources. The purpose of the EDS is to streamline and speed up the design and development process, help maintain consistency in design across products and improve communication between teams. This study aims to find potential areas for improvement of the EDS. To accomplish this, we compare the Ericsson Design System to the best practices of what makes an effective design system, as well as compare it to other companies’ publicly available design systems. To make this comparison, we performed an expert evaluation of the EDS and conducted interviews with Ericsson employees with experience with the design system to understand its strengths and weaknesses. The study found that the EDS is well suited for developers using the supported platform, but lacks some big-picture support for designers. System adoption would benefit from a push for political support within Ericsson. / Som del av en förnyelseprocess på kommunikationsföretaget Ericsson så lanserade företaget en ny varumärkesidentitet kallad Brand 2.0, och påbörjade konstruktionen av Ericsson Design System (EDS), en samling av digitala design- och utvecklingsresurser. EDS syfte är att understödja kommunikation, effektivisera design- och utvecklingsprocesser för mjukvaruprodukter, samt bidra till en mer konsekvent design mellan olika produkter inom bolaget.Denna studie utvärderar Ericsson Design System med syftet att finna förbättringsmöjligheter för systemet. För att uppfylla detta syfte gjordes en jämförelse med industribeprövad praxis för vad som gör ett effektivt designsystem, samt en jämförelse med designsystem från andra aktörer. För att göra denna jämförelse utfördes en expertanalys samt en intervjustudie som hämtade data från befintliga användare av Ericsson Design System. Studiens resultat visar att EDS är väl anpassat till att stödja utvecklare som använder den avsedda plattformen, men saknar visst stöd för designers, och att systemets användning skulle kunna breddas om det hade ett starkare strukturellt stöd i Ericssons internpolitik.

Software testing can be cumbersome and complicated. The complexity of the tests increases when the software itself becomes larger and more complex. When continuous integration is applied to software development feedback to tests can be obtained regularly.  These tests are performed in stages and each loop provides test results.A theoretical model for assigning confidence to different testing stages is presented in this thesis to aid in the understanding of the test quality. The input to the model was based on information given in interviews in a case study performed at Ericsson AB. The model is based on the ISO/IEC 25010 standard for software product quality. The theoretical model presented is focused on the early stages of integration and evaluated qualitatively. Its input is delivery test results, trouble reports both from customers and internal testers, and continuous integration flow trends. It was concluded that the theoretical model can be easily automated as each input source can be automatically collected. For developers working in the early stages of integration the model could be of help to give insight into what confidence they can assign their to test's quality. For testers working later in the flow the suitability of the model requires alterations that cannot be deduced from this thesis alone. For other stakeholders the usefulness of the model depends on how involved their work is in the development chain.