Co-Evolving Code-Related and Database-Related Changes in a Data-Intensive Software System

Size: px

Start display at page:

Download "Co-Evolving Code-Related and Database-Related Changes in a Data-Intensive Software System"

Marcus Sutton
5 years ago
Views:

Co-Evolving Code-Related and Database-Related Changes in a Data-Intensive Software System Mathieu Goeminne, Alexandre Decan, Tom Mens Service de Génie Logiciel, Université de Mons!

1 Co-Evolving Code-Related and Database-Related Changes in a Data-Intensive Software System Mathieu Goeminne, Alexandre Decan, Tom Mens Service de Génie Logiciel, Université de Mons! FNRS Projet de Recherche Data-Intensive Software System Evolution in collaboration with A. Cleve and L. Meurice (Université de Namur)

2 Context Focus on data-intensive software systems (DISS) Expand empirical MSR research to include database-related activities Study co-evolution between code and database Carry out empirical studies on open source DISS 2

3 Research Questions RQ1: Is there any relation between how source code files and database-related files evolve? RQ2: What is the effect of migrating to new database technology? RQ3: How do developers divide their work and how does this evolve over time? 3

4 Case Study: OSCAR Canadian research network SCOOP Social Collaboratory for Outcome Oriented Primary care Open source tool infrastructure for Electronic Medical Records (EMR) OSCAR: EMR system for healthcare Support for billing, chronic disease management tools, prescription module, scheduling,... Data available on 4

5 Case Study: OSCAR characteristic value duration 3,939 days ( > 129 months) dates from Nov 2002 till Aug 2013 # of commits 18,727 # of distinct files 20,718 (54% are code files) # of file touches 93,721 # of distinct developers 100 5

6 Evolution of OSCAR Monthly aggregated proportion of JSP and Java files in OSCAR 100%# 90%# 80%# 70%# 60%# 50%# 40%# 30%# 20%# 10%# 0%# # # # # # # # # # # # # # # # # # # # jsp# java# # 6

7 Evolution of OSCAR - Social Dimension Monthly number of distinct active developers for OSCAR 25" 20" 15" 10" 5" 0" 2003'07" 2004'01" 2004'07" 2005'01" 2005'07" 2006'01" 2006'07" 2007'01" 2007'07" 2008'01" 2008'07" 2009'01" 2009'07" 2010'01" 2010'07" 2011'01" 2011'07" 2012'01" 2012'07" 2013'01" 7

8 Evolution of OSCAR Growth of source code files and database-related files 6000" 5000" 4000" pure" sql" 3000" 2000" 1000" 0" 2003)07" 2004)01" 2004)07" 2005)01" 2005)07" 2006)01" 2006)07" 2007)01" 2007)07" 2008)01" 2008)07" 2009)01" 2009)07" 2010)01" 2010)07" 2011)01" 2011)07" 2012)01" 2012)07" 2013)01" 8

9 Evolution of OSCAR - Social Dimension How does the activity of developers evolve over time? Developer 9

10 Introduction of Persistence Provider Hibernate (introduced in OSCAR since July 2006) Java object-relational mapping (ORM) library XML files map Java classes to database tables and Java data types to SQL data types facilitates data query and retrieval generates SQL calls and relieves the developer from manual result set handling and object conversion JPA (introduced in OSCAR since July 2008) Java Persistence API Uses Java annotations instead of XML files for ORM 10

Introduction of Persistence Provider SQL = code file containing embedded SQL query HIB = Java file targeted by Hibernate XML file JPA = Java file containing JPA annotation pure = code files not

2007-07-01# 2008-01-01# 2008-07-01# 2009-01-01# 2009-07-01# 2010-01-01# 2010-07-01# 2011-01-01# 2011-07-01# 2012-01-01# 2012-07-01# 2013-01-01# 2013-07-01# 1600" 1400" 1200" 1000" 800" 600" 400" 200"

11 Introduction of Persistence Provider SQL = code file containing embedded SQL query HIB = Java file targeted by Hibernate XML file JPA = Java file containing JPA annotation pure = code files not containing any of these 100%# 90%# 80%# 70%# 60%# 50%# 40%# 30%# 20%# 10%# 0%# JPA# SQL# HIB# pure# # # # # # # # # # # # # # # # # # # # # # 1600" 1400" 1200" 1000" 800" 600" 400" 200" 0" JPA" HIB" SQL" 2003)07)01" 2003)11)01" 2004)03)01" 2004)07)01" 2004)11)01" 2005)03)01" 2005)07)01" 2005)11)01" 2006)03)01" 2006)07)01" 2006)11)01" 2007)03)01" 2007)07)01" 2007)11)01" 2008)03)01" 2008)07)01" 2008)11)01" 2009)03)01" 2009)07)01" 2009)11)01" 2010)03)01" 2010)07)01" 2010)11)01" 2011)03)01" 2011)07)01" 2011)11)01" 2012)03)01" 2012)07)01" 2012)11)01" 2013)03)01" 2013)07)01" Monthly aggregated number of active files 11

12 Introduction of Persistence Provider Who is involved in introducing changes in database-related code? Developer 12

13 Evolution of OSCAR - Social Dimension How do developers divide their work? Java$(87)$ OSCAR$developers$(100)$ 3" 24" JSP$(86)$ 24" 10" 10" HIB$ JPA$ 8" 9" 11" 1" 0" SQL$(53)$ Number of developers that introduce database-related code in some file for the first time 13

14 Preliminary Conclusions RQ1: Code-related and database-related files evolve together (no phased co-evolution)! RQ2: Migration to Hibernate, then JPA, but embedded SQL still remains important! RQ3: No clear separation of activities between developers The majority of developers changes both db-related and db-unrelated code No observed periods dedicated to a specific activity 14

15 Future Work Continue studying co-evolution between coderelated and db-related changes Refine our results by analysing changes at finer granularity Analyse database schema changes and their impact on source code (collaboration with UNamur) Detect change patterns in code and database schema Study impact of introducing persistence providers Analyse migration patterns in code How do persistence providers reduce impact of changes in database schema? Study and compare with other DISS 15

Analyzing the Evolution of Database Usage in Data-Intensive Software Systems

Analyzing the Evolution of Database Usage in Data-Intensive Software Systems Loup Meurice, Mathieu Goeminne, Tom Mens, Csaba Nagy, Alexandre Decan, and Anthony Cleve February 19, 2016 Abstract This chapter