On the Survival of Database Frameworks in Java Projects

•

2 likes•631 views

Presentation by Mathieu Goeminne at SATTOSE 2015 research seminar of joint research. Abstract: More and more software systems are becoming data-intensive, and require intensive access to a database. We empirically study a large corpus of data-intensive Java projects as well as the database frameworks used in these projects to manage the connection between the source code and the database. We also study how this usage evolves over time. In particular, we study whether certain database frameworks are used simultaneously, whether some database frameworks get replaced over time by others. Using the statistical technique of survival analysis, we study the survival of database frameworks in the Java projects in which they are used, as well as the survival of these projects themselves.

Science

ONTHE USE OF DATABASE
FRAMEWORKS IN JAVA PROJECTS
A LARGE-SCALE HISTORICAL EMPIRICAL ANALYSIS
Mathieu Goeminne
mathieu.goeminne@umons.ac.be
Tom Mens
tom.mens@umons.ac.be
Software Engineering Lab
Alexandre Decan
alexandre.decan@umons.ac.be

GENERAL CONTEXT
• FNRS interuniversity research collaboration with the University of Namur.
• Study of software systems that use a database.
• Understanding the dynamics, issues and evolution of such systems.
• Need to take into account their speciﬁcities:
• How is their connection managed?
• How do the source code and the database co-evolve?
• How can we assess and increase the quality of such systems?

DATABASE FRAMEWORKS?
.java
.jsp
.php
DBMS
ORM
Connector
Session
manager
Source code DatabaseFrameworks

ONTHIS PRESENTATION
• Focus on database frameworks.
• Empirical study for answering 3 research questions:
• Q1: Which combinations of DB frameworks are being used
simultaneously?
• Q2: How long do DB frameworks ‘survive’ in the projects that use
them?
• Q3: Does the introduction of a DB framework inﬂuence the
survivability of another one?

CASE STUDY
• 20 Java DB frameworks.
• Top 5 retained: JDBC, Spring,
JPA, Vaadin, Hibernate.
• 13,307 Java projects from the
Github Java Corpus (MSR10):
3,707 of them use at least one
retained framework)

SURVIVAL ANALYSIS:
KAPLAN-MEIER ESTIMATOR
• Estimates the survival
function of a population
• Takes into account right
censoring (the event may
occur after the last
observation)
• Mantel-Haenszel test for
determining if 2 survival
functions differ.

Q1 - Which combinations of DB frameworks are
being used simultaneously?
• In most cases (98%), different
frameworks used in a project are
used in combination.
• JDBC is used as the single DB
framework in 56% of all projects.
• Most projects (83%) using
Hibernate also use JDBC.
Hibernate is almost never (3%)
used alone.
• JDBC used as support for the other
FW, providing unique services?
# projects using X fw vsY fw simultaneously
# projects using X andY simultaneously

Q2 - How long do database frameworks ‘survive’ in the projects?
• If a framework is introduced, it remains in
>45% of all the projects.
• Different trends. After 30 days:
• Hibernate disappears from 11.7% of
projects
• Spring disappears from 3.7% of
projects
• Partial order: JPA and Spring have higher
survival rates than JDBC and Hibernate.
• No clear relation between the order
and the popularity of the considered
frameworks.
Survival functions of top 5 FW according
to Kaplan-Meier estimator
p-values for difference tests of survival
functions

Q3 - Does the introduction of a database framework
inﬂuence the survivability of another one?
• Visually, the introduction of
some frameworks seems to
have a favorable inﬂuence.
• After Bonferroni correction,
no signiﬁcant difference
in the survival
functions… at project level.
• In the future: ﬁle level
analyse.
Survival functions of JDBC with and without Spring

CONCLUSIONS
• Important coexistence
• Especially between JDBC and the other considered DB frameworks.
• JDBC is still often present in projects despite the use frameworks
providing more advanced, higher level services.
• In our study, there is no evidence for competition between frameworks.
• An introduced framework has an ≳45% of chance that it will remain.
• The disappearance of a framework doesn’t seem to be related to the
introduction of an other one.

