MétaCan
Menu
Back to cohort
Record W3097833986 · doi:10.1145/3419804.3420267

A Model Traceability Framework for Network Service Management

2020· article· en· W3097833986 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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsToronto Metropolitan UniversityConcordia University
Fundersnot available
KeywordsTraceabilityComputer scienceOrchestrationRequirements traceabilitySoftware engineeringTRACE (psycholinguistics)Process (computing)VisualizationProcess managementSystems engineeringRequirements analysisProgramming languageEngineeringData mining

Abstract

fetched live from OpenAlex

Automating enactment along with traceability management of processes using model-driven engineering methods could be of significant benefit to the Network Functions Virtualization (NFV) paradigm in view of its move towards zero-touch automation of the orchestration and management of network services (NS). Earlier, we proposed an integrated process modelling and enactment environment with traceability support, MAPLE-T, for NS management. In this paper, we extend MAPLE-T with the notion of intents. We propose the usage of intents at both the process model (PM) and model-transformation levels as part of our traceability information. We define intents as information representing the objective of the PM actions/activities and their implementations. We extend MAPLE-T with traceability visualization support to visualize trace links relating models at different levels through the captured intents. The intent-enriched traceability information and the enhanced visualization enable semantically richer traceability analysis. We apply our traceability generation and analysis approach to the NS design process in order to show the benefits of intents not only for the process, but also for the whole NS lifecycle management operations.

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.000
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.606
Threshold uncertainty score0.407

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.046
GPT teacher head0.271
Teacher spread0.224 · 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