The job of healthcare professionals in the healthcare sector has never been more critical than now due to the current unprecedented rate of long-term IT infrastructural changes and digital transformation. The 2019/2020 COVID-19 pandemic has been a major driver of these changes. Cultivating a culture of digital innovation and transformation is now at the forefront of the healthcare value-chain. There is an increased need to optimize the operations of the healthcare system, improve collaboration among Health Teams and deliver more agile and secure applications to support both clinical and administrative processes in healthcare institutions. These driving forces require a vision and strategy for digital transformation in the healthcare system, involving a closer look at modern DevSecOps best practices in the application development process. The fast-growing popularity of Cloud Computing has driven the consideration of Low-Code Development Platforms (LCDP), built securely in the cloud infrastructure, to support the transformation of the healthcare system. Low-Code Development Platforms are being considered by enterprises around the world to deliver rapid software development, continuous delivery, and continuous integration of their application systems. The William Osler Health System is recognized for its adoption of technological innovations for improved patient experience and satisfaction. Its innovations include the use of the Microsoft Cloud for Healthcare platforms; and Microsoft 365 and Power Platform services with embedded Low-Code technology to automate and optimize internal operational processes. The aim of this master’s thesis is to demystify the concept of cloud-based Low-Code Application Development approaches to healthcare software development by using a case study of a healthcare application within the systems being built to support operational processes in the William Osler Health System. This study contrasts challenges of current internal tools and methods of operations, communication, and application development in the organization, with the potential benefits of using cloud-based Low-Code platforms to drive digital transformation. / Thesis / Master of Science (MSc)

Software development is a growing part of many businesses today. The software development approach that is used to develop new software may have a positive or negative impact on the efficiency and quality of the final software product. The objective of this thesis was to propose a refined software development approach and to test it empirically. The software development approach is comprised of three main subcomponents: development style, development architecture, and technical documentation. The software development approach was applied in a case study in cooperation with Ericsson. At the completion of the case study, questionnaires were administered to Ericsson employees to evaluate the success of the software development approach. The results showed that the quality of the software product was high and Ericsson was pleased with the result. The results indicated that the development approach helped the case study be successful in some of the researched areas. The end results suggest that the proposed software process has the potential to be successful in other projects of a similar type and structure.

Distribuerade agila mjukvaruutvecklings-metoder har aldrig varit mer populärt. Att kunna arbeta hemifrån för att undvika den dagliga pendlingen eller för att samarbeta med utvecklare utomlands har aldrig varit enklare. Tredjepartsverktyg som Zoom och Google Meet förenklar kommunikationsprocessen, och med introduktionen av verktyg som Visual Studio’s “liveshare” som möjliggör realtids-kodning, har agila metoder verkligen flyttat ut från kontoren. Dock är en av de viktigaste komponenterna av att arbeta agilt att arbeta ansikte mot ansikte, vilket innebär att en av de effektivaste metoderna för kommunikation nu förloras när man flyttas till att arbeta med distribuerade metoder. Att övergå till nya metoder är aldrig enkelt, och när företag övergår till en distribuerad framtid kan mjukvaruutvecklare potentiellt drabbas av denna förändring i miljö och metod. Om företag har riktlinjer för övergången till distribuerade metoder kan det potentiellt göra förflyttninen enklare.Problemet är att det inte finns några sådana riktlinjer. Syftet med denna rapport är att skapa riktlinjer med målet att hjälpa organisationer övergå till distribuerade agila metoder från lokala agila metoder. Metoden i denna rapport är en kvalitativ utforskande litteraturstudie tillsammans med utforskande intervjuer som utforskar de positiva och negativa erfarenheterna utvecklare möter när de gör en övergång till distribuerade metoder. Litteraturstudien användes för att formulera forskningskriterierna och intervjufrågorna. Totalt tillfrågades åtta personer som hade erfarenheter av att göra en övergång till distribuerade agila metoder. Dessa intervjuer resulterade i tre generella riktlinjer som kan användas för att förenkla övergången mellan lokala-och distribuerade agila metoder. / Distributed agile software development has never been more popular. Being able to work at home to avoid the commute or simply collaborating with developers abroad has never been easier. Third party tools such as Zoom and Google Meet makes communication easier than ever, and with the introduction of Visual Studio’s live share that enables real-time collaborative coding, distributed agile development truly has moved out of the offices. Yet, one of the core components of the agile working method is working face to face, meaning that one of the most efficient methods of communication is lost upon moving development into a distributed setting. Transitions towards new methods and settings are never easy, and as companies transition towards a remote and distributed future, software developers are potentially burdened by this change in environment. If companies had access to guidelines they could potentially experience a smoother transition. The problem is that there currently do not exist such guidelines. The purpose of this report is to create such guidelines with the goal of helping organizations transition towards distributed agile methods. In this report, the method utilized is a qualitative and explorative literature study, coupled with interviews aimed to explore the positive and negative experiences developers face when transitioning towards distributed methods. A literature study was used to help formulate the research criteria and the interview questions. In total, eight people that had experienced a recent transition towards distributed agile methods were interviewed. These interviews resulted in three general guidelines that can be used to ease the transition between a local and distributed work environment.

