Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey

•Download as PPTX, PDF•

0 likes•282 views

This document summarizes preliminary results from an exploratory survey about factors that influence the longevity of code smells. The survey found that duplicated code and long methods were the most recurring smells. Refactoring habits varied depending on the nature of the software, with reusable asset developers more cautious about refactoring due to risks of breaking APIs. Respondents also noted difficulties with testing behavior preservation after refactoring and limitations of refactoring tools.

Technology

Understanding the Longevity of Code SmellsPreliminary Results of an Exploratory Survey Roberta Arcoverde – rarcoverde@inf.puc-rio.br Alessandro Garcia – afgarcia@inf.puc-rio.br Eduardo Figueiredo – figueiredo@dcc.ufmg.br ICSE.11

why? May 11 Roberta @ OPUS Group 2 codesmellsentailevidenceofbadqualitycode harder to readandmaintain some [patternsof] smellsseem to be “ignored”

why? May 11 Roberta @ OPUS Group 3 codesmellsentailevidenceofbadqualitycode harder to readandmaintain some [patternsof] smellsseem to be “ignored”  [1] How we refactor and how we know it. Murphy-Hill et al. [ICSE 2010]

objective May 11 Roberta @ OPUS Group 4 perform a firstexploratorystudy to identify which factors influence longevity of code smells, based on refactoring habits

refactoring habits howoftencode is refactored? which refactorings are prioritized? is refactoringapplied as anisolateactivity? which refactorings are considered to beharder to apply? howoftenandwhenrefactoringtools are used? May 11 Roberta @ OPUS Group 5

which factors influence refactoring habits natureof software beingdeveloped reusableassets (frameworks, libraries, software productlines) standalone applications use of TDD developer’sexperience May 11 Roberta @ OPUS Group 6

survey setting - questionnaire May 11 Roberta @ OPUS Group 7

participants May 11 Roberta @ OPUS Group 8 agiledevelopmentteams framework developers = 33 answers

participants distribution May 11 Roberta @ OPUS Group 9

participants distribution - TDD May 11 Roberta @ OPUS Group 10

most recurring smells May 11 Roberta @ OPUS Group 11 duplicated code – 78% (26) long methods – 78% (26) inadequate naming – 69% (23) god classes – 42% (14) same results for developers of reusable assets and standalone applications... ...regardless of experience level

how often refactoring tools are used... May 11 Roberta @ OPUS Group 12

...and reasons for not using them May 11 Roberta @ OPUS Group 13 tool does notsupportthedesiredrefactoring – 41% theydidnotknowanyrefactoringtool – 37% tools do notallowthem to easilyfollowtheeffectsofrefactoring – 28% it’snoteasy to testwhetherthesystem’sbehaviourwaspreserved – 22%

classifying refactorings - difficulty May 11 Roberta @ OPUS Group 14

concluding remarks May 11 15 Roberta @ OPUS Group nature of the software being developed influences refactoring habits reusable assets developers consider the possibility of breaking APIs before refactoring refactoring prioritization is fairly different when we consider reusable assets versus standalone applications refactoring scope is considered

concluding remarks visualizationmechanismsimprovements are needed testingwhetherthecodetransformationpreservedbehaviour is noteasy specifictoolsorfeaturescouldbeinvestigated for refactorings oflibraries, frameworks and software productlines May 11 Roberta @ OPUS Group 16

thank you questions? May 11 Roberta @ OPUS Group 17

classifying refactorings - priority May 11 Roberta @ OPUS Group 18

classifying refactorings - frequency May 11 Roberta @ OPUS Group 19

This document proposes a technical debt management framework based on cost-benefit analysis (CoBeTDM). It discusses identifying technical debt using metrics, prioritizing debt repayment using a cost-benefit analysis to determine which issues provide the best return on investment, and using a meta-model to track debt over time. Examples are provided of identifying a debt item, assessing its costs and benefits, and prioritizing repayment. Open questions on monitoring and thresholds are also discussed, as well as plans for future work validating the approach with historical data and developing management tools.

Prioritization of Code Anomalies Based on Architecture Sensitiveness

roberta arcoverde

