Sökning: "Code Smells"

Visar resultat 1 - 5 av 14 uppsatser innehållade orden Code Smells.

  1. 1. MLpylint: Automating the Identification of Machine Learning-Specific Code Smells

    Master-uppsats, Blekinge Tekniska Högskola/Institutionen för programvaruteknik

    Författare :Peter Hamfelt; [2023]
    Nyckelord :Code Smell; Machine Learning; Static Code Analysis; Software Quality; Technical Debt;

    Sammanfattning : Background. Machine learning (ML) has rapidly grown in popularity, becoming a vital part of many industries. This swift expansion has brought about new challenges to technical debt, maintainability and the general software quality of ML systems. LÄS MER

  2. 2. Analysis of Code Smells and Anomalies in Modern Web Software

    Kandidat-uppsats, Blekinge Tekniska Högskola/Institutionen för programvaruteknik

    Författare :Elias Cherkaoui; [2023]
    Nyckelord :Code anomalies; smells; refactoring;

    Sammanfattning : Code anomalies, also known as code smells, are any characteristics in software code that indicate amore severe problem exists deep in the code. These anomalies do not always prevent a system fromfunctioning, but they can restrict development and increase the difficulty of maintaining the software. LÄS MER

  3. 3. Code smells in machine learning pipelines: an MSR sample study

    Kandidat-uppsats, Göteborgs universitet/Institutionen för data- och informationsteknik

    Författare :Johann Henri Tammen; [2022-12-22]
    Nyckelord :technical debt; code smells; machine learning; data science;

    Sammanfattning : As technical debt in software engineering projects continues to negatively impact the development process, this study focuses on technical debt in form of code smells in machine learning pipelines and in code written by data scientists. This study contributes to the body of knowledge on technical debt as it tries to quantify the assumption in the literature that scientists without a software engineering background struggle with software engineering’s best practices when writing code. LÄS MER

  4. 4. Non-deterministic tests and where to find them : Empirically investigating the relationship between flaky tests and test smells by examining test order dependency

    Kandidat-uppsats, Linköpings universitet/Institutionen för datavetenskap

    Författare :Sokrates Lamprou; [2022]
    Nyckelord :flaky tests; continuous integration; regression tests; test order dependency;

    Sammanfattning : Flaky tests are non-deterministic tests that both pass and fail when no new code changes have been introduced to the code under test. This is a widespread problem for the Continuous Integration community where the underlying idea is that code is only integrated if all test cases pass. LÄS MER

  5. 5. Clean Code in Practice : Developers´ perception of clean code

    Kandidat-uppsats, Blekinge Tekniska Högskola/Institutionen för programvaruteknik

    Författare :Kevin Ljung; [2021]
    Nyckelord :clean code; code quality; technical debt; refactoring;

    Sammanfattning : Context. There is a need for developers to write clean code and code that adheres to a high-quality standard. We need developers not to introduce technical debt and code smells to the code. LÄS MER