MétaCan
Menu
Back to cohort
Record W1982990420 · doi:10.1109/ictai.2010.29

A Technique and a Tool to Detect Emergent Behavior of Distributed Systems Using Scenario-Based Specifications

2010· article· en· W1982990420 on OpenAlexaff
Mohammad Moshirpour, Abdolmajid Mousavi, Behrouz H. Far

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsComputer scienceDistributed computingTask (project management)RoboticsArtificial intelligenceSequence (biology)SoftwareSoftware engineeringSystems engineeringRobotEngineeringProgramming language

Abstract

fetched live from OpenAlex

Distributed systems are employed in countless applications such as information systems, robotics, etc. Lack of central control makes the design of such systems a challenging task because of possible unwanted behavior at runtime, commonly known as emergent behavior. Developing a methodology to detect emergent behavior in the pre-implementation stages of the software development life-cycle of distributed systems can potentially lead to huge savings in time and cost. Moreover, due to the typical large size of the modern distributed systems, automating the detection methodology is considered greatly beneficial. An effective and efficient approach for the design of distributed systems is to describe system requirements using scenarios. A scenario, commonly known as a message sequence chart (MSC), is a temporal sequence of messages sent between system components. However, scenario-based specifications may contain subtle deficiencies with respect to analysis and validation known as incompleteness and partial description. In this research, a tool to automatically detect emergent behavior of scenario-based specification of distributed systems is developed and demonstrated using a robotics example.

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.003
metaresearch head score (Gemma)0.011
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: Methods · Consensus signal: Methods
Teacher disagreement score0.004
Threshold uncertainty score0.016

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.011
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0030.001
Science and technology studies0.0010.001
Scholarly communication0.0020.003
Open science0.0020.002
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0040.002

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.077
GPT teacher head0.316
Teacher spread0.239 · 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
GenreMethods

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

Citations20
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207