The document discusses research into prioritizing code anomalies based on their impact on software architecture. Several heuristics for detecting architecturally relevant code anomalies are proposed, including change-proneness, error-proneness, anomaly density, and architecture role. The heuristics are evaluated on four systems by comparing the ranked anomalies to a ground truth of known architecture problems. The evaluations found that the heuristics could correctly identify architecturally relevant anomalies between 75-85% of the time by highlighting groups of classes that change together or contain similar anomalies. Future work is proposed to better evaluate heuristic combinations and their ability to improve refactoring effectiveness.

Bright talk if they cant use it, it doesnt work - final

Andrew White

The document discusses how latency and poor user experience can negatively impact systems in the cloud. It emphasizes the importance of monitoring from an end-user perspective to identify sources of latency. The key is to continually monitor all parts of the system, including individual transactions, infrastructure components, and end-user experience to drive the right actions that improve performance and optimize systems deployed in the cloud.

Personalized Defect Prediction

Sung Kim

Personalized defect prediction models can more accurately predict buggy changes. The researchers propose two personalized approaches: 1) Personalized Change Classification (PCC) trains a separate model for each developer using their change history. 2) Confidence-based Hybrid PCC (PCC+) combines the predictions from the CC and PCC models, selecting the one with the highest confidence. The approaches were evaluated on six projects, finding up to 155 more bugs by inspecting only 20% of code locations compared to non-personalized models. PCC and PCC+ consistently outperformed the baseline across different settings, demonstrating the benefits of personalization.

On the Relevance of Code Anomalies for Identifying Architecture Degradation S...

roberta arcoverde

The document analyzes the relationship between code anomalies and architecture degradation in software systems. It studies this relationship across multiple systems and revisions to answer three questions: 1) Are anomalous code elements related to architecture problems? 2) Which characteristics of code anomalies are relevant for architecture? 3) Did refactorings address architecturally-relevant code anomalies? The study collected data on code anomalies, architecture problems, and refactorings. Statistical tests found that code anomalies were related to architecture problems in 77.5% of versions analyzed. Further analysis identified which specific anomalies and characteristics caused architecture problems.

Code Smell Research: History and Future Directions

Nikolaos Tsantalis

This document discusses the history and future directions of code smell research. It covers the origins of refactoring and code smells, definitions of various code smells, methods for identifying code smells, prioritizing refactoring opportunities based on risk analysis, and the need to consider refactoring dependencies and conflicts. The goal is to improve software maintainability and quality through addressing code smells.

MSR2013

Norihiro Yoshida

This document describes two datasets for analyzing open source software code review processes. The datasets contain information about who submits and reviews code patches, the types of roles reviewers perform, review activity metrics, and reviewer statistics. Example applications include social network analysis of collaboration between reviewers and analyzing how reviewers' roles relate to privileges like testing code. The datasets are available online and are aimed to provide more detailed information about reviewers compared to downloading full review repository JSON files.

Code smells represent symptoms of poor implementation choices. Previous studies found that these smells make source code more difficult to maintain, possibly also increasing its fault-proneness. There are several approaches that identify smells based on code analysis techniques. However, we observe that many code smells are intrinsically characterized by how code elements change over time. Thus, relying solely on structural information may not be sufficient to detect all the smells accurately. We propose an approach to detect five different code smells, namely Divergent Change, Shotgun Surgery, Parallel Inheritance, Blob, and Feature Envy, by exploiting change history information mined from versioning systems. We applied approach, coined as HIST (Historical Information for Smell deTection), to eight software projects written in Java, and wherever possible compared with existing state-of-the-art smell detectors based on source code analysis. The results indicate that HIST’s precision ranges between 61% and 80%, and its recall ranges between 61% and 100%. More importantly, the results confirm that HIST is able to identify code smells that cannot be identified through approaches solely based on code analysis.

Bright talk bringing back the love - final

Andrew White

This document discusses how situational awareness improves user experience. It defines situational awareness as the perception of and reaction to changing events based on understanding the situation rather than just recalling stimuli. Most outages result from a lack of situational awareness. The document explores why situational awareness is lost and how new capabilities can help provide the right information when needed.

