A5020235955- Software Engineering Techniques and Practices
- Software Engineering Research
- Open Source Software Innovations
- Software Reliability and Analysis Research
- Big Data and Business Intelligence
- Advanced Software Engineering Methodologies
- ERP Systems Implementation and Impact
- Software System Performance and Reliability
- Business Process Modeling and Analysis
- Service-Oriented Architecture and Web Services
- Construction Project Management and Performance
- Technology Assessment and Management
- Educational Robotics and Engineering
- Context-Aware Activity Recognition Systems
- Educational Reforms and Innovations
- Private Equity and Venture Capital
- FinTech, Crowdfunding, Digital Finance
- Mobile and Web Applications
- Problem and Project Based Learning
- Cloud Computing and Resource Management
- Outsourcing and Supply Chain Management
- IoT and Edge/Fog Computing
- Semantic Web and Ontologies
- Green IT and Sustainability
- AI in Service Interactions
Virginia Commonwealth University
2022-2024
Universidade Salvador
2014-2023
The University of Melbourne
2023
Drexel University
2023
Huawei Technologies (China)
2023
University of Saskatchewan
2023
Shinshu University
2023
Ōtani University
2023
Universidade do Estado da Bahia
2018-2022
Universidade Federal da Bahia
2015-2022
Context: The technical debt (TD) concept describes a tradeoff between short-term and long-term goals in software development. While it is highly useful as metaphor, has utility beyond the facilitation of discussion, to inspire set methods tools that support identification, measurement, monitoring, management, payment TD. Objective: This study focuses on identification We evaluate human elicitation TD compare automated identification. Method: asked development team identify items artifacts...
Technical debt is a term that has been used to describe the increased cost of changing or maintaining system due shortcuts taken during its development. As technical recent research area, different types and their indicators are not organized yet. Therefore, this paper proposes an ontology terms on in order organize common vocabulary for area. The concepts derived from results systematic literature mapping. proposed was evaluated two steps. In first one, some design quality criteria were...
Requirements Engineering (RE) has established itself as a software engineering discipline during the past decades. While researchers have been investigating RE with plethora of empirical studies, attempts to systematically derive an empirically-based theory in context just recently started. However, such is needed if we are define and motivate guidance performing high quality research practice. We aim at providing valid foundation for RE, which helps engineers establish effective efficient...
Context: Contemporary software development is typically conducted in dynamic, resource-scarce environments that are prone to the accumulation of technical debt. While this general phenomenon acknowledged, what remains unknown how debt specifically manifests and affects processes, techniques employed accommodate or mitigate presence Objectives: We sought draw on practitioner insights experiences order classify effects agile method use management, given popularity perceived success methods....
The identification of technical debt (TD) is an important step to effectively manage it. In this context, a set indicators has been used by automated approaches identify TD items, but some may not be directly identified using only metrics collected from the source code. work we propose CVM-TD, model support through code comment analysis. We performed exploratory study on two large open sources projects with goal characterizing feasibility proposed detection comments results indicate that (1)...
Background: The presence of technical debt (TD) brings risks to a software project and makes it difficult manage. Several TD management strategies have been proposed, but considering actions that could explicitly prevent the insertion in first place monitor its effects is not yet common practice. Thus, while an important topic, also worthwhile understand causes lead development teams incur different types as well their on projects. Aims: objective this work twofold. First, we investigate...
Understanding TD causes can support development teams in defining actions that could be taken to prevent the occurrence of debt items. effects aid prioritization items pay off minimize possible negative consequences for project. Existing work has revealed 105 and 85 TD, this high number make it difficult practical use information. Without a consolidated representation, we would need rely on set tables isolated pieces data. In work, propose cross-company probabilistic cause-effect diagrams...
Background: Little is known about the practices used for technical debt (TD) payment. The study of payment practices, as well reasons not applying them, can help practitioners to control and manage TD items. Aims: To investigate, from point view software practitioners, if items have been paid off in projects, that pay hamper implementation these practices. Method: We analyzed - both quantitatively qualitatively a corpus responses survey 432 four countries, possibility Results: found that,...
We identified and organized a number of statements about technical debt (TD Folklore list) expressed by practitioners in online websites, blogs published papers. chose 14 we evaluated them through two surveys (37 answered the questionnaires), ranking agreement consensus. The most agreed with show that TD is an important factor software project management not simply another term for bad code. This study will help research community identifying folklore can be translated into questions to...
Background: Software repositories provide large amount of data encompassing software changes throughout its evolution. Those can be effectively used to extract and analyze pertinent information derive conclusions related the history or current snapshot. Objective: This work aims investigate recent studies on Mining Repositories (MSR) approaches collecting evidences about analysis goals (purpose, focus, object analysis), sources, evaluation methods, tools, how area is evolving. Method: A...
We identified and organized a number of statements about technical debt (TD Folklore list) expressed by practitioners in online websites, blogs published papers. chose 14 we evaluated them through two surveys (37 answered the questionnaires), ranking agreement consensus. The most agreed with show that TD is an important factor software project management not simply another term for "bad code". This study will help research community identifying folklore can be translated into questions to...
As part of the Naming Pain in Requirements Engineering (NaPiRE) initiative, researchers compared problems that companies Brazil and Germany encountered during requirements engineering (RE). The key takeaway was RE, human interaction is necessary for eliciting specifying high-quality requirements, regardless country, project type, or company size.
The term Technical Debt (TD) is used to describe the debt that a development team incurs when it takes shortcuts in software process, but may increase complexity and maintenance cost long-term. If does not manage TD, this can cause significant long-term problems such as high costs. An important goal of management evaluate appropriate time pay TD item effectively apply decision-making criteria balance short-term benefits against However, although there are different studies have proposed...
Background: Preventing the occurrence of technical debt (TD) in software projects can be cheaper than its payment. Prevention practices also help catching inexperienced developers' 'not-so-good' solutions. However, little is known on how to prevent TD. Aims: To investigate, from point view practitioners, preventive actions that used curb TD and impediments hamper use those actions. Method: We data InsighTD Project, a family industrial surveys specifically designed study engineering corpus...