Benjamin Benni
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Benjamin Benni has a total of 9 co-authors. Here are the top co-authors by number of shared publications:
Michel Riveill
Computer Science, SPARKS Université Côte d'Azur, CNRS, I3S Nice France
2 shared publicationsNaouel Moha
Université du Québec à Montréal Montréal, Québec Canada
2 shared publicationsSébastien Mosser
Université Côte d’Azur, CNRS, I3S
2 shared publications- Sébastien Mosser
McMaster Centre for Software Certification (McSCert), McMaster University, Hamilton, ON, Canada
2 shared publications Anne-Marie Pinna-Déry
Université Côte d’Azur, CNRS, I3S
1 shared publicationGuilhem Molines
Université Côte d’Azur, CNRS, I3S
1 shared publication
Latest Publications
- Open Access
- 1 January 2020
- Published by AITO - Association Internationale pour les Technologies Objets in The Journal of Object Technology
- Vol. 19 (2) , 7:1
Characterizing Black-box Composition Operators via Generated Tailored Benchmarks.
- 1 January 2020
- Published by AITO - Association Internationale pour les Technologies Objets in The Journal of Object Technology
- Vol. 19 (2) , 7:1
Open AccessCharacterizing Black-box Composition Operators via Generated Tailored Benchmarks.
- 12 August 2019
- Published by Wiley in Journal of Software: Evolution and Process
- Vol. 31 (8) , e2208
A delta‐oriented approach to support the safe reuse of black‐box code rewriters
Large‐scale corrective and perfective maintenance is often automated thanks to rewriting rules using tools such as Python2to3, Spoon, or Coccinelle. Such tools consider these rules as black‐boxes and compose multiple rules by chaining them: giving the output of a given rewriting rule as input to the next one. It is up to the developer to identify the right order (if it exists) among all the different rules to yield the right program. In this paper, we define a formal model compatible with the black‐box assumption that reifies the modifications (Δs) made by each rule. Leveraging these Δs, we propose a way to safely compose multiple rules when applied to the same program by (a) ensuring the isolated application of the different rules and (b) identifying unexpected behaviors that were silently ignored before. We assess this approach on two large‐scale case studies: (a) identifying conflicts in the Linux source‐code automated maintenance and (b) fixing energy antipatterns existing in Android applications available on GitHub.
- 12 August 2019
- Published by Wiley in Journal of Software: Evolution and Process
- Vol. 31 (8) , e2208
A delta‐oriented approach to support the safe reuse of black‐box code rewriters
Large‐scale corrective and perfective maintenance is often automated thanks to rewriting rules using tools such as Python2to3, Spoon, or Coccinelle. Such tools consider these rules as black‐boxes and compose multiple rules by chaining them: giving the output of a given rewriting rule as input to the next one. It is up to the developer to identify the right order (if it exists) among all the different rules to yield the right program. In this paper, we define a formal model compatible with the black‐box assumption that reifies the modifications (Δs) made by each rule. Leveraging these Δs, we propose a way to safely compose multiple rules when applied to the same program by (a) ensuring the isolated application of the different rules and (b) identifying unexpected behaviors that were silently ignored before. We assess this approach on two large‐scale case studies: (a) identifying conflicts in the Linux source‐code automated maintenance and (b) fixing energy antipatterns existing in Android applications available on GitHub.
- 17 April 2018
- Published by Springer Nature
- p. 164-180
A Delta-Oriented Approach to Support the Safe Reuse of Black-Box Code Rewriters
- 17 April 2018
- Published by Springer Nature
- p. 164-180
A Delta-Oriented Approach to Support the Safe Reuse of Black-Box Code Rewriters