MétaCan
Menu
Back to cohort
Record W4210477369 · doi:10.21203/rs.3.rs-1264268/v1

Applying Declarative Analysis to Industrial Automotive Software Product Line Models

2022· preprint· en· W4210477369 on OpenAlexaff
Ramy Shahin, Rafael Toledo, Robert Hackman, S. Ramesh, Joanne M. Atlee, Marsha Chećhik

Bibliographic record

VenueResearch Square · 2022
Typepreprint
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of WaterlooUniversity of Toronto
Fundersnot available
KeywordsAutomotive industryProduct lineSoftware product lineComputer scienceProduct (mathematics)SoftwareSoftware engineeringManufacturing engineeringProgramming languageEngineeringSoftware developmentMathematics

Abstract

fetched live from OpenAlex

Abstract Software Product Lines (SPLs) are families of related software products developed from a common set of artifacts. Most existing analysis tools cannot be applied to an entire SPL, but rather must be applied an SPL’s products one at a time. Some tools have been redesigned or re-implemented to support the kind of variability exhibited in SPLs, but this usually takes a lot of effort and is error-prone. Declarative analyses written in languages like Datalog have been collectively lifted to SPLs in prior work, which enables the application of existing declarative analyses to SPLs.In this paper, we apply five declarative analyses (behaviour alteration, re-cusion analysis, simplifiable global variable analysis, and two of their variants) to a set of automotive software product lines from General Motors. We discuss the design of the analysis pipeline used in this process, present its scalability results, and provide a means to visualize the analysis results for a subset of products filtered by feature expression. We also reflect on some of the lessons learned throughout this project.

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 machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.009
Threshold uncertainty score0.018

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.005
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.001
Science and technology studies0.0000.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.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.331
GPT teacher head0.457
Teacher spread0.126 · 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 source (direct Gemma or distilled Codex), not a consensus.

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

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
Published2022
Admission routes1
Has abstractyes

Explore more

Same venueResearch SquareSame topicAdvanced Software Engineering MethodologiesFrench-language works237,207