Wyniki wyszukiwania - BazTech

1

Technical debt prioritization in telecommunication applications – why the actual refactoring deviates from the plan and how to remediate it?

Stochel Marek G., Chołda Piotr, Wawrowski Mariusz R.

Przegląd Telekomunikacyjny + Wiadomości Telekomunikacyjne

|

2022

|

nr 4

151--155

EN

This paper focuses on application of technical debt prioritization technique to the telecommunication software managing the fleet of devices for a video surveillance system. Technical debt for this application was gathered, categorized and prioritized according to the approach named CoDVA. However, the implementation of technical debt reduction did not follow exactly the expected guidelines. The three main causes of this phenomenon were discovered: continuous refactoring approach, sizing of technical debt items, and the broadened scope of refactoring activities. Therefore, we propose to adopt a specific definition of technical debt and follow a few rules for defining its scope and granularity.

2

Conceptualisation of using technical debt to measure the innovation level of new product – selected issues

Paweł Filipowicz

Zeszyty Naukowe. Organizacja i Zarządzanie / Politechnika Śląska

|

2021

|

z. 153

89--101

EN

Purpose: Conceptualisation of the technical debt use as the new product innovativeness measure. Design/methodology/approach: This paper adopts the J. Highsmith perspective on the technical debt as the essential of agile project management. The presented customer centered perspective of product value allows to use the technical debt as base for the new product innovativeness parametrization. The presented approach is possible also with the behavioral conception of innovativeness being directly associated with the subjective customer perception and works to build theory accordingly. The research is entirely theoretical and uses two points of reference. The first was used to explore the possible use of the technical debt as innovativeness measure through the use of user function. The second, consisting of presentation the possible modification of F. Sgobbi value model as the management tool for analyzing the value of new technology based product. Findings: The Concept of technical debt use as the measure of technology value is presented. Research limitations/implications: Future research sugestions will concerne the discretization of presented concept. Practical implications: The Presented conception may became the an interestning base for analyse and assesement of innovatives products and also in this way it can be used for new management tool designing, particulary in the domain of value based management process. Originality/value: Elaboration and operationalization of new technology based products model development with application of technology life cycle.

3

Technical Debt Aware Estimations in Software Engineering: a Systematic Mapping Study

Klimczyk Paweł, Madeyski Lech

e-Informatica Software Engineering Journal

|

2020

|

Vol. 14, nr 1

61--76

EN

Context: The Technical Debt metaphor has grown in popularity. More software is being created and has to be maintained. Agile methodologies, in particular Scrum, are widely used by development teams around the world. Estimation is an often practised step in sprint planning. The subject matter of this paper is the impact technical debt has on estimations. Objective: The goal of this research is to identify estimation problems and their solutions due to previously introduced technical debt in software projects. Method: The Systematic mapping study (SMS) method was applied in the research. Papers were selected from the popular digital databases (IEEE, ACM, Scopus, etc.) using defined search criteria. Afterwards, a snowballing procedure was performed and the final publication set was filtered using inclusion/exclusion criteria. Results: 42 studies were selected and evaluated. Five categories of problems and seven proposed solutions to the problems have been extracted from the papers. Problems include items related to business perspective (delivery pressure or lack of technical debt understanding by business decision-makers) and technical perspective (difficulties in forecasting architectural technical debt impact or limits of source code analysis). Solutions were categorized in: more sophisticated decision-making tools for business managers, better tools for estimation support and technical debt management tools on an architectural-level, portfolio approach to technical debt, code audit and technical debt reduction routine conducted every sprint. Conclusion: The results of this mapping study can help taking the appropriate approach in technical debt mitigation in organizations. However, the outcome of the conducted research shows that the problem of measuring technical debt impact on estimations has not yet been solved. We propose several directions for further investigation. In particular, we would focus on more sophisticated decision-making tools.

4

Dług technologiczny jako narzędzie optymalizacji procesu zarządzania innowacjami

Filipowicz P.

Zeszyty Naukowe. Organizacja i Zarządzanie / Politechnika Śląska

|

2015

|

z. 83

153--163

PL

Koncepcja długu technologicznego organizacji wywodzi się z praktyki zarządzania długiem technicznym w sektorze IT. Jej zastosowanie w procesie zarządzania przedsiębiorstwem może umożliwić określenie obszaru optymalizacji procesów organizacyjnych, kluczowych dla skutecznej komercjalizacji produktów opartych na rozwoju innowacyjnym.

EN

Organization technological debt conception is derived from the IT sector management process practice. Its generalization and application in the company management process could be helpful for key organization process optimization, which is particular important for innovation based product effective commercialization.