Vladimir MandićUniversity of Novi Sad · Department of Industrial Engineering and Engineering Management
Vladimir Mandić
PhD - Software Engineering
About
37
Publications
7,298
Reads
How we measure 'reads'
A 'read' is counted each time someone views a publication summary (such as the title, abstract, and list of authors), clicks on a figure, or views or downloads the full-text. Learn more
181
Citations
Citations since 2017
Introduction
Vladimir Mandic currently works at the Department of Industrial Engineering and Engineering Management, University of Novi Sad. Vladimir does research in Computer Engineering, Empirical Software Engineering, and Information Systems.
Additional affiliations
September 2011 - April 2012
January 2008 - September 2012
Education
January 2008 - September 2012
Publications
Publications (37)
Context: The presence of technical debt (TD) brings risks to software projects. Managers must continuously find a cost-benefit balance between the benefits of incurring in TD and the costs of its presence in a software project. Much attention has been given to TD related to coding issues, but other types of debt can also have impactful consequences...
Context: Advances in technical debt research demonstrate the benefits of applying the financial debt metaphor to support decision-making in software development activities. Although decision-making during requirements engineering has significant consequences, the debt metaphor in requirements engineering is inadequately explored. Objective: We aim...
Context
Technical debt (TD) payment refers to the activity of expending maintenance effort and resources to make up for the effects of previous technical compromises.
Aims
To investigate if software practitioners have paid debt items off in their projects, the practices that have been used for paying off debt items, and the issues that hamper the...
Commonly, software developers are faced with situations to compromise internal quality to achieve short term goals, e.g. time-to-market. In software engineering, such compromises are described with Technical Debt (TD) concept. TD implies cost of additional rework—usually expressed as effort—and when the code is compromised, it is called code debt....
Context: Advances in technical debt research demonstrate the benefits of applying the financial debt metaphor to support decision-making in software development activities. Although decision-making during requirements engineering has significant consequences, the debt metaphor in requirements engineering is inadequately explored. Objective: We aim...
Context: It is common for a software project to incur technical debt (TD) during its development. It can impact several artifacts produced throughout the software development process. Therefore, it is necessary to carry out management actions to find a balance between the benefits of incurring it and the effects of its presence. However, so far, mu...
This article presents technical debt (TD) impediments, decision factors, enabling practices, and actions diagrams for TD management in agile software projects. By analyzing diagrams, professionals can avoid the pitfalls, and increase their capacity, for better TD management.
Context
The technical debt (TD) metaphor describes actions made during various stages of software development that lead to a more costly future regarding system maintenance and evolution. According to recent studies, on average 25% of development effort is spent, i.e. wasted, on TD caused issues in software development organizations. However, furth...
The technical debt (TD) metaphor describes actions made during various stages of software development that lead to a more costly future regarding system maintenance and evolution. According to recent studies, on average 25% of development effort is spent, i.e. wasted, on TD caused issues in software development organizations. However, further resea...
Desiderata is a general term for stakeholder needs, desires or preferences. Recent experiments demonstrate that presenting desiderata as templated requirements specifications leads to less creative solutions. However, these experiments do not establish how the presentation of desiderata affects design creativity. This study, therefore, aims to expl...
Technical Debt (TD) can be injected at any stage of software development. Once injected, TD rarely remains contained and spreads across other stages causing various problems. During software development, technical and non-technical roles need to cooperate and communicate complex issues to implement optimal solutions. This article presents a model f...
Context
Test-driven development (TDD) is an agile software development approach that has been widely claimed to improve software quality. However, the extent to which TDD improves quality appears to be largely dependent upon the characteristics of the study in which it is evaluated (e.g., the research method, participant type, programming environme...
Context: Test-driven development (TDD) is an agile software development approach that has been widely claimed to improve software quality. However, the extent to which TDD improves quality appears to be largely dependent upon the characteristics of the study in which it is evaluated (e.g., the research method, participant type, programming environm...
Technical debt (TD), as a metaphor for utilizing quick workarounds to achieve short-term wins, is gaining attention in academia and industry. However , little is known about how companies pay off the accumulated TD, or why they chose to avoid this payment. The goal of this research was set to address this knowledge gap by gaining insight on TD paym...
Software developers commonly faced with situations to compromise internal quality ta=hat achieve short term goals, e.g. time-to-market. In software engineering, such compromises are described with Technical Debt (TD) concept. TD implies cost of additional rework-usually expressed as effort-and when the code is compromised, it is called code debt. O...
Background. Software engineering is one of the engineering fields with the highest inflow of junior engineers. Tools that utilize source code analysis to provide feedback on internal software quality, i.e. Technical Debt (TD), are valuable to junior developers who can learn and improve their coding skills with minimal consultations with senior coll...
Background: The concept of technical debt (TD) describes a phenomenon that impacts software projects and makes them difficult to manage. In recent years, various techniques and best practices in terms of TD management were proposed and although important on its own this knowledge must be complemented with a broader comprehension of what causes TD a...
Background: There is a growing body of knowledge on Technical Debt (TD) in recent years. This knowledge provides various explanations of the term and suggests different remedies for it. However, the knowledge is yet to be validated in software development
processes. Aims: The objective of this study is twofold. First, to get empirical insight on th...
Desiderata is a general term for stakeholder needs, desires or preferences. Recent experiments demonstrate that
presenting desiderata as formal requirements specifications leads to less creative solutions. However, these experiments do not
establish how the presentation of desiderata affects design creativity. This study, therefore, aims to explore...
As software trends go, in recent years, cloud technologies have become increasingly popular. Thanks to cloud technologies, nowadays software solutions can be developed and deployed in significantly shorter time cycles. These solutions usually rely on some services to do the heavy lifting and processing of the data. At the other hand, microservices...
Replications are an integral component of experimentation through which the validity and reliability of the observed outcome in a previous experiment can be probed. In a strict replication, the experiment is executed in the same conditions as the original by following the same protocol and thus the evidence is strengthened statistically by means of...
Nowadays, agile approaches are becoming the mainstream paradigm for organizing the software
development teams. However, in practice, some aspects of the agility of software development, e.g.
the speed of development, scalability, reusability, and modularity are constrained or diminished due to
the software product design itself or because of the in...
Context: Successful organizations need to manage and synchronize their strategic objectives with daily operations and activities. In general, achieving that requires a continuous process of organizational alignment. GQM⁺Strategies is an approach that helps software organizations with documenting and aligning organizational goals and strategies, and...
Nowadays, the software industry has at its disposal several approaches that accentuate the concept of value, e.g., lean or agile software development. However, our experience has shown that arriving at an understanding of what is meant by value in a given organizational context presents real challenges. And, one of the reasons for having those chal...
Business value analysis (BVA) quantifies the factors that provide value and cost to an organization. It aims at capturing value, controlling risks, and capitalizing on opportunities. GQM+Strategies is an approach designed to aid in the definition and alignment of business goals, strategies, and an integrated measurement program at all levels in the...
In this paper, we offer an approach for performing an organization-wide earned value analysis by taking advantage of the hierarchical structure of the GQM+Strategies grid. The merger enables us to create an integrated hierarchy of business goals, value goals, and strategies for achieving those goals and to monitor and evaluate those goals at all le...
GQM+Strategies is an approach designed to help the software industry develop measurement programs that are aligned with business
goals. The resulting structure, which aligns metrics (GQM goals) and business goals, is called a grid. Usefulness (quality)
of the grids depends on how well the environment is characterized by the grid elements. Our resea...
The success of a measurement initiative in a software company depends on the quality of the links between metrics programs
and organizational business goals. GQM+Strategies is a new approach designed to help in establishing links between the organizational business goals and measurement
programs. However, there are no reported industrial experience...
The main concern of the software industry is to deliver more products in shorter time-cycles to customers with an acceptable
economic justification. In virtue of these concerns, the software industry and researchers in the field of software engineering
have engaged in the process of adopting lean principles. In this paper, we are seeking the knowl...
Most of today's products and services are software-based. Organizations that develop software want to maintain and improve their competitiveness by controlling software-related risks. To do this, they need to align their business goals with software development strategies and translate them into quantitative project management. There is also an inc...
This paper presents results of a literature analysis on Empirical Research Approaches in Software Engineering (SE). The analysis
explores reasons why traditional methods, such as statistical hypothesis testing and experiment replication are weakly utilized
in the field of SE. It appears that basic assumptions and preconditions of the traditional me...
We offer an approach for performing organization earned value analysis by taking advantage of the hierarchical structure of the GQM + Strategies grid. The merger enables us to create an integrated hierarchy of business goals, value goals, and strategies for achieving those goals and to monitor and evaluate those goals at all levels. It provides a m...
Business value analysis (BVA) quantifies the factors that provide value and cost to an organization. It aims at capturing value, controlling risks, and capitalizing on opportunities. GQM + Strategies is an approach designed to aid in the definition and alignment of business goals, strategies, and an integrated measurement pro-gram at all levels in...
Projects
Projects (4)
InsighTD is a globally distributed family of industrial surveys on TD. Its goal is to investigate the state of practice and industry trends in the TD area including the status quo, the causes that lead to TD occurrence, the effects of its existence, how these problems manifest themselves in the software development process, and how software development teams react when they are aware of the presence of debt items in their projects.
InsighTD has been planned cooperatively with several TD researchers. It is designed to run as an incremental large scale study based on continuous and independent replications of the questionnaire in different countries. Currently, researchers from 10 countries (visit the Project Team web page) have already joined the initiative.
By replicating the survey, we will incrementally put together data about practical problems of TD considering different development cultures, organization sizes, development methodologies, and so on. Each replication can bring several findings to the area. Further, the combination of data from different locations can shed some light on possible differences or similarities regarding perceptions of TD in specific development cultures.
Our goal is to help both practitioners and researchers to better understand possible causes and effects of TD (Technical Debt) presence in software projects. The collected information will lay the foundation for identifying practically relevant problems in the TD area. Through the cooperation with practitioners and industry at national level (Serbia) we are contributing to the InsighTD global initiative (http://td-survey.com/).