The recent growth of the software industry has drawn attention to strategies aimed at improving collaboration within the development team. Shown to frequently encounter dilemmas associated with cross-disciplinary work are User Experience designers and software developers, whose effective collaboration are essential for the success of the development process. Design systems have evolved as a response to the demand for efficient collaboration as a collection of reusable patterns and documentation used to establish a common language within software development teams. The popularity of using design systems within software development projects has grown rapidly in recent years, but little research has yet been conducted on its usability in development work. The goal of this thesis is to study design systems from a developer perspective, and evaluate its ability to facilitate the collaboration within software development teams. By building upon previous work on developer experience, this study proposes a method for assessing design system usability from a developer perspective. In this study, participating software developers were tasked with implementing user interface design in code with the help of a design system, followed by interview questions based on the Cognitive Dimensions Framework. Thematic analysis was used to analyze the data. Results provide insights into design system usability and developer experience. Findings include aspects of design system usability in general, such as the importance of developers' autonomy and flexibility of the system, as well as implications from the tested method in particular, such as the relevance of context of implementation. The results implicated an inherent dilemma of approaching design system development through conventions and best practices rather than with a systems theory and systems thinking perspective. / Senaste tidens tillväxt inom mjukvaruutvecklingsindustrin har resulterat i ett ökat intresse för att effektivisera samarbetet inom utvecklingsteamet. Två yrkesgrupper som påvisats stöta på dilemman associerade med multidisciplinärt arbete är de som designar och utvecklar mjukvara, vars samarbete är avgörande för utvecklingsprocessens framgång. Designsystem har vuxit fram som ett svar på en ökad efterfrågan på effektivt samarbete som en samling återanvändbara mönster och dokumentation som syftar till att etablera en gemensam vokabulär och inom mjukvaruutvecklingsteam. Trots att användandet av designsystem inom mjukvaruutveckling har ökat under de senaste åren har inte mycket forskning gjorts på dess användbarhet i utvecklingsarbetet. Denna uppsats syftar till att studera designsystem från ett utvecklarperspektiv, och utvärdera dess förmåga att facilitera samarbetet inom mjukvaruutvecklingsteam. Genom att ta avstamp i tidigare forskning kring utvecklarupplevelse föreslår denna studie en metod för att bedöma användbarheten och utvecklarupplevelsen av ett designsystem. Deltagande mjukvaruutvecklare fick i denna studie i uppgift att implementera gränssnittsdesign i kod med hjälp av ett designsystem, följt av intervjufrågor baserade på ramverket för Cognitive Dimensions. Tematisk analys användes för att analysera data. Resultaten ger inblick i användbarhet och designsystem i allmänhet, så som vikten av utvecklarens autonomi och systemets flexibilitet, samt implikationer från det testade design systemet i synnerhet, så som implementationskontextens relevans. Resultaten antyder att det finns svårigheter med att närma sig mjukvaruutveckling med designsystem genom konventioner och god praxis snarare än med ett systemteoretiskt perspektiv.

This paper studies how the newly released AI ChatGPT can be used to reduce the time and effort software developers spend on writing unit tests, more specifically if ChatGPT can generate quality unit tests. Another aspect of the study is how the prompting of ChatGPT can be optimized for generating unit tests, by creating a prompt framework. Lastly how the generated unit tests of ChatGPT compare to human written tests was tested. This was done by conducting an experiment where ChatGPT was prompted to generate unit tests for predefined code written in C# or Typescript which was then evaluated and rated. After the generated unit test had been rated, the next steps were determined, and the process was repeated. The results were logged following a diary study. The rating system was constructed with the help of previous research and interviews with software developers working in the industry which defined what a high-quality unit test should include. The interviews also helped in understanding ChatGPT’s perceived capabilities. The experiment showed that ChatGPT can generate unit tests that are of quality, though with certain issues. For example, reusing the same prompt multiple times revealed that the consistency in the responses was lacking. Inconsistencies included different testing approaches (how setup methods were used for example), testing areas and sometimes quality. The inconsistencies were reduced by using the deduced prompt framework, but the issue could be a current limitation of ChatGPT which could be handled with a future release.