FUTURE WORK
• Finer granularity: from projects to packages, ﬁles, methods, …
• Analysis of (un)frequently used framework services.
• Looking for evolutionary patterns:
• New frameworks introduced for their unique services?
• Simple SQL queries are replaced by framework services, while
complex queries remain as it?
• Extension to frameworks for less structured databases, NoSQL, etc.

Viewers also liked

This talk was presented by Tom Mens and Loup Meurice at the EvoLille'15 European Open Symposium on Empirical Software Engineering (December 2015). We report on the evolution of open source Java projects relying on relational database technologies. We empirically analysed how the use of Java database access technologies evolves over time. We carried out a coarse-grained source-code analysis over several thousands of Java projects on GitHub, and complemented this by a fine-grained longitudinal analysis of the co-evolution between database schema changes and source code changes within three large Java projects (OSCAR, OpenEMR and BroadLeaf). The presented results are a first step towards a recommendation system supporting developers in writing database-centered code. The research was part of an interuniversity research project between University of Mons and University of Namur, financed by the F.R.S.-FNRS, Belgium.

Evolution of database access technologies in Java-based software projects

Tom Mens

GISMO

Tom Mens

Automated Planning for Resolving Model Inconsistencies - A Scalability Study

Tom Mens

This presentation is joint work by Alexandre Decan, Tom Mens and Maelick Claes (Software Engineering Lab, COMPLEXYS research institute, University of Mons). It was presented by Maelick during the International Workshop on Software Ecosystem Architectures (WEA 2016) in Copenhagen, on 29 November 2016. Abstract of the accompanying paper (DOI 10.1145/1235): Package-based software ecosystems are composed of thousands of interdependent software packages. Many empirical studies have focused on software packages belonging to a single software ecosystem, and suggest to generalise the results to more ecosystems. We claim that such a generalisation is not always possible, because the technical structure of software ecosystems can be very different, even if these ecosystems belong to the same domain. We confirm this claim through a study of three big and popular package-based programming language ecosystems: R’s CRAN archive network, Python’s PyPI distribution, and JavaScript’s NPM package manager. We study and compare the structure of their package dependency graphs and reveal some important differences that may make it difficult to generalise the findings of one ecosystem to another one. A follow-up on this work can be found in the SANER 2017 paper by the same authors, entitled "An Empirical Comparison of Dependency Issues in OSS Packaging Ecosystems”

On the topology of package dependency networks: A comparison of programming l...

Tom Mens

In this short presentation I introduce the need for, and use of executable modelling for the purpose of developing and improving software systems and business processes. I present the need for modelling tools, modelling languages and formalisms. I also present some of the open challenges in this domain. This presentation was given at an research meeting at the University of Mons (Belgium) in January 2016.

Executable modeling and simulation of system software and processes

Tom Mens

This talk was presented at the international research seminar SATTOSE 2016 in Bergen, Norway (2016-07-12). We present various ways to test executable statechart models: using unit testing, behaviour-driven development, design by contract, property statecharts and regression testing. We illustrate these ideas on the basis of a running example of a microwave oven controller. We also present a proof-of-concept implementation of a statechart interpreter supporting all these ideas. The interpreter, called Sismic, is provided as an open source Python library. This research was carried out by Tom Mens and Alexandre Decan, Software Engineering Lab, University of Mons, Belgium.

Model-based testing of executable statecharts

Tom Mens

In this talk we discuss the results of the survey of software ecosystems researchers conducted in October-December 2014. Researchers have been asked to identify the current trends in ecosystems’ research as well as the challenges the research community has to address in the coming years. We augment discussion of the trends identified by the community by the review of some of the recent results on software ecosystems.

Challenges in Software Ecosystem Research

Tom Mens

