MétaCan
Menu
← Back to cohort
Record W2731817361 · doi:10.4050/f-0073-2017-12033

Benefits and Limitations of Reliance on an Open Architecture Technical Standard to Meet Expectations of an Open System

2017· article· en· W2731817361 on OpenAlexaff
Thomas A. DuBois, Scott Wigginton

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsArchitectureOpen architectureComputer scienceOpen sourceOperating systemSoftware

Abstract

fetched live from OpenAlex

The US Army, Boeing, Sikorsky, Lockheed Martin and other partners conducted independent demonstrations on use of open architecture technical standards can be used to create an open system that meets the expectations identified in the Modular Open System Approach to achieve the benefits of the United States Department of Defense Better Buying Power initiative. This paper presents previously unreleased results and lessons learned from mission system experiments using the Future Airborne Capability Environment (FACETM) Technical Standard and the Army's Joint Common Architecture (JCA). The results show how to apply the FACE standard to address the expectations of an open system while identifying the potential to align with the open standard without achieving the expected benefits. This paper aims to inform acquisition authorities about the technical considerations of open architecture procurements, to provide guidance on how to apply emergent open architecture standards, and address actual or perceived gaps between meeting the requirements of an open standard and achieving the goals of procuring an open system.

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.087
metaresearch head score (Gemma)0.126
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: Empirical
Teacher disagreement score0.087
Threshold uncertainty score0.459

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0870.126
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.001
Science and technology studies0.0030.007
Scholarly communication0.0090.016
Open science0.0020.007
Research integrity0.0020.005
Insufficient payload (model declined to judge)0.0020.001

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.076
GPT teacher head0.349
Teacher spread0.273 · 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
Published2017
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Research→French-language works237,207→