A5025579659- Software Engineering Research
- Software Engineering Techniques and Practices
- Open Source Software Innovations
- Software Reliability and Analysis Research
- Software System Performance and Reliability
- Data Visualization and Analytics
- Big Data and Business Intelligence
- Advanced Software Engineering Methodologies
- Scientific Computing and Data Management
- ERP Systems Implementation and Impact
- Business Process Modeling and Analysis
- Service-Oriented Architecture and Web Services
- Advanced Text Analysis Techniques
- Construction Project Management and Performance
- Data Quality and Management
- Risk and Safety Analysis
- Cloud Computing and Resource Management
- Educational Reforms and Innovations
- Educational Robotics and Engineering
- Problem and Project Based Learning
- Business and Management Studies
- Web Data Mining and Analysis
- FinTech, Crowdfunding, Digital Finance
- Private Equity and Venture Capital
- Mobile Crowdsensing and Crowdsourcing
Universidade Federal da Bahia
2015-2024
Hospital Ana Nery
2019-2024
Instituto Federal da Bahia
2015-2020
Issues Research
2019
Universidade do Estado da Bahia
2010-2018
Universidade Salvador
2000-2018
Instituto Federal de Educação, Ciência e Tecnologia de Sergipe
2018
Universidade Federal de Sergipe
2018
Fraunhofer USA
2001-2016
University of Maryland, College Park
1998-2009
The software engineering research community has been adopting systematic reviews as an unbiased and fair way to assess a topic. Despite encouraging early results, review process can be time consuming hard conduct. Thus, tools that help on its planning or execution are needed. This article suggests the use of Visual Text Mining (VTM) aid reviews. A feasibility study was conducted comparing proposed approach with manual process. We observed VTM contribute Systematic Review we propose new...
Recently the awareness of importance replicating studies has been growing in empirical software engineering community. The results any one study cannot simply be extrapolated to all environments because there are many uncontrollable sources variation between different environments. In our work, we have reasoned that availability laboratory packages for experiments can encourage better replications and complementary studies. However, even with effectively specified packages, transfer...
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...
Code smells are anomalies often caused by the way concerns realized in source code. Their identification might depend on properties governing structure of individual and their inter-dependencies system implementation. Although code visualization tools increasingly applied to support anomaly detection, they mostly limited represent modular structures, such as methods, classes packages. This paper presents a multiple views approach that enriches four categories with concern properties, namely:...
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,...
Psychological safety is essential for high-performing software teams. It allows team members to feel comfortable taking risks, asking questions, and sharing feedback. This paper identifies everyday interpersonal challenges that point a lack of psychological in development practices, such as reluctance admit mistakes, avoiding seeking help, fear negative Our study suggests critical meeting practices can be better managed promote more supportive healthy environment.
Software organizations are in need of methods to understand, structure, and improve the data their collecting. We have developed an approach for use when a large number diverse metrics already being collected by software organization (M.G. Mendonca et al., 1998; M.G. Mendonca, 1997). The combines two methods. One looks at organization's measurement framework top-down goal-oriented fashion other it bottom-up data-driven fashion. method is based on paradigm called Goal-Question-Metric (GQM)....
Experimental replications are very important to the advancement of empirical software engineering. Replications one key mechanisms confirm previous experimental findings. They also used transfer knowledge, train people, and expand a base evidence. Unfortunately, difficult endeavors. It is not easy know-how Based on our experience, this paper discusses problem proposes Framework for Improving Replication Experiments (FIRE). The FIRE addresses knowledge sharing issues both at intra-group...
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...
Context . Technical debt (TD) prevention allows software practitioners to apply practices avoid potential TD items in their projects. Aims To uncover and prioritize, from the point of view practitioners, that could be used items, relations between these causes TD, practice avoidance reasons (PARs) explain failure prevent TD. Method We analyze data collected six replications a global industrial family surveys on totaling 653 answers. also conducted follow up survey understand importance level...
Folklore and beliefs are strong in the software practitioners' community. Software engineering is a communication intensive activity. engineers innovation driven regularly use automated resources to share ideas, new paradigms approaches support improve their practices. This information flow generates technical folklore (that do not have formal trial basis). applying practices influenced by these they inevitably taken on board adoption of particular technology or practice. paper presents an...
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...