Browsing by study line "Ohjelmistot"
Now showing items 21-40 of 57
-
(2023)This thesis examines the render speeds of WebViews in React Native applications. React Native is a popular cross-platform framework for developing mobile applications, and WebViews allow embedding web content within mobile applications. While WebViews offer the advantage of bringing readily available web content in applications, the cost of using this technology in terms of applications responsiveness is not well researched. The goal of this thesis is to evaluate this cost so that developers and stakeholders can make more informed decisions regarding the use of WebViews in React Native applications. A series of tests was performed using a React Native application that was developed for the purpose of this study. In these tests, we rendered WebViews and similarly appearing views that consist of React Native components, and measured their mean render times. Our analysis of these results revealed that using React Native components instead of WebViews offers significant benefits in terms of rendering performance on both, iOS and Android platforms. The use of WebViews in rendering user interfaces can bring a notable disadvantage in the matter of user experience, especially on Android devices. These findings suggest that rendering Native user interface components instead of WebViews should be preferred if we want to maximize user experience across different devices and platforms.
-
(2022)While the role of IT and computer science in the society is on the rise, interest in computer science education is also on the rise. Research covering study success and study paths is important for understanding both student needs and developing the educational programmes further. Using a data set covering student records from 2010 to 2020, this thesis aims to find key insights and base research in the topic of computer science study success and study paths in the University of Helsinki. Using novel visualizations and descriptive statistics this thesis builds a picture of the evolution of study paths and student success during a 10-year timeframe, providing much needed contextual information to be used as inspiration for future focused research into the phenomena discovered. The visualizations combined with statistical results show that certain student groups seem to have better study success and that there are differences in the study paths chosen by the student groups. It is also shown that the graduation rates from the Bachelor’s Programme in Computer Science are generally low, with some student groups showing higher than average graduation rates. Time from admission to graduation is longer than suggested and the sample study paths provided by the university are not generally followed, leading to the conclusion that the programme structure would need some assessment to better incorporate students with diverse academic backgrounds and differing personal study plans.
-
(2023)Context: An abundance of research on the productivity of software development teams and developers exists identifying many factors and their effects in different contexts and concerning different aspects of productivity. Objective: This thesis aims to collect and analyse existing recent research results of factors that are related to or directly influence the productivity of teams or developers, how they influence it in different contexts and briefly summarise the metrics used in recent studies to measure productivity. Method: The method selected to reach for these aims was to conduct a systematic literature review on relevant studies published between 2017 and 2022. Altogether, 48 studies were selected and analysed during the review. Results: The metrics used by the reviewed studies for measuring productivity range from time used for completing a task to self-evaluated productivity to the amount of commits contributed. Some of these are used by multiple studies and many by only one or a few and measure productivity from different angles. Various factors were found and these range from team size to experienced emotion to working from home during the COVID-19 pandemic. The relationships found between these factors and some aspects of the productivity of developers and teams range from positive to negative and sometimes both depending on the context and the productivity metric in question. Conclusions: While many relationships were found between various factors and the productivity of software developers and development teams in this review, these do not cover all possible factors, relationships or measurable productivity aspects in all possible contexts. Additionally, one should keep in mind that most of the found relationships do not imply causality.
-
(2023)Ship traffic is a major source of global greenhouse gas emissions, and the pressure on the maritime industry to lower its carbon footprint is constantly growing. One easy way for ships to lower their emissions would be to lower their sailing speed. The global ship traffic has for ages followed a practice called "sail fast, then wait", which means that ships try to reach their destination in the fastest possible time regardless and then wait at an anchorage near the harbor for a mooring place to become available. This method is easy to execute logistically, but it does not optimize the sailing speeds to take into account the emissions. An alternative tactic would be to calculate traffic patterns at the destination and use this information to plan the voyage so that the time at anchorage is minimized. This would allow ships to sail at lower speeds without compromising the total length of the journey. To create a model to schedule arrivals at ports, traffic patterns need to be formed on how ships interact with port infrastructure. However, port infrastructure is not widely available in an easy-to-use form. This makes it difficult to develop models that are capable of predicting traffic patterns. However, ship voyage information is readily available from commercial Automatic Information System (AIS) data. In this thesis, I present a novel implementation, which extracts information on the port infrastructure from AIS data using the DBSCAN clustering algorithm. In addition to clustering the AIS data, the implementation presented in this thesis uses a novel optimization method to search for optimal hyperparameters for the DBSCAN algorithm. The optimization process evaluates possible solutions using cluster validity indices (CVI), which are metrics that represent the goodness of clustering. A comparison with different CVIs is done to narrow down the most effective way to cluster AIS data to find information on port infrastructure.
-
(2023)Introduction: The issue of climate change has emerged as a global challenge in response to the increasing consumption of natural resources. As the Information Technology (IT) sector has undergone significant growth in recent years, the implementation of environmentally sustainable practices which lower the environmental impact of software, such as electricity usage, has become imperative. The concept of green in software engineering seeks to address these challenges in the software engineering process. Methods: As the goal is to explore and evaluate different approaches to environmental sustainability in green in software engineering whilst also taking a look into the maturity and evidence level of research about the subject, this study adopts a systematic literature review approach. The search strings, search process and other relevant information are meticulously documented and explored in each step of the research process. Results: Green in software engineering has been identified as a promising field of research, but the absence of agreed-upon definitions and terminology often leads to research efforts replicating the previous studies without a clear reason as to why. The goal of increasing environmental sustainability is commonly agreed on in software engineering, but the concrete steps to achieve it are currently missing. Building a strong body of knowledge, common measurements and tooling to support them and increasing the knowledge about sustainability in the field of software engineering should all be taken into account in an effort to reach the environmental sustainability goals of tomorrow.
-
(2023)Background: The production, operation and use of information technology (IT) have a significant impact on the environment. As an example, the estimated footprint of global greenhouse gas emissions of the IT industry, including the production, operation and maintenance of main consumer devices, data centres and communication networks, doubled between 2007 (1–1.6%) and 2016 (2.5–3.1%). The European Union regulates the energy efficiency of data centre hardware. However, there is still a lack of regulation and guidance regarding the environmental impacts of software use, i.e. impacts from the production, operation and disposal of hardware devices required for using software. Aims: The goal of this thesis is to provide actionable knowledge which could be used by software practitioners aiming to reduce the environmental impacts of software use. Method: We conducted a systematic literature review of academic literature where we assessed evidence of the effectiveness of tools, methods and practices for reducing the environmental impacts of software use. The review covers 20 papers. Results: 60% of studied papers focus on reducing the energy consumption of software that is executed on a single local hardware device, which excludes networked software. The results contain 6 tools, 25 methods and 11 practices. Program code optimisation can potentially reduce the energy consumption of software use by 2–62%. Shifting the execution time of time-flexible data centre workloads towards times when the electric grid has plenty of renewable electricity can potentially reduce data centre CO2 emissions by 33.7%. Conclusions: The results suggest that the energy consumption of software use has received much attention in research. We suggest more research to be done on environmental impacts other than energy consumption, such as CO2 emissions, software-induced hardware obsolescence, electronic waste and freshwater consumption. Practitioners should also take into account the potential impacts of data transmission networks and remote hardware, such as data centres, in addition to local hardware.
-
(2022)Toimijamalli on hajautetun ja samanaikaisen laskennan malli, jossa pienet osat ohjelmistoa viestivät keskenään asynkronisesti ja käyttäjälle näkyvä toiminnallisuus on usean osan yhteistyöstä esiin nouseva ominaisuus. Nykypäivän ohjelmistojen täytyy kestää valtavia käyttäjämääriä ja sitä varten niiden täytyy pystyä nostamaan kapasiteettiaan nopeasti skaalautuakseen. Pienempiä ohjelmiston osia on helpompi lisätä kysynnän mukaan, joten toimijamalli vaikuttaa vastaavan tähän tarpeeseen. Toimijamallin käytössä voi kuitenkin esiintyä haasteita, joita tämä tutkimus pyrkii löytämään ja esittelemään. Tutkimus toteutetaan systemaattisena kirjallisuuskatsauksena toimijamalliin liittyvistä tutkimuksista. Valituista tutkimuksista kerättiin tietoja, joiden pohjalta tutkimuskysymyksiin vastattiin. Tutkimustulokset listaavat ja kategorisoivat ohjelmistokehityksen ongelmia, joihin käytettiin toimijamallia, sekä erilaisia toimijamallin käytössä esiintyviä haasteita ja niiden ratkaisuita. Tutkimuksessa löydettiin toimijamallin käytössä esiintyviä haasteita ja näille haasteille luotiin uusi kategorisointi. Haasteiden juurisyitä analysoidessa havaittiin, että suuri osa toimijamallin haasteista johtuvat asynkronisen viestinnän käyttämisestä, ja että ohjelmoijan on oltava jatkuvasti tarkkana omista oletuksistaan viestijärjestyksestä. Haasteisiin esitetyt ratkaisut kategorisoitiin niihin liittyvän lisättävän koodin sijainnin mukaan.
-
(2023)This thesis explores the Ionic Framework, a popular open-source framework for building hybrid mobile applications using web technologies. The first part of the thesis briefly compares hybrid applications, native applications, and PWAs (Progressive Web Apps). The thesis includes a concise overview of the Ionic Framework through a literature review and a guide on how to use Ionic with React from installation to distribution, providing practical tips and recommendations for developers new to the framework. This part includes a discussion on the tools and technologies required to develop with Ionic, as well as using Ionic UI components and styling them. In addition, this thesis documents an Ionic project and workshop conducted for Knowit Solutions Oy. The project involved building a proof-of-concept mobile application using Ionic, while the workshop provided hands-on training for JavaScript developers on how to use the framework effectively. This thesis aims to introduce the Ionic Framework and demonstrate its usefulness for building mobile applications for iOS and Android with a single codebase.
-
(2023)Background: Continuous practices are common in today’s software development and the terms DevOps, continuous integration, continuous delivery and continuous deployment are fre- quently used. While each one of the practices helps in making agile development more agile, using them requires a lot of effort from the development team as they are not only about au- tomating tasks but also about how development should be done. Out of the three continuous practices mentioned above, continuous delivery and deployment focus on the deployability of the application. Implementing continuous delivery or deployment is a difficult task, especially for legacy software that can set limitations on how these practices can be taken into use. Aims: The aim of this study is to design and implement a continuous delivery process in a case project that does not have any type of automation regarding deployments. Method: Challenges of the current manual deployment process were identified and based on the identified challenges, a model continuous delivery process was designed. The identified challenges were also compared to the academic literature on the topic and solutions were taken into consideration when the model was designed. Based on the design, a prototype was created that automates the deploy- ment. The model and the prototype were then evaluated to see how it addresses the previously identified challenges. Results: The model provides a more robust deployment process, and the prototype automates most of the bigger tasks in deployment and provides valuable information about the deployments. However, due to the limitations of the architecture, only some of the tasks could be automated. Conclusions: Taking continuous delivery or deployment into use in legacy software is a difficult task, as the existing software sets a lot of limitations on what can be realistically done. However, the results of this study prove that continuous delivery is achievable to some degree even without larger changes to the software itself.
-
(2023)Web development is in great demand these days. Constantly developing technologies enables to create impressive websites and mitigates the amount of development work. However, it is useful to consider the performance aspect, which affects directly to user experience. Performance in this context means website’s load times. Front end web development typically involves using Cascading Style Sheets (CSS) which is a style sheet language and a web technology that is used to describe the visual presentation of a website. This research consist of a literature review part, which contains background knowledge about how web browsers work, performance in general, performance metrics along with CSS performance optimization and an empirical part, which includes different benchmarks presented in major software industry conferences for testing the performance of a certain CSS feature, that have a possibility to improve the performance of the website. The loading times obtained from the benchmarks are reviewed and compared with each other. In addition, a few techniques are presented that do not have their own benchmark, but which may have an effect on performance. To highlight the results, CSS performance is usually not the biggest bottleneck of performance on a website, since the overall style calculation takes about a quarter of the total runtime calculation on average. However, utilizing some particular techniques and managing to shrink the style calculation costs can be valuable. Based on the benchmarks on this research, using shadow DOM and scoped styles have a positive effect on style performance. For layout, performance benefits can be achieved by utilizing CSS containment and concurrent rendering. From other practices, it can be concluded that removing unused CSS, avoiding reflow and repaint along with complex selectors and considering the usage of web fonts a better results can be achieved in terms of performance.
-
(2022)Test automation has a crucial role in modern software development. Automated tests are immensely helpful in quality assurance, catching bugs and giving information on the state of the software. There are many existing frameworks that are designed to assist in creating automated tests. The frameworks can have massively varying purposes and targeted applications and technologies. In this paper, we aim to study a selected group of Behavior Driven Development (BDD) testing frameworks, compare them, identify their strengths and shortcomings, and implement our own testing framework to answer the discovered challenges. Finally, we will evaluate the resulting framework and see if it can meet its requirements. As a result we’ll have a better understanding in what kind of tools there are for automating behavior driven tests, what type of different approaches have been and can be taken to implement such frameworks, and what are the benefits and suitable uses of each tool.
-
(2023)Tutkimuksen kohteena oli lentoyhtiö Finnair. Finnair on tehnyt monia muutoksia IT-järjestelmiinsä ja johtamisessa viime vuosina. Vuoden 2020 lopussa kaikki palvelut siirrettiin AWSpilveen ja fyysisten palvelinkeskusten käytöstä luovuttiin. Tämä toimintamalli on parantanut IT-järjestelmien toimivuutta, koska pilvipalvelujen saatavuus ja käytettävyys on korkea. Silti järjestelmissä on ollut ongelmia, joiden syynä ovat olleet järjestelmätoimittajan ongelmat ohjelmiston kanssa. SIAM (Service Integration and Management) on lähestymistapa useiden palveluntarjoajien hallintaan ja niiden integroimiseen yhdeksi liiketoiminnalliseksi IT-organisaatioksi. SIAM tavoitteena on integroida saumattomasti erilaiset sisäiset ja ulkoiset palveluntarjoajat toisiinsa. SIAM on uusi termi IT-ympäristön hallinnasta. SIAM toiminnolle ei ole tarkkaa määritelmää, mutta yritykset voivat itse määritellä, kuinka käyttää sitä ympäristönsä kehittämiseen. SIAM on terminä niin uusi, ettei sille ole vielä löydettävissä parhaita käytäntöjä. SIAM toiminto voi olla yrityksen sisäinen toimintaa tai toimittajalta ostettua palvelua. Tutkimuksen kirjallisuuskatsauksessa perehdyttiin SIAM aiheiseen kirjallisuuteen ja verkkosivuihin. Tutkimuksessa havaittiin, että jonkin verran tieteellistä materiaalia oli saatavilla SIAM aiheesta. Näiden materiaalien pohjalta laadittiin yhteenveto, jota käytettiin tutkimuksen aikana. Kirjallinen aineisto auttoi tutkimuksen aikana ymmärtämään, miten määritellään SIAM toiminto. Näitä tietoja verrattiin tutkimushaastatteluissa kerättyihin tietoihin. Tutkimuksen lopuksi laadittiin selvitys kuinka hyvin SIAM toiminto saatiin käyttöönotettua Finnarilla. Arvioinnin perusteella laadittiin suosituksia jatkotoimenpiteistä ja suositus miten SIMA toimintoja tulisi edelleen kehittää.
-
(2022)Tässä tutkielmassa käydään läpi kirjallisuutta ja tutkimusta ohjelmistojen julkaisumenetelmistä sekä -tiheydestä niiden historiasta alkaen. Tarkemmin tutustutaan etenkin uusimpiin julkaisutiheyden lähestymistapoihin, jotka ovat jatkuva tuotantoonvienti (continuous deployment) ja jatkuva toimitus (continuous delivery). Tutkielmassa etsitään näiden lähestymistapojen käyttöönotosta odotettavissa olevia hyötyjä sekä ohjelmistotuotanto-organisaatioiden kokemuksia ja haasteita niihin siirryttäessä. Tutkielmassa etsitään myös ratkaisutapoja, joilla mahdollisia haasteita on lähestytty. Lisäksi pyritään pohtimaan esimerkiksi yrityksen toimialan, yrityksen tyypin ja muiden tekijöiden vaikutusta jatkuvan tuotantoonviennin ja toimituksen tarpeellisuuteen tai niistä saataviin hyötyihin. Kirjallisuuskatsauksen lisäksi tutkielmassa tehdään pienimuotoinen tapaustutkimus sähköisen taloushallinnon yrityksen pääohjelmistotuotteen julkaisutiheydestä ja sen tihentämisen mahdollisista menetelmistä ja odotuksista tutkielmassa löydetyn materiaalin pohjalta. Kirjallisuuskatsauksen perusteella alan kirjallisuudesta ja ohjelmistoyritysten kokemuksista saa joillain osa-alueilla yleisiä mallinnuksia ja ohjenuoria, joita tapaustutkimuksessakin tarkasteltu yritys voisi seurata mahdollisessa julkaisusyklin tihennyksessä. Jokaisen organisaation omakohtaisella kulttuurilla ja kypsyydellä on kuitenkin runsaasti merkitystä syklin tihennyksen onnistumisessa. Tarkastellun lähdemateriaalin pohjalta voidaan kuitenkin todeta, että epäonnistuneenakin pidetyn julkaisusyklin tihennysprojektin tuomat vaatimukset lisäävät helposti ohjelmisto-organisaation kuria ja sen tuotteiden kehitysprosessin laatua pysyvästi.
-
(2022)Verkon avulla tarjottavien rajapintojen käyttö ja niiden tarjoaminen kolmannen osapuolen käyttäjille on lisääntynyt sovelluskehityksessä viimevuosina suuresti. Mikropalveluarkkitehtuurin yleistyminen on osaltaan lisännyt sovelluksien hyödyntämien rajapintojen määrää merkittävästi ja luonut tarpeen työkaluille ja toimintatavoille, joilla kasvanutta rajapintojen määrää voidaan hallita ja ylläpitää tehokkaasti. Tämä tutkimus koostuu kahdesta erillisestä osasta. Ensimmäisessä osassa kartoitetaan kirjallisuuskatsauksen avulla API-hallinnan tavoitteita. Toisessa osassa tutustutaan tapaustutkimuksen avulla, kuinka kirjallisuuskatsauksessa tunnistettuja tavoitteita on toteutettu ja kuinka ne koetaan käytännön sovelluskehityksessä. Tutkielman keskeisenä tuloksena on joukko API-hallinnan tavoitteita ja käsitys siitä, kuinka niistä merkittävimmät ovat toteutettu tapausorganisaatioissa. API-hallinnan käytäntöjen lisäksi haastattelujen avulla selvitettiin, kuinka nämä käytännöt koetaan sovelluskehittäjien keskuudessa. Tuloksien perusteella API-hallinta voi lisätä sovelluskehittäjien työmäärää, mutta samalla se koetaan suurien organisaatioiden tuotteiden parissa lähes välttämättömänä toimintatapojen yhtenäistäjänä. Yhteenvetona tutkielman perusteella API-hallinta tarjoaa tarpeellisia työkaluja ja toimintatapoja rajapintojen kanssa työskentelyyn, kun rajapintoja on suuri määrä tai kun niitä tarjotaan organisaation ulkopuolisille sovelluskehittäjille. Käytännössä tapausorganisaatioiden rajapintojen hallinta on toteutettu vaihtelevin käytännöin eikä sitä koeta aivan pienessä organisaatiossa lähtökohtaisesti mielekkääksi.
-
(2022)The COVID-19 pandemic moved the work force to work from home (WFH). This is also true for the internal startup Toska, who started the development of a new course feedback system (CFS) during the pandemic. This thesis compares existing literature about lean software development (LSD) and remote working to the results gained from the interviews of the people who worked on the CFS. This thesis explores previous work on topics of lean software development, remote working and work from home during COVID-19. Developers and other personnel of the CFS project were interviewed to gain insight into how COVID-19 and remote working in general affected the project. After taking a look into previous work, the study design of the thesis is discussed after which the results gained from the interviews are analyzed. Finally the interview results are compared to the previous work to see if the CFS project produced similar results. At the end of the thesis the limitations and future work of the project are discussed. The results gained from the interviews indicate similiarities and differences between other studies which are discussed in the background chapter. Similarities include things such as the developers missing the face-to-face interactions with each other and the ability to have ad-hoc discussions around a whiteboard when discussing. The project was considered a success by everyone working on it and based on the results lean software development and remote working are tools that should be taken into consideration when discussing how to do a software development project. Remote working in most cases improves the work-life balance of people and lean software development methods help empower the development team.
-
(2022)Background: The splitting of functionality into multiple inter-communicating services has created a need for managing the APIs that these services are using to talk to each other. They also present an easy avenue for faults to be introduced into the system as these services are updated over time, especially in the absence of extensive testing, such as in rapid prototyping contexts. Aims: The study aimed to find a light-weight method for detecting API breakages between services, which requires as little manual labor from developers as possible. Method: The method used for the study was design science research focused around the iterative de- velopment and validation of the method through using it in synthetic and practical use-cases. Results: The study identified the possibility of using self-documenting services and machine- readable API documentation as a means to automatically detect API breakages either via naive or more complex approaches, with complex approaches providing more granular fault detec- tion and ability to create dependency graphs between services. Conclusion: Use of more automation seems a viable approach to detecting faults in network-based communication be- tween services. With further study, these approaches could be developed into developer-friendly systems, which allow not only automated fault detection, but also visual impact analysis for complex architectures spanning multiple services.
-
(2022)Tiedonhallinta on oleellinen osa nykypäivän tietotyötä, tämä maisterintutkielma tarkastelee tietojohtamisen ja tiedonhallinnan käsitteiden avulla projektinhallintaa. Projektinhallinta on käsitteenä laaja ja tässä työssä sitä tarkastellaan rakennushankkeiden johtamisen ja eri osapuolien tiedonhallinnan näkökulmasta. Rakennushanke koostuu useasta erilaisesta sidosryhmästä, joiden tavoitteena on yhteistoimin rakentaa ja tai korvata jotakin olemassa olevaa. Rakennushankkeissa tiedonhallinta on kriittistä, sillä päätöksillä on suoranainen vaikutus projektin onnistumiseen. Työ käsittelee datan mallinnuksen merkitystä sekä sen hyödyntämistä matalan kynnyksen ohjelmoinnissa, jonka hyödyntäminen yrityksissä on kasvanut viime vuosina merkittävästi. Työn tavoitteena on tutkia kuinka rakennushankkeiden tiedonhallintaa voisi kehittää rakennushankkeiden projektityöskentelyssä. Tavoitteena on tutkia, soveltuuko Microsoft Power Platform sekä Teams viestintä- ja yhteistyöalusta tietojohtamisen työkaluksi projektinhallintaan tiedonhallinnan näkökulmasta sekä voiko kyseisillä tuotteilla ratkaista eri toimijoiden yhteistoiminnan haasteita. Case esimerkkinä matalan kynnyksen ohjelmointiin liittyen tutkitaan erästä rakennushankkeiden johtamiseen liittyvää prosessia nimeltä työmaakokous. Työn tuloksena on havaittu, että tiedonhallinta sekä työssä tarkasteltu matalan kynnyksen ohjelmointialusta soveltuu rakennushankkeen projektinhallintaan tuoden läpinäkyvää tiedonhallintaa sekä hallittavuutta projekteihin.
-
(2023)The topic of API governance is important because of the ubiquity of cross-component interfaces in microservice systems. Tasks such as documenting interfaces manually can be a laborious and error-prone task, and the quality of said documentation can vary greatly. A large software system may also incorporate multiple protocols, programming languages, and development teams, further complicating the topic. Due to this, it is important to find ways to automate tasks such as this to ensure quality standards are met. In this thesis, we inspect the problems within the topic of API governance, and present the structure of an enterprise microservice application as a problem setting, and set out to design an automated system to handle parts of API governance. First, we set out the requirements of this system, after which we review literature and technological solutions on the subject. After these, we present two approaches for achieving the design goals, and develop a proof-of-concept implementing parts of one of the designs. While the presented designs remain abstract in some areas, they can act as starting points for future research and development.
-
(2022)Tässä tutkielmassa käsitellään sovellusten huoltovarmuutta: tutkimuksen kohteena oli Yleisradio Oy:n verkkouutiset, eli Uutisvahti– ja Yle–sovellukset, sekä yle.fi–verkkosivusto. Tutkimuksessa selvitettiin, onko verkkouutiset tärkeä viestintäväline viranomaisviestinnässä. Lisäksi selvitettiin, miten huoltovarmuus toteutuu Yleisradion verkkouutisissa. Tulosten perusteella verkkouutiset on tärkeä väline viranomaisviestinnässä. Lisäksi verkkouutisten huoltovarmuus on tulosten perusteella pääosin hyvällä tasolla. Suurin uhkatekijä verkkouutisten huoltovarmuudelle on riippuvuus ulkomaailman internet–yhteyksistä sekä kolmansien osapuolien pilvipalveluista.
-
(2022)Legacy software systems, which refers to old and likely outdated software applications and practices, are a reality that most software development companies have to contend with. Old practices and technologies are often at fault for slowing down development and deployment of software, as they can have compatibility, security, scalability and economic issues with their continued use, among other issues. Software modernization, reengineering and refactoring can alleviate the issues stemming from legacy systems, whether it be in the form of altering practices, updating technologies or changing platforms. There are many technologies and methods that can facilitate the modernization of a software system, including a move to using different architectures, specific newer technologies and changing the methods of working and developing the software system. These technologies and methods, and modernization in general, come with their own risks and challenges that must be considered for a successful modernization to take place; These strategic considerations are a key factor in modernization. This thesis will explore software modernization in general through literature reviews and as a case study for a specific company using data from surveys and the case company’s logs, with a look into the technologies, concepts and strategies required for a successful modernization, and what kinds of effects modernization can have on the software system being modernized, both from a user perspective as well as from a developer perspective. The end-result of this exploration reveals that modernization is a complex subject with many challenges, but that also offers benefits to the software system being modernized. These results are best used as a guideline on what issues should be concentrated on during modernization, with a mindful consideration for the limited scope of the case study represented within.
Now showing items 21-40 of 57