Open-source software development is becoming increasingly popular in the public sector due toits potential for innovation and technology integration. This study investigates the possibilities of developing an open-source trip planner using OpenTripPlanner (OTP) for the Uppsala region's growing public transport needs. This thesis aims to increase understanding of the opportunitiesand challenges of open-source software development within the public sector and what lessons can be learned from previous implementations of OTP. The methods used were the development of a stand-alone web-based Proof of Concept of an OTP solution as well as a case study including public organizations that have worked with open-source software development and specifically implementations of OTP. The implementation of the Proof of Concept shows the work effort put in to set up a web-based OTP solution, how it can be used and adapted to the Uppsala region's needs. The results from the case study show that open-source applications can be developed through cooperation within and between regions and countries, resulting in innovative solutions with more transparency and flexibility. The use of OTP has the potential for creating a less complex, streamlined system with flexible and efficient data processing. Challenges include the administration of the data sets used, changing the work culture to more open ways of working and understanding ones needs to develop the right product. The need for a comprehensive system review and the establishment of competent teams or suppliers are identified as critical factors in successful open-source development.

The Agile method has since it got published, of many been regarded as the universal solution to increased flexibility in software development. Scrum is, without a doubt, the most widely used Agile method among software development teams. Nonetheless, there are many challenges with the Scrum method, and therefore, success factors need to be identified to make up for its weaknesses. Lack of enthusiasm or events being time-consuming is some of the challenges the team faces with the framework, which can result in its members only using Scrum partially. For that reason, the main objective of this thesis is to identify which parts of Scrum are most commonly skipped by the members of an Agile development team for software, and why. In the initial study, a content analysis was conducted to examine how people in forums and on social media express themselves regarding Scrum, to identify the most common objections to the framework. The conclusion of the work was that the sprint review was identified as the most common event to skip, and the number one reason for skipping an event was that it felt unnecessary. Sprint planning was the step seen as giving the most negative consequences when skipped, and some of the risks of skipping a step were that it could give less oversight, a low feedback cycle, and a lack of communication, and collaboration. A positive outcome of skipping an event was that it allowed for more time to work, to get an uninterrupted flow and less overhead. To get an even better insight into the Scrum team’s daily work, the future study would be to perform a case study for an in-depth, detailed examination of the challenges with Scrum.

Mobile application development has grown in the past few years, and instead of native development, some developers have moved to a new strategy; cross-platform mobile development using frameworks. There are many frameworks that all have their use case, but whether or not these frameworks are ready to be used in production applications is hard to decide on . This research aims to find the strengths and weaknesses of cross-platform mobile development frameworks, and how they can be improved to better suit the needs of developers. To gather data in this topic a survey was created to analyze developer experiences on frameworks in key areas such as front-end design, platform maturity and more. The results reveal that there are many areas that can be improved, but frameworks are a great tool for smaller teams and are being used extensively already to create applications for multiple platforms.

There can be a lack of trust in distributed workplaces. Former studies have shown how agile frameworks can increase trust, and how to do it further. These studies mostly investigate scrum, but in this study, a modern framework called Shape up, is investigated. The study aims to answer the question “How can modern IT project management frameworks increase perception of trust, coworker to coworker, and towards the process, in distributed software development?” and does so through semi structured interviews on participants from an american software company, Ambassador Labs, and then analyzed through thematic analysis. The goal, and delimitation of the study, will be on personal experience and perceived trust, rather than measurements. This is partly due to the scarcity of participants and lack of time. Questions in the interview template are inspired by former similar studies, a definition of trust, and different types of trust. In total, 5 themes were found. This being, how the company applies Shape up and what additions they have, group and individual accountability and autonomy, communication and collaboration, pressure, stress, and focus, and shape up and trust. The most frequent topics of discussion being the flexibility of shape up, and how it gives increased accountability, autonomy and good group dynamics, and the lack of communication cross teams and regarding the future. Further studies could be qualitative or quantitative and have larger samples to strengthen dependability of the result. Furthermore, the results of this study can be used as a guide to what should be investigated and measured in a quantitative study. Lastly, continuous studies on how different variables, beyond using a flexible framework in a distributed workplace, affects trust should be done.

Indiana University-Purdue University Indianapolis (IUPUI) / Component-Based Software Development (CSBD) has gained widespread importance in recent times, due to its wide-scale applicability in software development. System developers can now pick and choose from the pre-existing components to suit their requirements in order to build their system. For the purpose of developing a quality-aware system, finding the suitable components offering services is an essential and critical step. Hence, Service Discovery is an important step in the development of systems composed from already existing quality-aware software services. Currently, there is a plethora of new-age devices, such as PDAs, and cell phones that automate daily activities and provide a pervasive connectivity to users. The special characteristics of these devices (e.g., mobility, heterogeneity) make them as attractive choices to host services. Hence, they need to be considered and integrated in the service discovery process. However, due to their limitations of battery life, intermittent connectivity and processing capabilities this task is not a simple one. This research addresses this challenge of including resource constrained devices by enhancing the UniFrame Resource Discovery System (URDS) architecture. This enhanced architecture is called Mobile Device Enabled Service Discovery System (MDE-URDS). The experimental validation of the MDE-URDS suggests that it is a scalable and quality-aware system, handling the limitations of mobile devices using existing and well established algorithms and protocols such as Mobile IP.