MétaCan
Menu
Back to cohort
Record W84004232 · doi:10.11575/prism/2723

Pragmatic software reuse

2008· article· fr· W84004232 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenuePRISM (University of Calgary) · 2008
Typearticle
Languagefr
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsReuseComputer scienceTask (project management)Software engineeringPlan (archaeology)Set (abstract data type)SoftwareSoftware developmentHuman–computer interactionCode (set theory)Systems engineeringProgramming languageEngineering

Abstract

fetched live from OpenAlex

Many software reuse tasks involve reusing source code that was not designed in a reusable manner. These pragmatic reuse tasks arise for a variety of organizational and technical reasons. To investigate a pragmatic reuse task, a developer must navigate through, and reason about, unfamiliar source code in order to identify those program elements that are relevant to his reuse task and to decide how they should be reused. Once these elements have been identified, the developer must convert his mental model of the task into a set of actions he can perform. These tasks are poorly supported by modern development tools and practices. The thesis of this dissertation is that by providing developers with a mechanism to create pragmatic reuse plans in a structured way, and a methodology to semi-automatically perform the pragmatic reuse task using this plan, we can enable developers to perform pragmatic reuse tasks more quickly and with greater confidence. To validate these claims we have created a model that captures the program elements involved in a pragmatic reuse task, along with annotations that correspond to the developer's decisions about how an element should be treated in a reuse task; the model explicitly enumerates each of the actions required to perform a pragmatic reuse task. We have created a tool, called Gilligan, that allows developers to create pragmatic reuse plans by navigating through unfamiliar source code and annotating its structural elements corresponding to how they should be treated in a reuse task. Using this plan, Gilligan can semi-automatically transform the source code from its originating system and integrate it into the developer's system. We have evaluated Gilligan using a series of case studies and experiments using a variety of source systems and tasks. The results show that pragmatic reuse plans are a robust metaphor for capturing pragmatic reuse intent and that Gilligan can significantly decrease the amount of time developers require to perform pragmatic reuse tasks.

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.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.711
Threshold uncertainty score1.000

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.001
Science and technology studies0.0000.001
Scholarly communication0.0000.001
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.001

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.021
GPT teacher head0.213
Teacher spread0.192 · 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