MétaCan
Menu
Back to cohort
Record W2109672042 · doi:10.1109/aiccsa.2008.4493638

Delegation model for object-oriented systems

2008· article· en· W2109672042 on OpenAlexafffund
Hamid Mcheick, Hafedh Mili, Eric Dallaire, Rakan Mcheik

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
KeywordsCommon Object Request Broker ArchitectureDelegationComputer scienceObject (grammar)MethodDistributed objectInteroperable Object ReferenceSet (abstract data type)Object modelFunction (biology)Object-oriented programmingDistributed computingSoftware engineeringProgramming languageComputer securityArtificial intelligence

Abstract

fetched live from OpenAlex

In wide-enterprise information system, an object can change its behaviors and play different roles in their lifecycle. Each client program needs to access different pieces/views of the same domain object. Our approach, called distributed view programming, tries to address both problems and in particular, we address delegation problem in view-based systems. At any given point of time, an object offers a different set of behaviors depending of the active views in that time. Therefore, a client/application user may select a subset of existing functionalities of that object. The core object forwards a function call to a view that has to return it to core object. In distributed platforms, there is no need to support delegation in EJB Corba or .Net because the separation of an object and its aspects doesn't exist. We discuss the delegation model and security issues.

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.005
metaresearch head score (Gemma)0.007
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: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.005
Threshold uncertainty score0.026

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0050.007
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0020.004
Scholarly communication0.0050.010
Open science0.0020.004
Research integrity0.0030.004
Insufficient payload (model declined to judge)0.0050.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.082
GPT teacher head0.293
Teacher spread0.212 · 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

Citations0
Published2008
Admission routes2
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207