Presentation by Eleni Constantinou (postdoctoral researcher at the Software Engineerin Lab of the University of Mons, Belgium) during the Workshop on Ecosystem Architecuters (WEA2016), Copenhagen, Denmark, 29 November 2016. Abstract: Software ecosystems evolve through an active community of developers who contribute to projects within the ecosystem. However, development teams change over time, suggesting a potential impact on the evolution of the technical parts of the ecosystem. The impact of such modifications has been studied by previous works, but only temporary changes have been investigated, while the long-term effect of permanent changes has yet to be explored. In this paper, we investigate the evolution of the ecosystem of Ruby on Rails in GitHub in terms of such temporary and permanent changes of the development team. We use three viewpoints of the Rails ecosystem evolution to discuss our preliminary findings: (1) the base project; (2) the forks; and (3) the entire ecosystem containing both base project and forks.

Social and Technical Evolution of the Ruby on Rails Software Ecosystem

Tom Mens

Software Ecosystem Evolution. It's complex!

Tom Mens

Viewers also liked (9)

Evolution of database access technologies in Java-based software projects

GISMO

Automated Planning for Resolving Model Inconsistencies - A Scalability Study

On the topology of package dependency networks: A comparison of programming l...

Executable modeling and simulation of system software and processes

Model-based testing of executable statecharts

Challenges in Software Ecosystem Research

Social and Technical Evolution of the Ruby on Rails Software Ecosystem

Software Ecosystem Evolution. It's complex!

More from Tom Mens

How to be(come) a successful PhD student

Tom Mens

Recognising bot activity in collaborative software development

Tom Mens

A Dataset of Bot and Human Activities in GitHub

Tom Mens

The (r)evolution of CI/CD on GitHub

Tom Mens

In January 2018, four Software Engineering research groups located in different Belgian Universities launched a five year research project to nurture the software ecosystems of the future. We assembled a diverse team of about a dozen researchers and embarked on an exciting journey leading to a rich and diverse suite of papers, tools and datasets. Halfway into the project the corona pandemic intervened, but despite several months of lockdown, we succeeded in increasing inter-university collaboration. In this paper we share our achievements so that the BENEVOL community may benefit from our experience.

Nurturing the Software Ecosystems of the Future

Tom Mens

Comment programmer un robot en 30 minutes?

Tom Mens

On the rise and fall of CI services in GitHub

Tom Mens

