MétaCan
Menu
Back to cohort

Combination of connectors with loosely coupled architecture based on aspect-oriented computing

2012· article· en· W2102705096 on OpenAlex
Hamid Mcheick, Yan Qi

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversité du Québec à Chicoutimi
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsComputer scienceSoftware architectureDistributed computingSoftware systemComponent-based software engineeringProcess (computing)SoftwareSoftware engineeringOperating system

Abstract

fetched live from OpenAlex

Software architecture has a vital role in achieving quality goals for large scale software systems which is made up of components and connectors. For reducing the complexity of software, components and connectors are applied to understanding, designing, and implementing software, especially connectors residing in distributed systems. To satisfy requirements of interaction between various components, it is time and cost consuming process to create a connector. In particular, it is often difficult to select only one type of connector to develop connectors in distributed systems. To address the difficulties, our research focuses on the issue: how do traditional types of connectors, in combination with new technologies in distributed systems, provide systems architectures with loosely coupled structures. In this paper, we propose an approach to the combination of connectors in order to provide distributed systems with loosely coupled interaction. Our approach involves AOP technology and design pattern, as well as messaging systems. In the end, we present an example of our approach in which we show a connector designed by combining the AspectJ, shared memory, UDP Socket and publish-subscribe design pattern with the aim of designing a loosely coupled system architecture.

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: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.476
Threshold uncertainty score0.456

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.0000.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.019
GPT teacher head0.259
Teacher spread0.240 · 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