23
A Delta Oriented Approach to the Evolution and Reconciliation of Enterprise Software Product Lines Federal University of Rio Grande do Norte, Natal-RN, Brazil Department of Informatics and Applied Mathematics Informatics Superintendence Gleydson Lima, Jadson Santos, Uirá Kulesza, Daniel Alencar and Sergio Fialho ICEIS 2013 - 15 th International Conference on Enterprise Information Systems

ICEIS 2013 Presentation

Embed Size (px)

Citation preview

A Delta Oriented Approach to the Evolution and Reconciliation of

Enterprise Software Product Lines

Federal University of Rio Grande do Norte, Natal-RN, Brazil Department of Informatics and Applied Mathematics

Informatics Superintendence

Gleydson Lima, Jadson Santos, Uirá Kulesza, Daniel Alencar and Sergio Fialho

ICEIS 2013 - 15th International Conference on Enterprise Information Systems

Motivation

� Traditional SPL Development

2

Motivation

� Traditional Development Scenario

Asset Inputs

Product Derivation

3

Product 1

Product 2

Product 3

Product n

Configuration Knowledge

Variabilities

Motivation

� There are industrial scenarios where traditional SPL processes do not work! ◦ Distributed and separate development teams ◦ Great demand for changing

�  Several existing research works describe these alternative scenarios

4

Motivation

� Alternative Development Scenario

SPL 1.1

Fork Partial Reconciliation

Source SPL

Target SPL

SPL 1.0 SPL 1.1

SPL 1.2 SPL 2.1

5

Overlap !

SPL 1.5

Motivation

� Code conflicts when integrating features from SPLs that evolved independently

6

Limitations of existing tools

7

� Configuration Management Systems + Change Request Systems

Limitations of existing work

�  (Rubin et al, 2012) propose the improvement of the efficiency of forking practices, but they have not developed a concrete implementation

�  (Nunes et al, 2010) analyze the historical evolution by identifying how each feature has evolved, but they do not promote the merge of these evolutions

8

Motivation Limitations of existing work Approach Overview Approach In Action Conclusions and Future Work

9

Approach Overview

� The main aim of our approach is to promote the reconciliation of SPLs that are independently evolved from an initial version

10

Approach Overview

11

1.0 2.0 3.0

Change Log Change Log

1.0 1.5 2.3

Source SPL

Target SPL

Change Log Change Log

CMS + CRS

CMS + CRS

Delta Model

Conflict analysis

Approach Overview

� Provide a structured high level view of changes and conflicts to the user

12

Motivation Limitations of existing work Approach Overview Approach In Action Conclusions and Future Work

13

Approach In Action �  It calculates the dependencies between

classes implementing features in order to decide what merge strategy to adopt: ◦ Automatic ◦  Semi-automatic ◦ Manual

14

Approach In Action � Case Study – SIGAA/UFRN ◦ The enterprise information system

responsible for the management of academic activities at the UFRN (1.000.000 loc)

◦ We evaluated a scenario of evolution in features from the SIGAA Library Management System Module (100.000 loc)

15

Punishment

Approach In Action

Source SPL

Target SPL

�  SIGAA Library Management System Feature Model evolution

16

SIGAA

Library

Suspension …

SIGAA

Library

Suspension …

Reservation

Suspension

SIGAA

Library

Suspension Fine

Punishment

SIGAA

Library

Suspension Fine

Reservation

Approach In Action

Domain Layer LibraryUser

GUI Layer RequestReservationMBean

Source SPL Target SPL

� Automatic Strategy

Not Changed

Changed

17 Suspension Reservation Punishment

Domain Layer LibraryUser

GUI Layer MaterialDetailsMBean

Approach In Action

GUI Layer MaterialDetailsMBean

Source SPL Target SPL

Persistence Layer LoanDAO

�  Semi-automatic Strategy

18 Suspension Reservation Punishment

Not Changed

Changed

Business Layer Business Layer

Approach In Action

Source SPL Target SPL

LoanProcessor

� Manual Strategy

19 Suspension Reservation Punishment

Not Changed

Changed

LoanProcessor

Motivation Limitations of existing work Approach Overview Approach In Action Conclusions and Future Work

20

� We have generated an initial version of the tool and apply it at some isolated scenarios for validation

� We are refining the current implementation ◦ Mining feature evolution from CMS instead

source code annotation (less intrusive) ◦ Development a more complete study to

classify types of evolution and conflicts ... and quantify the efficiency of our approach

Conclusions and Future Work

21

Thank You

22

A Delta Oriented Approach to the Evolution and Reconciliation of

Enterprise Software Product Lines

Federal University of Rio Grande do Norte, Natal-RN, Brazil Department of Informatics and Applied Mathematics

Informatics Superintendence

Gleydson Lima, Jadson Santos, Uirá Kulesza, Daniel Alencar and Sergio Fialho

ICEIS 2013 - 15th International Conference on Enterprise Information Systems