Presentation at FOSDEM 2022 Composition and Dependency Management DevRoom of empirical research on backporting practices in package dependency networks, published in the IEEE Transactions in Software Engineering in 2021 (https://doi.org/10.1109/TSE.2021.3112204) Joint work by Alexandre Decan, Tom Mens; Ahmed Zeourali, Coen De Roover as part of the Belgian Excellence of Science research project SECOASSIST (https://secoassist.github.io)

On backporting practices in package dependency networks

Tom Mens

Presentation by Tom Mens at PackagingCon 2021 on Wednesday 10 November 2021. Abstract: Semantic versioning (semver) is a commonly accepted open source practice, used by many package management systems to inform whether new package releases introduce possibly backward incompatible changes. Maintainers depending on such packages can use this practice to reduce the risk of breaking changes in their own packages by specifying version constraints on their dependencies. Depending on the amount of control a package maintainer desires to assert over her package dependencies, these constraints can range from very permissive to very restrictive. We empirically compared the evolution of semver compliance in four package management systems: Cargo, npm, Packagist and Rubygems. We discuss to what extent ecosystem-specific characteristics influence the degree of semver compliance, and we suggest to develop tools adopting the wisdom of the crowds to help package maintainers decide which type of version constraints they should impose on their dependencies. We also studied to which extent the packages distributed by these package managers are still using a 0.y.z release, suggesting less stable and immature packages. We explore the effect of such "major zero" packages on semantic versioning adoption. Our findings shed insight in some important differences between package managers with respect to package versioning policies. Our empirical results have been published in two peer-reviewed academic journals: the IEEE Transactions in Software Engineering (https://doi.org/10.1109/TSE.2019.2918315) and Elsevier Science of Computer Programming (https://doi.org/10.1016/j.scico.2021.102656). Achknowledgments: Research conducted in the context of the SECOASSIST "Excellence of Science" Research Project.

Comparing semantic versioning practices in Cargo, npm, Packagist and Rubygems

Tom Mens

Presentation by Tom Mens at FOSDEM21 (Free Open Source Developers Meeting, February 2021). Published in Science of Computer Programming, August 2021. https://doi.org/10.1016/j.scico.2021.102656 Abstract: When developing open source software end-user applications or reusable software packages, developers depend on software packages distributed through package managers such as npm, Packagist, Cargo, RubyGems. In addition to this, empirical evidence has shown that these package managers adhere to a large extent to semantic versioning principles. Packages that are still in major version zero are considered unstable according to semantic versioning, as some developers consider such packages as immature, still being under initial development. This presentation reports on large-scale empirical evidence on the use of dependencies towards 0.y.z versions in four different software package distributions: Cargo, npm, Packagist and RubyGems. We study to which extent packages get stuck in the zero version space, never crossing the psychological barrier of major version zero. We compare the effect of the policies and practices of package managers on this phenomenon. We do not reveal the results of our findings in this abstract yet, as it would spoil the fun of the presentation.

Lost in Zero Space

Tom Mens

Detecting the presence of bots in distributed software development activity is very important in order to prevent bias in socio-technical empirical studies. In previous work, we proposed a classification model to detect bots in GitHub repositories based on the pull request and issue comments of GitHub accounts. The current study generalises the approach to git contributors based on their commit messages. We train and evaluate the classification model on a large dataset of 6,922 git contributors. The original model based on pull request and issue comments obtained a precision of 0.77 on this dataset, whereas retraining the classification model on git commit messages increased the precision to 0.80. As a proof-of-concept, we implemented this model in BoDeGiC, an open source command-line tool to detect bots in git repositories.

Evaluating a bot detection model on git commit messages

Tom Mens

Is my software ecosystem healthy? It depends!

Tom Mens

Presentation by Mehdi Golzadeh (Software Engineering Lab, University of Mons) of an article published at the 2nd International ICSE Workshop on Bots In Software Engineering (BotSE). See https://doi.org/10.1145/3387940.3391503 Abstract: Many empirical studies focus on socio-technical activity in social coding platforms such as GitHub, for example to study the onboarding, abandonment, productivity and collaboration among team members. Such studies face the difficulty that GitHub activity can also be generated automatically by bots of a different nature. It therefore becomes imperative to distinguish such bots from human users. We propose an automated approach to detect bots in GitHub pull request activity. Relying on the assumption that bots contain repetitive message patterns in their pull request comments, we analyse the similarity between multiple messages from the same GitHub identity, using a clustering method that combines the Jaccard and Levenshtein distance. We empirically evaluate our approach by analysing 20,090 comments of 250 users and 42 bots in 1,262 GitHub repositories. Our results show that the method is able to clearly separate bots from human users.

Bot or not? Detecting bots in GitHub pull request activity based on comment s...

Tom Mens

On the fragility of open source software packaging ecosystems

Tom Mens

How magic is zero? An Empirical Analysis of Initial Development Releases in S...

Tom Mens

This talk reports on our findings based on multiple empirical studies that we have conducted to understand different aspects of dependency management and their practical implications. This includes: * the outdatedness of package dependencies, the transitive impact of such "technical lag", and its relation to the presence of bugs and security vulnerabilities. * the impact of using either more permissive or more restrictive version contraints on dependencies. * the virtues and limitations of being compliant to semantic versioning, a common policy to inform dependents whether new releases of software packages introduce possibly backward incompatible changes. * the impact of specific characteristics, policies and tools used by the packaging ecosystem and its supporting community on all of the above. The contents of the talk is primarily based on the following peer-reviewed scientific articles: * What do package dependencies tell us about semantic versioning? Alexandre Decan, Tom Mens. IEEE Transactions on Software Engineering, 2019. https://doi.org/10.1109/TSE.2019.2918315 * An empirical comparison of dependency network evolution in seven software packaging ecosystems. Alexandre Decan, Tom Mens, Philippe Grosjean. Empirical Software Engineering 24(1):381-416, 2019. https://doi.org/10.1007/s10664-017-9589-y * A formal framework for measuring technical lag in component repositories and its application to npm. Ahmed Zerouali, Tom Mens, Jesus Gonzalez‐Barahona, Alexandre Decan, Eleni Constantinou, Gregorio Robles. Journal of Software: Evolution and Process 31(8), 2019. https://doi.org/10.1002/smr.2157 * On the Impact of Security Vulnerabilities in the npm Package Dependency Network. Alexandre Decan, Tom Mens, Eleni Constantinou. International Conference on Mining Software Repositories, 2018. https://doi.org/10.1145/3196398.3196401 * On the Evolution of Technical Lag in the npm Package Dependency Network. Alexandre Decan, Tom Mens, Eleni Constantinou. International Conference on Software Maintenance and Evolution, 2018. https://doi.org/10.1109/ICSME.2018.00050

Comparing dependency issues across software package distributions (FOSDEM 2020)

Tom Mens

Measuring Technical Lag in Software Deployments (CHAOSScon 2020)

Tom Mens

This presentation reports on the research results achieved in the context of the interuniversity interdisciplinary research project SECOHealth "Vers une méthodologie et analyse socio-technique interdisciplinaire de la santé des écosystèmes logiciels" co-financed by FRS-FNRS Belgium and FRQ (FRSC - FRNT, Québec) with principal investigators Tom Mens (UMONS), Bram Adams (Polytechnique Montréal) and Josianne Marsan (Université Laval).

SecoHealth 2019 Research Achievements

Tom Mens

Introduction to the research seminar on empirical analysis of open source software ecosystems, organised by the SECO-ASSIST "excellence of science" research project, on September 4th, 2019 at the University of Mons, Belgium. With invited presentations by Alexander Serebrenik, Jesus Gonzalez-Barahona, Dario Di Nucci and Henrique Nucci. The seminar concludes with the public PhD defense of Ahmed Zerouali (supervised by Tom Mens) on the topic of "A Measurement Framework for Analyzing Technical Lag in Open-Source Software Ecosystems"

SECO-Assist 2019 research seminar

Tom Mens

Invited presentation at Concordia University (Montreal, Canada) by Eleni Constantinou and Tom Mens on recent research about the socio-technical health issues in software package management ecosystems. Abstract: The large majority of today’s software is relying on open software software components. Such components are typically distributed through package managers for a wide variety of programming languages, and developed and maintained through online distributed software development services like GitHub. Software component repositories are perceived as software ecosystems that constitute complex and evolving socio-technical software dependency networks. Because of their complexity and evolution, these ecosystems tend to suffer from a wide variety of software health issues that can be either technical or social in nature. Examples of such issues include the ecosystem fragility due to exponential growth and transitive dependencies; the abundance of outdated, unmaintained or obsolete software components; the prolonged presence of unfixed bugs and security vulnerabilities; the abandonment or high turnover of key contributors, suboptimal collaboration between contributors, and many more. This presentation will report on our past and ongoing empirical research that studies such health factors within and across different software packaging ecosystems (such as npm, RubyGems, Cargo, CRAN, CPAN). We provide empirical evidence of some of the health problems, compare their presence across different ecosystems, and suggest ways to reduce their potential impact by providing concrete guidelines and tools. The presented research Is being conducted by researchers of the Software Engineering Lab at the University of Mons in the context of two ongoing projects SECOHealth and SECO-ASSIST, aiming to analyse and improve the health of software ecosystems.

Empirically Analysing the Socio-Technical Health of Software Package Managers

Tom Mens

More from Tom Mens (20)

How to be(come) a successful PhD student

Recognising bot activity in collaborative software development

A Dataset of Bot and Human Activities in GitHub

The (r)evolution of CI/CD on GitHub

Nurturing the Software Ecosystems of the Future

Comment programmer un robot en 30 minutes?

On the rise and fall of CI services in GitHub

On backporting practices in package dependency networks

Comparing semantic versioning practices in Cargo, npm, Packagist and Rubygems

Lost in Zero Space

Evaluating a bot detection model on git commit messages

Is my software ecosystem healthy? It depends!

Bot or not? Detecting bots in GitHub pull request activity based on comment s...

On the fragility of open source software packaging ecosystems

How magic is zero? An Empirical Analysis of Initial Development Releases in S...

Comparing dependency issues across software package distributions (FOSDEM 2020)

Measuring Technical Lag in Software Deployments (CHAOSScon 2020)

SecoHealth 2019 Research Achievements

SECO-Assist 2019 research seminar

Empirically Analysing the Socio-Technical Health of Software Package Managers

Recently uploaded

Site Acceptance Test .

Poonam Aher Patil

Grade 7 - Lesson 1 - Microscope and Its Functions

OrtegaSyrineMay

Genetics and epigenetics of ADHD and comorbid conditions

bassianu17

Module for Grade 9 for Asynchronous/Distance learning

levieagacer

Genome sequencing,shotgun sequencing.pptx

Silpa

FAIRSpectra - Enabling the FAIRification of Analytical Science

Alex Henderson

Use of mutants in understanding seedling development.pptx

RenuJangid3

Phenolics: types, biosynthesis and functions.

Silpa

POGONATUM : morphology, anatomy, reproduction etc.

Silpa

Dr. E. Muralinath_ Blood indices_clinical aspects

muralinath2

Atp synthase , Atp synthase complex 1 to 4.

Silpa

Ultrasound color Doppler imaging has been routinely used for the diagnosis of cardiovascular diseases, enabling real-time flow visualization through the Doppler effect. Yet, its inability to provide true flow velocity vectors due to its one-dimensional detection limits its efficacy. To overcome this limitation, various VFI schemes, including multi-angle beams, speckle tracking, and transverse oscillation, have been explored, with some already available commercially. However, many of these methods still rely on autocorrelation, which poses inherent issues such as underestimation, aliasing, and the need for large ensemble sizes. Conversely, speckle-tracking-based VFI enables lateral velocity estimation but suffers from significantly lower accuracy compared to axial velocity measurements. To address these challenges, we have presented a speckle-tracking-based VFI approach utilizing multi-angle ultrafast plane wave imaging. Our approach involves estimating axial velocity components projected onto individual steered plane waves, which are then combined to derive the velocity vector. Additionally, we've introduced a VFI visualization technique with high spatial and temporal resolutions capable of tracking flow particle trajectories. Simulation and flow phantom experiments demonstrate that the proposed VFI method outperforms both speckle-tracking-based VFI and autocorrelation VFI counterparts by at least a factor of three. Furthermore, in vivo measurements on carotid arteries using the Prodigy ultrasound scanner demonstrate the effectiveness of our approach compared to existing methods, providing a more robust imaging tool for hemodynamic studies. Learning objectives: - Understand fundamental limitations of color Doppler imaging. - Understand principles behind advanced vector flow imaging techniques. - Familiarize with the ultrasound speckle tracking technique and its implications in flow imaging. - Explore experiments conducted using multi-angle plane wave ultrafast imaging, specifically utilizing the pulse-sequence mode on a 128-channel ultrasound research platform.

(May 9, 2024) Enhanced Ultrafast Vector Flow Imaging (VFI) Using Multi-Angle ...

Scintica Instrumentation

Proteomics: types, protein profiling steps etc.

Silpa

FAIRSpectra - Enabling the FAIRification of Spectroscopy and Spectrometry

Alex Henderson

Embark on a captivating exploration of the transformative power of biotechnology on economic prosperity and societal advancement in this illuminating presentation. Uncover the multifaceted impacts of biotech breakthroughs across diverse sectors, from bolstering agricultural yields to revolutionizing personalized medicine in healthcare. Delve deep into case studies and real-world examples illustrating how biotechnological innovations serve as catalysts for economic growth and sustainable development. This presentation offers a comprehensive analysis of the strategic imperatives driving the integration of biotechnology into global economies. Discover the pivotal role of public-private partnerships, regulatory frameworks, and investment incentives in fostering an ecosystem conducive to biotech innovation and entrepreneurship. Gain invaluable insights into emerging trends and market dynamics shaping the biotech landscape, from CRISPR gene editing to synthetic biology and beyond. Moreover, explore the ethical, social, and environmental implications inherent in the widespread adoption of biotechnological solutions. Learn how stakeholders navigate complex challenges such as intellectual property rights, biosecurity concerns, and equitable access to biotech advancements while maximizing their positive impact on communities worldwide. Whether you're a seasoned industry professional, an academic researcher, or a policymaker, this presentation promises to deepen your understanding of the pivotal role biotechnology plays in shaping our economic future. Join us on this enlightening journey at the intersection of science, economics, and innovation, and unlock the boundless potential of biotechnology to uplift societies and enhance quality of life on a global scale.

THE ROLE OF BIOTECHNOLOGY IN THE ECONOMIC UPLIFT.pptx

ANSARKHAN96

Human & Veterinary Respiratory Physilogy_DR.E.Muralinath_Associate Professor....

muralinath2

TheCarringtoneventof1859hasbeenthestrongestsolarflareintheobservationalhistory.ItplaysacrucialroleinsheddinglightonthefrequencyandimpactsofthepastandfutureSolarEnergeticParticle(SEP)eventsonhumansocieties.WeaddresstheimpactoftheCarringtoneventbymeasuringtree‐ring14Cwithmultiplereplicationsfromhigh‐latitudelocationsaroundtheeventandbycomparingthemwithmid‐latitudemeasurements.Atransientoffsetin14Cfollowingtheeventisobservedwithhighstatisticalsignificance.Ourstate‐of‐the‐art14Cproductionandtransportmodeldoesnotreproducetheobservationalfinding,suggestingfeaturesbeyondpresentunderstanding.Particularly,ourobservationwouldrequirepartiallyfasttransportof14Cbetweenthestratosphereandtroposphereathighlatitudes.TheobservationisconsistentwiththepreviousfindingswiththeSEPeventsof774and993CEforwhichfasterintegrationof14Cintotreeringsisobservedathighlatitudes

TransientOffsetin14CAftertheCarringtonEventRecordedbyPolarTreeRings

Sérgio Sacani

Reboulia: features, anatomy, morphology etc.

Silpa

CURRENT SCENARIO OF POULTRY PRODUCTION IN INDIA

Dr. TATHAGAT KHOBRAGADE

module for grade 9 for distance learning

levieagacer

Recently uploaded (20)

Site Acceptance Test .

Grade 7 - Lesson 1 - Microscope and Its Functions

Genetics and epigenetics of ADHD and comorbid conditions

Module for Grade 9 for Asynchronous/Distance learning

Genome sequencing,shotgun sequencing.pptx

FAIRSpectra - Enabling the FAIRification of Analytical Science

Use of mutants in understanding seedling development.pptx

Phenolics: types, biosynthesis and functions.

POGONATUM : morphology, anatomy, reproduction etc.

Dr. E. Muralinath_ Blood indices_clinical aspects

Atp synthase , Atp synthase complex 1 to 4.

(May 9, 2024) Enhanced Ultrafast Vector Flow Imaging (VFI) Using Multi-Angle ...

Proteomics: types, protein profiling steps etc.

FAIRSpectra - Enabling the FAIRification of Spectroscopy and Spectrometry

THE ROLE OF BIOTECHNOLOGY IN THE ECONOMIC UPLIFT.pptx

Human & Veterinary Respiratory Physilogy_DR.E.Muralinath_Associate Professor....

TransientOffsetin14CAftertheCarringtonEventRecordedbyPolarTreeRings

Reboulia: features, anatomy, morphology etc.

CURRENT SCENARIO OF POULTRY PRODUCTION IN INDIA

module for grade 9 for distance learning

On the Survival of Database Frameworks in Java Projects

1. ONTHE USE OF DATABASE FRAMEWORKS IN JAVA PROJECTS A LARGE-SCALE HISTORICAL EMPIRICAL ANALYSIS Mathieu Goeminne mathieu.goeminne@umons.ac.be Tom Mens tom.mens@umons.ac.be Software Engineering Lab Alexandre Decan alexandre.decan@umons.ac.be

2. GENERAL CONTEXT • FNRS interuniversity research collaboration with the University of Namur. • Study of software systems that use a database. • Understanding the dynamics, issues and evolution of such systems. • Need to take into account their speciﬁcities: • How is their connection managed? • How do the source code and the database co-evolve? • How can we assess and increase the quality of such systems?

3. DATABASE FRAMEWORKS? .java .jsp .php DBMS ORM Connector Session manager Source code DatabaseFrameworks

4. ONTHIS PRESENTATION • Focus on database frameworks. • Empirical study for answering 3 research questions: • Q1: Which combinations of DB frameworks are being used simultaneously? • Q2: How long do DB frameworks ‘survive’ in the projects that use them? • Q3: Does the introduction of a DB framework inﬂuence the survivability of another one?

5. CASE STUDY • 20 Java DB frameworks. • Top 5 retained: JDBC, Spring, JPA, Vaadin, Hibernate. • 13,307 Java projects from the Github Java Corpus (MSR10): 3,707 of them use at least one retained framework)

6. SURVIVAL ANALYSIS: KAPLAN-MEIER ESTIMATOR • Estimates the survival function of a population • Takes into account right censoring (the event may occur after the last observation) • Mantel-Haenszel test for determining if 2 survival functions differ.

7. Q1 - Which combinations of DB frameworks are being used simultaneously? • In most cases (98%), different frameworks used in a project are used in combination. • JDBC is used as the single DB framework in 56% of all projects. • Most projects (83%) using Hibernate also use JDBC. Hibernate is almost never (3%) used alone. • JDBC used as support for the other FW, providing unique services? # projects using X fw vsY fw simultaneously # projects using X andY simultaneously

8. Q2 - How long do database frameworks ‘survive’ in the projects? • If a framework is introduced, it remains in >45% of all the projects. • Different trends. After 30 days: • Hibernate disappears from 11.7% of projects • Spring disappears from 3.7% of projects • Partial order: JPA and Spring have higher survival rates than JDBC and Hibernate. • No clear relation between the order and the popularity of the considered frameworks. Survival functions of top 5 FW according to Kaplan-Meier estimator p-values for difference tests of survival functions

9. Q3 - Does the introduction of a database framework influence the survivability of another one? • Visually, the introduction of some frameworks seems to have a favorable influence. • After Bonferroni correction, no significant difference in the survival functions… at project level. • In the future: file level analyse. Survival functions of JDBC with and without Spring

10. CONCLUSIONS • Important coexistence • Especially between JDBC and the other considered DB frameworks. • JDBC is still often present in projects despite the use frameworks providing more advanced, higher level services. • In our study, there is no evidence for competition between frameworks. • An introduced framework has an ≳45% of chance that it will remain. • The disappearance of a framework doesn’t seem to be related to the introduction of an other one.

11. FUTURE WORK • Finer granularity: from projects to packages, ﬁles, methods, … • Analysis of (un)frequently used framework services. • Looking for evolutionary patterns: • New frameworks introduced for their unique services? • Simple SQL queries are replaced by framework services, while complex queries remain as it? • Extension to frameworks for less structured databases, NoSQL, etc.

On the Survival of Database Frameworks in Java Projects

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (9)

More from Tom Mens

More from Tom Mens (20)

Recently uploaded

Recently uploaded (20)

On the Survival of Database Frameworks in Java Projects