QwalKeko, a History Querying Tool

•

0 gefällt mir•436 views

Presentation about our ERA track paper given on csmr2013. Paper can be found here: http://soft.vub.ac.be/Publications/2013/vub-soft-tr-13-02.pdf

QwalKeko,
a History Querying Tool
Reinout Stevens, Coen De Roover, Carlos Noguera
resteven@vub.ac.be
@ReinoutStevens

1
Wednesday 6 March 13

Context

Program
Comprehension

2
Wednesday 6 March 13

Was this method pulled up?
Who introduced
this class?
Who has made changes to
my classes?

History Questions
How often is this method
Why were these changes changed?
introduced? Template-based Reconstruction of Complex Refactorings
Kyle Prete, Napol Rachatasumrit, Nikita Sudan, Miryung Kim
International Conference on Software Maintenance (ICSM), p.1--10, 2010

Using Information Fragments to Answer the Questions Developers Ask
Thomas Fritz and Gail C. Murphy
International Conference on Software Engineering (ICSE), p.175--184, 2010
3
Wednesday 6 March 13

Pulled up Method
BaseClass

Version 1

DerivedClass
Method()

BaseClass
Method()
Version 2

DerivedClass

4
Wednesday 6 March 13

Pulled up Method
(ast :MethodDeclaration ?method)
Version 1 (declaring-class ?method ?derived)

(method-moved ?method ?pulled)
Version 2 (declaring-class ?pulled ?base)
(superclass ?base ?derived)

Template-based Reconstruction of Complex Refactorings
Kyle Prete, Napol Rachatasumrit, Nikita Sudan, Miryung Kim
International Conference on Software Maintenance (ICSM), p.1--10, 2010
5
Wednesday 6 March 13

QwalKeko
(qwal graph version1 version2
(qin-current
Version 1 (ast :MethodDeclaration ?method)
(declaring-class ?method ?derived))

q=> ;;transition to next version

(qin-current
(method-moved ?method ?pulled)
Version 2 (declaring-class ?pulled ?base)
(superclass ?base ?derived)))

6
Wednesday 6 March 13

Multiversion Refactorings
(qwal graph version1 ?versionX
Version 1
(qin-current
(ast :MethodDeclaration ?method)
(declaring-class ?method ?derived))

... (q=>+) ;;skip >= 1 versions

(qin-current
Version X (method-moved ?method ?pulled)
(declaring-class ?pulled ?base)
(superclass ?base ?derived)))

7
Wednesday 6 March 13

QwalKeko
Pr Graph Query
og Language
ra
La m

od ry
ng Q Qwal

sto
el
ua ue

Hi
ge ry

M
Ekeko +

+

8
Wednesday 6 March 13

Other Domains

• Answering Developer Questions
• Temporal Bad Smells
• Detecting Co-changing Entities
• Zombie Methods
• Verifying Design Process
Reasoning over the Evolution of Source Code using Quantiﬁed Regular Path Expressions.
Reinout Stevens, Coen De Roover, Carlos Noguera and Viviane Jonckers
Working Conference on Reverse Engineering (WCRE), 2011
9
Wednesday 6 March 13

Future Work:
Replaying Changes
...

??
...

12 - public int foo;
12 + private int foo;
37 + public getFoo(){
38 + return foo; }

10
Wednesday 6 March 13

Questions

Reinout Stevens
resteven@vub.ac.be
@ReinoutStevens
http://github.com/ReinoutStevens/damp.qwal
http://github.com/cderoove/damp.ekeko

11
Wednesday 6 March 13

Weitere ähnliche Inhalte

Ähnlich wie QwalKeko, a History Querying Tool

Bayesian network based software reliability prediction

JULIO GONZALEZ SANZ

CVPR 2018 完全読破チャレンジ報告会 cvpaper.challenge 勉強会@Wantedly白金台オフィス cvpaper.challenge はコンピュータビジョン分野の今を映し、創り出す挑戦です。論文読破・まとめ・アイディア考案・議論・実装・論文執筆（・社会実装）に至るまで広く取り組み、あらゆる知識を共有しています。 http://xpaperchallenge.org/cv/

