MétaCan
Menu
Back to cohort
Record W4246883339 · doi:10.22215/etd/2014-10588

Mapping ACL to JavaMOP: A Feasibility Study

2014· dissertation· en· W4246883339 on OpenAlexaff
Joshua Beltramin

Bibliographic record

Venuenot available
Typedissertation
Languageen
FieldComputer Science
TopicSoftware Testing and Debugging Techniques
Canadian institutionsCarleton University
Fundersnot available
KeywordsUSableSuiteComputer scienceSoftware engineeringTest suiteDebuggingJavaTest caseProgramming languageReliability engineeringEngineeringMachine learningWorld Wide Web

Abstract

fetched live from OpenAlex

Model-based testing (MBT) is a quality assurance technique where a test suite is generated from an abstract model.There are a number of different approaches to accomplish model-based testing.While state-based techniques dominate, they have a number of inherent issues.These issues have led to the pursuit of alternatives such as scenario-based approaches.ACL/VF is one such scenario-based approach.Developed by Dr. Corriveau and his students, the ACL/VF system provides both a language to specify an implementation-independent testable model of a specification and the tool to validate an implementation against this model.However, the current implementation of ACL/VF has a number of issues that prevent it from being a usable solution.In particular, the current version of ACL/VF is extremely .NET3.5 specific.Unfortunately, upgrading it to a more recent version of .NET essentially amounts to a complete rewrite.Given the widespread use of Java, a most immediate research question is to determine whether or not it is feasible to reimplement ACL/VF on that platform.Our claim is that this reimplementation can be accomplished through a mapping from ACL specifications to JavaMOP monitor specifications.The following thesis provides two case studies supporting this claim as well as an element-by-element proposed mapping.

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.011
metaresearch head score (Gemma)0.029
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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.014
Threshold uncertainty score0.056

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0110.029
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0020.004
Open science0.0030.001
Research integrity0.0020.001
Insufficient payload (model declined to judge)0.0140.003

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.042
GPT teacher head0.330
Teacher spread0.288 · 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

Citations2
Published2014
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Testing and Debugging TechniquesFrench-language works237,207