MétaCan
Menu
Back to cohort
Record W2023026552 · doi:10.1109/apsec.2012.109

Architecture Based Development with DYNACOMM: Incorporating Dynamic Reconfiguration and Hierarchical Design into CommUnity

2012· article· en· W2023026552 on OpenAlex

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.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsMcMaster UniversityStatistics Canada
Fundersnot available
KeywordsComputer scienceControl reconfigurationComponent (thermodynamics)Architecture description languageSoftware architectureSoftware architecture descriptionSoftware engineeringReference architectureComponent-based software engineeringProgramming languageSoftware systemDistributed computingSoftwareEmbedded system

Abstract

fetched live from OpenAlex

Architecture Description Languages (ADLs) were developed to support the abstract level of software structuring that is the subject matter of software architecture. Community is an ADL built on co-ordination principles and a categorical framework to support the composition of specifications of components to form the system's specification. However, an important shortcoming of Community is the lack of integrated support for specifying the system's architectural changes in both the set of components and the connections between them. This paper presents DynaComm, an extension of Community to support hierarchical design and dynamic reconfiguration of component based systems. The architectural design principles supported by the DynaComm language are illustrated through the design of a fault-tolerant, dynamic client-server system. A state anchored semantics of DynaComm is given by reducing a DynaComm design to a Community design, i.e., a configuration of components, cables and superposition morphisms, and then taking the colimit of the Community diagram. The careful use of extension, refinement and superposition morphisms guarantees that this is always possible.

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.001
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: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.799
Threshold uncertainty score0.479

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.041
GPT teacher head0.275
Teacher spread0.234 · 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