MétaCan
Menu
Back to cohort
Record W2043022209 · doi:10.1109/iri.2013.6642473

Detecting distributed software components that will not cause emergent behavior in asynchronous communication style

2013· article· en· W2043022209 on OpenAlexafffund
Fatemeh H. Fard, Behrouz H. Far

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Calgary
FundersAlberta Innovates - Technology Futures
KeywordsAsynchronous communicationComputer scienceScalabilityDistributed computingSoftware deploymentSoftwareScale (ratio)Software engineeringComputer networkOperating system

Abstract

fetched live from OpenAlex

In distributed software systems (DSS) the functionality and/or control are distributed. This may cause the DSS components to show an unexpected behavior known as emergent behavior in the run time, which was not seen in their requirements and design. Emergent behaviors can have irreparable damages for companies. The savings in cost of detecting and fixing emergent behaviors in early phases is more than 20 times compared to fixing them after the deployment. The detecting methodologies usually utilize behavioral modeling which can face to state space explosion problem for large scale systems. Therefore, we approach this problem by detecting components that will not show emergent behavior and remove them from further analysis to help the scalability of these approaches. Previously, we have devised and implemented the algorithm for synchronous communications. In this paper, the extension of our method for detecting these components in the asynchronous communication style is presented which is closer to the real-world systems. The details of the technique and related algorithms are discussed.

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.001
metaresearch head score (Gemma)0.012
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.001
Threshold uncertainty score0.007

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.012
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.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.067
GPT teacher head0.295
Teacher spread0.228 · 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 designTheoretical or conceptual
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
Published2013
Admission routes2
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207