How to manage a time and beat a procrastination - azim tutorium 2016 by fir...

M Firdaus Harun

This document provides tips on time management and beating procrastination. It recommends identifying priorities and ranking tasks by importance and urgency. Important tasks with deadlines should be the focus. The Wunderlist app can help by allowing tasks to be written, starred, sorted by date, and checked off. Procrastination may be due to tasks being too big, hard, or lacking reward. To overcome it, start with small 2 minute tasks and use the Pomodoro technique of working in 25 minute intervals with short breaks. Evaluating progress and rewarding accomplishments can also help beat procrastination. The key takeaways are to clarify priorities and deadlines, use tools to organize tasks, and start small to overcome procrastinating tendencies

How to improve your system monitoring

Andrew White

The Refactoring Dilemma

Steve Chepp

Technical Debt

Gary Short

Measure It, Manage It, Ignore It - Software Practitioners and Technical Debt

Neil Ernst

Identifying and Managing Technical Debt

zazworka

The technical debt metaphor is useful in capturing the long-term impacts of tradeoffs taken during software maintenance between productivity (getting something done sooner) and maintainability (degradation of the code's quality over time). This webinar on Technical Debt will present techniques and insights that help software engineers to identify and track technical debt in their projects. We will outline how business and product quality goals should affect the choice of approaches (and combinations of approaches) for managing technical debt. More specifically, we will discuss a set of automated approaches based on static code analysis that are likely to spot problems in source code that have real impact on productivity and defect proneness. Based on previous empirical studies, we will give further advice on which types of debt can be found by these tools, and which types are not yet detectable.

Clean code and Code Smells

Mario Sangiorgio

The document discusses principles and best practices for writing clean code, including using meaningful names, separating commands and queries, avoiding repetition, using exceptions instead of return codes, and following object-oriented principles like polymorphism instead of switch statements on objects. It provides examples of good and bad code for concepts like single responsibility, primitive obsession, and refused bequest. The overall goal is to write code that is readable, maintainable, and extendable.

When, why and for whom do practitioners detect technical debts?: An experienc...

Norihiro Yoshida

How to Make Awesome SlideShares: Tips & Tricks

SlideShare

Getting Started With SlideShare

SlideShare

SlideShare is a global platform for sharing presentations, infographics, videos and documents. It has over 18 million pieces of professional content uploaded by experts like Eric Schmidt and Guy Kawasaki. The document provides tips for setting up an account on SlideShare, uploading content, optimizing it for searchability, and sharing it on social media to build an audience and reputation as a subject matter expert.

A Preliminary Field Study of Game Programming on Mobile Devices

Tao Xie

A Study on Code Smell Detection with Refactoring Tools in Object Oriented Lan...

ijcnes

A code smell is an indication in the source code that hypothetically indicates a design problem in the equivalent software. The Code smells are certain code lines which makes problems in source code. It also means that code lines are bad design shape or any code made by bad coding practices. Code smells are structural characteristics of software that may indicates a code or drawing problem that makes software hard to evolve and maintain, and may trigger refactoring of code. In this paper, we proposed some success issues for smell detection tools which can assistance to develop the user experience and therefore the acceptance of such tools. The process of detecting and removing code smells with refactoring can be overwhelming.

Feature Mining From a Collection of Software Product Variants

Ra'Fat Al-Msie'deen

This document proposes a three-step process to mine features from the source code of multiple software product variants. The process first extracts code elements from each variant, then uses formal concept analysis to group elements into common and variable partitions. Finally, it clusters elements into features using latent semantic indexing and formal concept analysis to identify mandatory and optional features based on element similarity. The approach was implemented and evaluated on a collection of ArgoUML products, identifying most features. Future work includes combining textual and semantic similarity and generating feature models from the mined features.

SciForge Workshop@Potsdam Institute for Climate Impact Reserach; Nov 2014

dreusser

SciForge: Is your code worth a full citation? Development of the software used for research at PIK is discussed in order to strengthen quality and reproducibility. Often, efforts put into good maintenance of software is not sufficiently recognised. However, the community is actively working on concepts and solutions enabling researchers to publish software, cite it and be credited for it. Software must meet the quality criteria of the scientific discourse to be a valuable and citeable contribution to science. Solutions also need to be developed regarding versioning and documentation, traceability, reproducibility and reusability. Furthermore, the archiving of source code and executables, the use of persistent identifiers, and metrics measuring productivity, impact, and recognition have to be addressed. SciForge is a network and a currently running project at GFZ addressing these questions. In the joint seminar, the current debate on scientific software publication will be presented and discussed.

An efficient tool for reusable software

prjpublications

This document discusses an efficient tool for a reusable software component taxonomy. It proposes integrating two existing classification schemes to develop a prototype system. Specifically: - It proposes developing an integrated classification scheme using a combination of existing schemes to better classify and store reusable software components in a repository for efficient retrieval. - A prototype was developed that integrates two existing classification schemes to demonstrate the proposed approach. This aims to improve on limitations of current software component retrieval methods.

Aliens in Your Apps! Are You Using Components With Known Vulnerabilities?

Sonatype

This presentation was given by Ryan Berg, Sonatype CSO, at the All Things Open conference in Raleigh, NC. We all know that Open Source brings speed, innovation, cost savings and more to our development efforts. It also brings risk. Bash, Heartbleed, Struts – anyone? Join this session to hear the latest research on the most risky open source component types – the alien invaders hiding in your software. And learn best practices to manage your risk based on the 11,000 people who shared their experiences in the 4 year industry-wide study on open source development and application security. Among the surprising results… - 1-in-3 organizations had or suspected an open source breach in the last 12 months - Only 16% of participants must prove they are not using components with known vulnerabilities - 64% don’t track changes in open source vulnerability data

Advantages and Disadvantages of a Monolithic Repository

mustafa sarac

This document discusses a case study conducted at Google to investigate the advantages and disadvantages of using a monolithic source code repository compared to multiple per-project repositories. The study utilized a survey of Google engineers as well as an analysis of developer tool logs. The survey found that engineers strongly prefer Google's monolithic repository and cited visibility of the codebase and simple dependency management as primary benefits. Engineer logs confirmed that they frequently view and edit code from other teams, indicating they take advantage of increased visibility. However, multi-repo systems provide benefits like more stable dependencies and flexibility in tool selection that a monolithic repo cannot match. Overall, the study uncovered several tradeoffs between the two approaches and that preferred development tools also influence engineers' preferences.

Adopting Open Source Software for Longer-term Reuse

Software Sustainability Institute

This document provides guidance on carefully selecting open source software for adoption and long-term reuse. It emphasizes the importance of evaluating several key factors, such as whether the software meets functional requirements both currently and for the future, has an active user and developer community, provides good documentation and support, remains up to date and interoperable with standards, and has a development roadmap that indicates ongoing support. The document advises asking the developer community questions and provides an example of thoroughly evaluating the Taverna workflow system based on these criteria.

A Preliminary Study of Android Refactorings

University of Hawai‘i at Mānoa

Viewers also liked

Mining the Modern Code Review Repositories: A Dataset of People, Process and ...

Norihiro Yoshida

Detecting Bad Smells in Source Code using Change History Information

Fabio Palomba

Bright talk bringing back the love - final

Andrew White

How to manage a time and beat a procrastination - azim tutorium 2016 by fir...

M Firdaus Harun

How to improve your system monitoring

Andrew White

The Refactoring Dilemma

Steve Chepp

Technical Debt

Gary Short

Measure It, Manage It, Ignore It - Software Practitioners and Technical Debt

Neil Ernst

Identifying and Managing Technical Debt

zazworka

Clean code and Code Smells

Mario Sangiorgio

When, why and for whom do practitioners detect technical debts?: An experienc...

Norihiro Yoshida

How to Make Awesome SlideShares: Tips & Tricks

SlideShare

Getting Started With SlideShare

SlideShare

Viewers also liked (13)

Mining the Modern Code Review Repositories: A Dataset of People, Process and ...

Detecting Bad Smells in Source Code using Change History Information

Bright talk bringing back the love - final

How to manage a time and beat a procrastination - azim tutorium 2016 by fir...

How to improve your system monitoring

The Refactoring Dilemma

Technical Debt

Measure It, Manage It, Ignore It - Software Practitioners and Technical Debt

Identifying and Managing Technical Debt

Clean code and Code Smells

When, why and for whom do practitioners detect technical debts?: An experienc...

How to Make Awesome SlideShares: Tips & Tricks

Getting Started With SlideShare

Similar to Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey

A Preliminary Field Study of Game Programming on Mobile Devices

Tao Xie

A Study on Code Smell Detection with Refactoring Tools in Object Oriented Lan...

ijcnes

Feature Mining From a Collection of Software Product Variants

Ra'Fat Al-Msie'deen

SciForge Workshop@Potsdam Institute for Climate Impact Reserach; Nov 2014

dreusser

An efficient tool for reusable software

prjpublications

Aliens in Your Apps! Are You Using Components With Known Vulnerabilities?

Sonatype

Advantages and Disadvantages of a Monolithic Repository

mustafa sarac

Adopting Open Source Software for Longer-term Reuse

Software Sustainability Institute

A Preliminary Study of Android Refactorings

University of Hawai‘i at Mānoa

A Model To Compare The Degree Of Refactoring Opportunities Of Three Projects ...

acijjournal

Refactoring is applied to the software artifacts so as to improve its internal structure, while preserving its external behavior. Refactoring is an uncertain process and it is difficult to give some units for measurement. The amount to refactoring that can be applied to the source-code depends upon the skills of the developer. In this research, we have perceived refactoring as a quantified object on an ordinal scale of measurement. We have a proposed a model for determining the degree of refactoring opportunities in the given source-code. The model is applied on the three projects collected from a company. UML diagrams are drawn for each project. The values for source-code metrics, that are useful in determining the quality of code, are calculated for each UML of the projects. Based on the nominal values of metrics, each relevant UML is represented on an ordinal scale. A machine learning tool, weka, is used to analyze the dataset, imported in the form of arff file, produced by the three projects

A MODEL TO COMPARE THE DEGREE OF REFACTORING OPPORTUNITIES OF THREE PROJECTS ...

acijjournal

This document presents a model for quantifying and comparing the degree of refactoring opportunities in three software projects. The model involves drawing UML diagrams for the projects, calculating source code metrics for each UML diagram, representing the diagrams on an ordinal scale based on the metrics, and using a machine learning tool (Weka) to analyze the resulting dataset. The tool uses a Naive Bayesian classifier to generate a confusion matrix for each project, allowing evaluation of the model's performance at classifying refactoring opportunities as low, medium, or high. The model is applied to three projects from a company to test its ability to measure and compare refactoring opportunities in code.

Code-Review-COW56-Meeting

Masud Rahman

Approaches and Challenges of Software Reusability: A Review of Research Liter...

IRJET Journal

The document discusses approaches and challenges related to software reusability. It outlines three main approaches to software reuse: component-based software reuse, domain engineering and software product lines, and architecture-based software reuse. It also discusses challenges to software reuse, including issues finding, selecting, and adapting existing components, as well as organizational and cultural challenges. Overall, the document examines the benefits of software reuse for improving productivity and quality, but also acknowledges there are still obstacles to implementing reuse effectively.

Rankingtherefactoring techniques

ijseajournal

The analytic hierarchy process (AHP) has been applied in many fields and especially to complex engineering problems and applications. The AHP is capable of structuring decision problems and finding mathematically determined judgments built on knowledge and experience. This suggests that AHP should prove useful in agile software development where complex decisions occur routinely. In this paper, the AHP is used to rank the refactoring techniques based on the internal code quality attributes. XP encourages applying the refactoring where the code smells bad. However, refactoring may consume more time and efforts.So, to maximize the benefits of the refactoring in less time and effort, AHP has been applied to achieve this purpose. It was found that ranking the refactoring techniques helped the XP team to focus on the technique that improve the code and the XP development process in general.

software development methodologies

UTeM

The document discusses and compares several software development methodologies: Extreme Programming (XP), Rational Unified Process (RUP), Object-Oriented Process, Environment and Notation (OPEN), and System Research Methodology. XP focuses on rapid, iterative development. RUP is a configurable process based on UML that ensures high-quality software. OPEN supports full lifecycle development using object-oriented modeling and can be tailored for different domains. System Research Methodology presents a five-stage guideline for research processes.

Research software identification - Catherine Jones

Jisc RDM

Ready, Set, Refactor

Jim Bethancourt

The document discusses various tools for detecting code smells and refactoring opportunities in Java code: - JDeodorant detects code smells like God Classes and suggests refactorings. It analyzed a 120K LOC codebase in 11 minutes, finding 115 refactoring opportunities. - JMove identifies Feature Envy smells and proposes moving methods. It analyzed the same codebase in 45 minutes, providing 13 suggestions. - JSpIRIT identifies 11 code "disharmonies" and found over 1300 in the codebase within a minute. It ranks issues but does not propose fixes. - Stench Blossom identifies smells as code is written without slowing development. It indicates severity and provides

GoOpen 2010: Sandro D'Elia

Friprogsenteret

Mouna Abidi

Ptidej Team

The document discusses research on identifying and analyzing the impact of patterns on the quality of multi-language systems. The objectives are to collect and categorize sets of programming languages used together, detect patterns in multi-language programs to track bugs and provide best practices, and study how patterns impact quality. The contributions will be a catalog of multi-language patterns and defects, a detection tool, and analysis of patterns' effects on quality attributes. Current work includes reviewing literature on language combinations and patterns to provide recommendations for high-quality multi-language development.

2014 IEEE JAVA SOFTWARE ENGINEERING PROJECT Repent analyzing the nature of id...

IEEEBEBTECHSTUDENTSPROJECTS

Similar to Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey (20)

A Preliminary Field Study of Game Programming on Mobile Devices

A Study on Code Smell Detection with Refactoring Tools in Object Oriented Lan...

Feature Mining From a Collection of Software Product Variants

SciForge Workshop@Potsdam Institute for Climate Impact Reserach; Nov 2014

An efficient tool for reusable software

Aliens in Your Apps! Are You Using Components With Known Vulnerabilities?

Advantages and Disadvantages of a Monolithic Repository

Adopting Open Source Software for Longer-term Reuse

A Preliminary Study of Android Refactorings

A Model To Compare The Degree Of Refactoring Opportunities Of Three Projects ...

A MODEL TO COMPARE THE DEGREE OF REFACTORING OPPORTUNITIES OF THREE PROJECTS ...

Code-Review-COW56-Meeting

Approaches and Challenges of Software Reusability: A Review of Research Liter...

Rankingtherefactoring techniques

software development methodologies

Research software identification - Catherine Jones

Ready, Set, Refactor

GoOpen 2010: Sandro D'Elia

Mouna Abidi

2014 IEEE JAVA SOFTWARE ENGINEERING PROJECT Repent analyzing the nature of id...

Recently uploaded

Ocean lotus Threat actors project by John Sitima 2024 (1).pptx

SitimaJohn

Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.

How to Get CNIC Information System with Paksim Ga.pptx

danishmna97

みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...

名前です男

How to use Firebase Data Connect For Flutter

Daiki Mogmet Ito

Building Production Ready Search Pipelines with Spark and Milvus

Zilliz

Skybuffer SAM4U tool for SAP license adoption

Tatiana Kojar

Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool. SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

akankshawande

Artificial Intelligence for XMLDevelopment

Octavian Nadolu

In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject. We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup. Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved. The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring. The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise. By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.

20240609 QFM020 Irresponsible AI Reading List May 2024

Matthew Sinclair

Recommendation System using RAG Architecture

fredae14

20240607 QFM018 Elixir Reading List May 2024

Matthew Sinclair

5th LF Energy Power Grid Model Meet-up Slides

DanBrown980551

5th Power Grid Model Meet-up It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology. Power Grid Model The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services. Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability. Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization. What to expect For the upcoming meetup we are organizing, we have an exciting lineup of activities planned: -Insightful presentations covering two practical applications of the Power Grid Model. -An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024. -An interactive brainstorming session to discuss and propose new feature requests. -An opportunity to connect with fellow Power Grid Model enthusiasts and users.

Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...

Jeffrey Haguewood

Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows. We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases. This video focuses on integration of Salesforce with Bonterra Impact Management. Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

HCL Notes and Domino License Cost Reduction in the World of DLAU

panagenda

Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/ The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this! We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model. Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward. These topics will be covered - Reducing license cost by finding and fixing misconfigurations and superfluous accounts - How do CCB and CCX licenses really work? - Understanding the DLAU tool and how to best utilize it - Tips for common problem areas, like team mailboxes, functional/test users, etc - Practical examples and best practices to implement right away

Project Management Semester Long Project - Acuity

jpupo2018

Acuity is an innovative learning app designed to transform the way you engage with knowledge. Powered by AI technology, Acuity takes complex topics and distills them into concise, interactive summaries that are easy to read & understand. Whether you're exploring the depths of quantum mechanics or seeking insight into historical events, Acuity provides the key information you need without the burden of lengthy texts.

Columbus Data & Analytics Wednesdays - June 2024

Jason Packer

Introduction of Cybersecurity with OSS at Code Europe 2024

Hiroshi SHIBATA

I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems. The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS. Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application. I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.

AI 101: An Introduction to the Basics and Impact of Artificial Intelligence

IndexBug

Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf

Malak Abu Hammad

Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers: * What is Vector Search? * Importance and benefits of vector search * Practical use cases across various industries * Step-by-step implementation guide * Live demos with code snippets * Enhancing LLM capabilities with vector search * Best practices and optimization strategies Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications. #MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology

Monitoring and Managing Anomaly Detection on OpenShift.pdf

Tosin Akinosho

Monitoring and Managing Anomaly Detection on OpenShift Overview Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices. Key Topics Covered 1. Introduction to Anomaly Detection - Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems. 2. Understanding Edge (IoT) - Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source. 3. What is ArgoCD? - Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices. 4. Deployment Using ArgoCD for Edge Devices - Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD. 5. Introduction to Apache Kafka and S3 - Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions. 6. Viewing Kafka Messages in the Data Lake - Learn how to view and analyze Kafka messages stored in a data lake for better insights. 7. What is Prometheus? - Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices. 8. Monitoring Application Metrics with Prometheus - Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system. 9. What is Camel K? - Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes. 10. Configuring Camel K Integrations for Data Pipelines - Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow. 11. What is a Jupyter Notebook? - Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text. 12. Jupyter Notebooks with Code Examples - Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.

Recently uploaded (20)

Ocean lotus Threat actors project by John Sitima 2024 (1).pptx

How to Get CNIC Information System with Paksim Ga.pptx

How to use Firebase Data Connect For Flutter

Building Production Ready Search Pipelines with Spark and Milvus

Skybuffer SAM4U tool for SAP license adoption

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

Artificial Intelligence for XMLDevelopment

20240609 QFM020 Irresponsible AI Reading List May 2024

Recommendation System using RAG Architecture

20240607 QFM018 Elixir Reading List May 2024

5th LF Energy Power Grid Model Meet-up Slides

Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...

HCL Notes and Domino License Cost Reduction in the World of DLAU

Project Management Semester Long Project - Acuity

Columbus Data & Analytics Wednesdays - June 2024

Introduction of Cybersecurity with OSS at Code Europe 2024

AI 101: An Introduction to the Basics and Impact of Artificial Intelligence

Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf

Monitoring and Managing Anomaly Detection on OpenShift.pdf

Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey

1. Understanding the Longevity of Code SmellsPreliminary Results of an Exploratory Survey Roberta Arcoverde – rarcoverde@inf.puc-rio.br Alessandro Garcia – afgarcia@inf.puc-rio.br Eduardo Figueiredo – figueiredo@dcc.ufmg.br ICSE.11

2. why? May 11 Roberta @ OPUS Group 2 codesmellsentailevidenceofbadqualitycode harder to readandmaintain some [patternsof] smellsseem to be “ignored”

3. why? May 11 Roberta @ OPUS Group 3 codesmellsentailevidenceofbadqualitycode harder to readandmaintain some [patternsof] smellsseem to be “ignored”  [1] How we refactor and how we know it. Murphy-Hill et al. [ICSE 2010]

4. objective May 11 Roberta @ OPUS Group 4 perform a firstexploratorystudy to identify which factors influence longevity of code smells, based on refactoring habits

5. refactoring habits howoftencode is refactored? which refactorings are prioritized? is refactoringapplied as anisolateactivity? which refactorings are considered to beharder to apply? howoftenandwhenrefactoringtools are used? May 11 Roberta @ OPUS Group 5

6. which factors influence refactoring habits natureof software beingdeveloped reusableassets (frameworks, libraries, software productlines) standalone applications use of TDD developer’sexperience May 11 Roberta @ OPUS Group 6

7. survey setting - questionnaire May 11 Roberta @ OPUS Group 7

8. participants May 11 Roberta @ OPUS Group 8 agiledevelopmentteams framework developers = 33 answers

9. participants distribution May 11 Roberta @ OPUS Group 9

10. participants distribution - TDD May 11 Roberta @ OPUS Group 10

11. most recurring smells May 11 Roberta @ OPUS Group 11 duplicated code – 78% (26) long methods – 78% (26) inadequate naming – 69% (23) god classes – 42% (14) same results for developers of reusable assets and standalone applications... ...regardless of experience level

12. how often refactoring tools are used... May 11 Roberta @ OPUS Group 12

13. ...and reasons for not using them May 11 Roberta @ OPUS Group 13 tool does notsupportthedesiredrefactoring – 41% theydidnotknowanyrefactoringtool – 37% tools do notallowthem to easilyfollowtheeffectsofrefactoring – 28% it’snoteasy to testwhetherthesystem’sbehaviourwaspreserved – 22%

14. classifying refactorings - difficulty May 11 Roberta @ OPUS Group 14

15. concluding remarks May 11 15 Roberta @ OPUS Group nature of the software being developed influences refactoring habits reusable assets developers consider the possibility of breaking APIs before refactoring refactoring prioritization is fairly different when we consider reusable assets versus standalone applications refactoring scope is considered

16. concluding remarks visualizationmechanismsimprovements are needed testingwhetherthecodetransformationpreservedbehaviour is noteasy specifictoolsorfeaturescouldbeinvestigated for refactorings oflibraries, frameworks and software productlines May 11 Roberta @ OPUS Group 16

17. thank you questions? May 11 Roberta @ OPUS Group 17

18. classifying refactorings - priority May 11 Roberta @ OPUS Group 18

19. classifying refactorings - frequency May 11 Roberta @ OPUS Group 19

Editor's Notes

Good afternoon. Thank you for coming to my presentation. My name is Roberta, I’m a MSc student at PUC-Rio and I will present an exploratory study towards understanding the longevity of code smells
The first question comes to our mind is why investigating codesmellslongevity?As we all know, Code smells are symptoms in the source code that possibly indicates a deeper maintainability problem – making code harder to read and to maintain. And yet, some patterns of smells seem to be, either deliberately or not, ignored (or not dealt with as promptly as others), so they linger in code longer than others. There is, however, little knowledge about the factors that are likely to influence this longevity. Understanding which and why those refactoring candidates are neglected can help us identify improvements for refactoring tools and IDEs.1st thing comes to mind whyAs we know, code smells are..And yet, some patterns of smells seems to be, deliberately, or not, ignored..There is little knowledge about factors that are likely to influenceUnderstanding which and why those refactoring candidates are neglected…
Previous studies were dedicated to understanding the state of practice of refactoring, identifying how and when they are commonly applied. Our investigation wants to complement such studies, by revealing recurring factors which lead developers to not worry about certain code smells, and we do so based on their refactoring habits.
We sent the questionnaire to companies and colleagues in order to diversify the answers.This study was carried out in october 2010, and we had 33 answers from different groups of developers, from Academy, agile development teams, software factories and also from open source framework developers.

Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (13)

Similar to Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey

Similar to Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey (20)

Recently uploaded

Recently uploaded (20)

Understanding the Longevity of Code Smells - Preliminary Results of an Explanatory Survey

Editor's Notes