MétaCan
Menu
Back to cohort
Record W7100081872

THE UNIVERSITY OF CALGARY Improving the Modularity of Context-Sensitive Concerns through the Use of Declarative Event Patterns

2005· article· en· W7100081872 on OpenAlexaboutno aff

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsnot available
Fundersnot available
KeywordsEvent (particle physics)Modularity (biology)Protocol (science)MaintainabilitySoftwareCommunications protocolProtocol analysisAbstraction
DOInot available

Abstract

fetched live from OpenAlex

Software modules communicate with one another to form coherent software systems. In order to facilitate this interaction, knowledge of the communication protocol is split up and embedded in each participating module, making local reasoning about the protocol difficult. Modules themselves become collectively responsible for seeing that the appropriate sequence of messages transpires. With protocols scattered in this way, and tangled amongst the details that intrinsically belong inside modules, the traceability, comprehensibility, and maintainability of the concern they represent, and of the system as a whole, tend to suffer. Declarative event patterns (DEPs) are a means to implement communication pro-tocols between modules in a localized manner. DEPs describe sequences of events in the execution of a system and include the ability to recognize properly nested structures. They allow a developer to describe a protocol at a high level, without the need to express extraneous details. A developer can indicate that specific actions be taken when a given pattern occurs. Protocol patterns are automatically translated

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.006
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.107
Threshold uncertainty score0.265

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.006
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.002
Science and technology studies0.0030.002
Scholarly communication0.0060.003
Open science0.0020.004
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0790.020

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.081
GPT teacher head0.282
Teacher spread0.201 · 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 designBench or experimental
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

Citations0
Published2005
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207