教師なし画像特徴表現学習の動向 {Un, Self} supervised representation learning (CVPR 2018 完全読破...

cvpaper. challenge

Artificial Intelligence Applications in Petroleum Engineering - Part I

Ramez Abdalla, M.Sc

During software evolution changes are inevitable. These changes may lead to design erosion and the introduction of inadequate design solutions, such as design antipatterns. Several empirical studies provide evidence that the presence of antipatterns is generally associated with lower productivity, greater rework, and more significant design efforts for developers. In order to improve the quality and remove antipatterns, refactoring operations are needed. In this demo, we present the Extract class features of ARIES (Automated Refactoring In EclipSe), an Eclipse plug-in that supports the software engineer in removing the “Blob” antipattern.

ARIES: An Eclipse Plug-in To Support Extract Class Refactoring

Fabio Palomba

The caret package is a unified interface to a large number of predictive model functions in R. First created in 2005, the home for the source code and documentation has changed several times. In this talk, we will outline the somewhat unique aspects of the package and how it impacts the development environment (including documentation and testing). Friction points with CRAN and their resolution will also be discussed.

The caret package is a unified interface to a large number of predictive mode...

odsc

Observability has never been more important: the complexity of microservices makes it harder and harder to answer basic questions about system behavior. The conventional wisdom claims that Metrics, Logging and Tracing are “the three pillars” of observability… yet software organizations check these three boxes and are still grasping at straws during emergencies. In this session we’ll illustrate the problem with the three pillars: metrics, logs, and traces are just data – they are the fuel, not the car.

Three Pillars, No Answers: Helping Platform Teams Solve Real Observability Pr...

DevOps.com

The past decade has seen tremendous growth in production deployments of machine learning algorithms across a range of applications such as targeted advertising, self driving cars, speech translation, medical diagnosis etc [1]. In these contexts, models make key decisions such as predicting the likelihood of a person committing a future crime, trustworthiness for a loan approval, medical diagnosis etc [2]. Presence of bias based on gender, geographical location, race etc., and their consequent negative impact, have been uncovered in several of these deployments [3], [4]. Industries and governments are reacting, enacting regulations requiring that decisions made by machine learning models be Interpretable/Explainable [5]. Explainability across the full range of ML and DL algorithms is an unsolved research problem, with many innovations over the last several years and entire conferences devoted to the topic. However, even simple explainability solutions that are considered established in development (training environments) run into additional difficulties when put into live production. Our design pattern uses a well known technique for explainability - the Canary model (sometimes called Surrogate model) [6,7]. In this approach, a classically non-explainable technique, such as a Neural Network, is paired with an explainable model (that approximates the predictions of the non-explainable technique) such as a Decision Tree. As long as predictions match - the Canary model’s behavior can be used to provide a human understandable reasoning for the prediction.

Interpretability and Reproducibility in Production Machine Learning Applicat...

Swaminathan Sundararaman

Multimodal Residual Learning for Visual Question-Answering

NAVER D2

SBST 2015 - 3rd Tool Competition for Java Junit test Tools

Tanja Vos

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1dImvww. Martin Thompson overviews Java's evolution, comparing it with C++'s, discussing the challenges of pushing the performance limits. Filmed at qconsf.com. Martin Thompson is a high-performance and low-latency specialist, with experience gained over two decades working on large scale transactional and big-data systems.

Practicing at the Cutting Edge: Learning and Unlearning about Java Performance

C4Media

ga-2.ppt

sayedmha

Jing Ma - 2017 - Detect Rumors in Microblog Posts Using Propagation Structur...

Association for Computational Linguistics

A novel approach for satellite imagery storage by classify

iaemedu

A novel approach for satellite imagery storage by classifying the non duplica...

IAEME Publication

Bug Prediction Based on Fine-Grained Module Histories

ASE02.ppt

50120140503004

In this talk I will overview ten years of research in the application of evolutionary computation ideas in the natural sciences. The talk will take us on a tour that will cover problems in nanoscience, e.g. controlling self-‐organizing systems, optimizing scanning probe microscopy, etc., problems arising in bioinformatics, such as predicting protein structures and their features, to challenges emerging in systems and synthetic biology. Although the algorithmic solutions involved in these problems are different from each other, at their core, they retain Darwin’s wonderful insights. I will conclude the talk by giving a personal view on why EC has been so successful and where, in my mind, the future lies.

Darwin’s Magic: Evolutionary Computation in Nanoscience, Bioinformatics and S...

Natalio Krasnogor

Eeee2017 Conference - OR in the digital era - ICT challenges | Presentation

Christos Papalitsas

Ähnlich wie QwalKeko, a History Querying Tool (20)

Bayesian network based software reliability prediction

教師なし画像特徴表現学習の動向 {Un, Self} supervised representation learning (CVPR 2018 完全読破...

Artificial Intelligence Applications in Petroleum Engineering - Part I

ARIES: An Eclipse Plug-in To Support Extract Class Refactoring

The caret package is a unified interface to a large number of predictive mode...

Three Pillars, No Answers: Helping Platform Teams Solve Real Observability Pr...

Interpretability and Reproducibility in Production Machine Learning Applicat...

Multimodal Residual Learning for Visual Question-Answering

SBST 2015 - 3rd Tool Competition for Java Junit test Tools

Practicing at the Cutting Edge: Learning and Unlearning about Java Performance

ga-2.ppt

Jing Ma - 2017 - Detect Rumors in Microblog Posts Using Propagation Structur...

A novel approach for satellite imagery storage by classify

A novel approach for satellite imagery storage by classifying the non duplica...

Bug Prediction Based on Fine-Grained Module Histories

ASE02.ppt

50120140503004

Darwin’s Magic: Evolutionary Computation in Nanoscience, Bioinformatics and S...

Eeee2017 Conference - OR in the digital era - ICT challenges | Presentation

QwalKeko, a History Querying Tool

1. QwalKeko, a History Querying Tool Reinout Stevens, Coen De Roover, Carlos Noguera resteven@vub.ac.be @ReinoutStevens 1 Wednesday 6 March 13

2. Context Program Comprehension 2 Wednesday 6 March 13

3. Was this method pulled up? Who introduced this class? Who has made changes to my classes? History Questions How often is this method Why were these changes changed? introduced? Template-based Reconstruction of Complex Refactorings Kyle Prete, Napol Rachatasumrit, Nikita Sudan, Miryung Kim International Conference on Software Maintenance (ICSM), p.1--10, 2010 Using Information Fragments to Answer the Questions Developers Ask Thomas Fritz and Gail C. Murphy International Conference on Software Engineering (ICSE), p.175--184, 2010 3 Wednesday 6 March 13

4. Was this method pulled up? Who introduced this class? Who has made changes to my classes? History Questions How often is this method Why were these changes changed? introduced? Template-based Reconstruction of Complex Refactorings Kyle Prete, Napol Rachatasumrit, Nikita Sudan, Miryung Kim International Conference on Software Maintenance (ICSM), p.1--10, 2010 Using Information Fragments to Answer the Questions Developers Ask Thomas Fritz and Gail C. Murphy International Conference on Software Engineering (ICSE), p.175--184, 2010 3 Wednesday 6 March 13

5. Pulled up Method BaseClass Version 1 DerivedClass Method() BaseClass Method() Version 2 DerivedClass 4 Wednesday 6 March 13

6. Pulled up Method (ast :MethodDeclaration ?method) Version 1 (declaring-class ?method ?derived) (method-moved ?method ?pulled) Version 2 (declaring-class ?pulled ?base) (superclass ?base ?derived) Template-based Reconstruction of Complex Refactorings Kyle Prete, Napol Rachatasumrit, Nikita Sudan, Miryung Kim International Conference on Software Maintenance (ICSM), p.1--10, 2010 5 Wednesday 6 March 13

7. QwalKeko (qwal graph version1 version2 (qin-current Version 1 (ast :MethodDeclaration ?method) (declaring-class ?method ?derived)) q=> ;;transition to next version (qin-current (method-moved ?method ?pulled) Version 2 (declaring-class ?pulled ?base) (superclass ?base ?derived))) 6 Wednesday 6 March 13

8. Multiversion Refactorings (qwal graph version1 ?versionX Version 1 (qin-current (ast :MethodDeclaration ?method) (declaring-class ?method ?derived)) ... (q=>+) ;;skip >= 1 versions (qin-current Version X (method-moved ?method ?pulled) (declaring-class ?pulled ?base) (superclass ?base ?derived))) 7 Wednesday 6 March 13

9. QwalKeko Pr Graph Query og Language ra La m od ry ng Q Qwal sto el ua ue Hi ge ry M Ekeko + + 8 Wednesday 6 March 13

10. Other Domains • Answering Developer Questions • Temporal Bad Smells • Detecting Co-changing Entities • Zombie Methods • Verifying Design Process Reasoning over the Evolution of Source Code using Quantiﬁed Regular Path Expressions. Reinout Stevens, Coen De Roover, Carlos Noguera and Viviane Jonckers Working Conference on Reverse Engineering (WCRE), 2011 9 Wednesday 6 March 13

11. Future Work: Replaying Changes ... ?? ... 12 - public int foo; 12 + private int foo; 37 + public getFoo(){ 38 + return foo; } 10 Wednesday 6 March 13

12. Questions Reinout Stevens resteven@vub.ac.be @ReinoutStevens http://github.com/ReinoutStevens/damp.qwal http://github.com/cderoove/damp.ekeko 11 Wednesday 6 March 13

QwalKeko, a History Querying Tool

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie QwalKeko, a History Querying Tool

Ähnlich wie QwalKeko, a History Querying Tool (20)

QwalKeko, a History Querying Tool