MétaCan
Menu
Back to cohort
Record W2613262537 · doi:10.5220/0006350701440157

A Change Impact Analysis Model for Aspect Oriented Programs

2017· article· en· W2613262537 on OpenAlexaff
Fabrice Déhoulé, Linda Badri, Mourad Badri

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversité du Québec
Fundersnot available
KeywordsAspectJAspect-oriented programmingComputer scienceChange impact analysisObject-oriented programmingSeparation of concernsProgramming languageSoftware engineeringSource codeSoftwareRegression testingSoftware developmentSoftware construction

Abstract

fetched live from OpenAlex

Software change impact analysis (IA) plays a crucial role in software evolution. IA aims at identifying the possible effects of a source code modification. It is often used to evaluate the effects of a change after its implementation. However, more proactive approaches use IA to predict the potential effects of a change before it is implemented. In this way, IA provides useful information that can be used, among others, to guide the implementation of the change and to support regression tests selection. This paper aims at proposing a change impact analysis model for AspectJ programs. Aspect-Oriented Programming (AOP) is a natural extension of Object-Oriented Programming (OOP). It particularly promotes improved separation of crosscutting concerns into single units called aspects. The IA techniques proposed for object-oriented programs are not directly applicable for aspect-oriented programs due to the new dependencies introduced by aspects. The proposed model was designed to particularly support predictive IA. The model includes several impact rules based on the AspectJ language constructs. We performed an empirical evaluation of the model using several AspectJ programs. In order to assess the model prediction quality, we used two traditional measures: precision and recall. The reported results show that the model is able to achieve high accuracy.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.646
Threshold uncertainty score0.397

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.199
GPT teacher head0.405
Teacher spread0.205 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations1
Published2017
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207