MétaCan
Menu
Back to cohort
Record W2137260567 · doi:10.2308/isys-50913

Addressing the Control Challenges of the Enterprise Architecture Process

2014· article· en· W2137260567 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

VenueJournal of Information Systems · 2014
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInformation Technology Governance and Strategy
Canadian institutionsQueen's University
Fundersnot available
KeywordsEnterprise architectureEnterprise architecture managementEnterprise architecture frameworkArchitectureKnowledge managementProcess managementEnterprise life cycleComputer scienceProcess (computing)COBITNIST Enterprise Architecture ModelBusiness architectureView modelEnterprise integrationControl (management)BusinessEnterprise softwareBusiness processSystems architectureWork in processMarketingArtificial intelligence

Abstract

fetched live from OpenAlex

ABSTRACT This paper examines the enterprise architecture process from the perspective of information systems controls, which refer to attempts to influence the behavior of employees in order to achieve organizational goals. Although controls have been extensively studied in processes such as systems development, there is little research examining control within the enterprise architecture process, despite its rising importance in today's organizations. This paper examines how enterprise architecture controls are employed in practice and considers the challenges faced in their design and operation. Drawing on empirical data from two in-depth case studies, enterprise architecture controls are classified and analyzed using COBIT 5. Our findings identify a series of specific challenges with enterprise architecture controls. Based on these challenges, we outline recommendations to practitioners in overseeing the enterprise architecture process and develop propositions to help guide future research initiatives to enhance enterprise architecture performance.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.736
Threshold uncertainty score0.159

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.002
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.230
Teacher spread0.211 · 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