MétaCan
Menu
Back to cohort
Record W4377200823 · doi:10.28945/5113

Analysis of the Scale Types and Measurement Units in Enterprise Architecture (EA) Measurement

2023· article· en· W4377200823 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

VenueInterdisciplinary Journal of Information Knowledge and Management · 2023
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInformation Technology Governance and Strategy
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsContext (archaeology)Computer scienceMetrologyMeasure (data warehouse)Empirical researchMeasurement uncertaintyScale (ratio)CredibilityPerformance measurementLevel of measurementRisk analysis (engineering)Industrial engineeringManagement scienceOperations researchData miningMathematicsEngineeringStatistics

Abstract

fetched live from OpenAlex

Aim/Purpose: This study identifies the scale types and measurement units used in the measurement of enterprise architecture (EA) and analyzes the admissibility of the mathematical operations used. Background: The majority of measurement solutions proposed in the EA literature are based on researchers’ opinions and many with limited empirical validation and weak metrological properties. This means that the results generated by these solutions may not be reliable, trustworthy, or comparable, and may even lead to wrong investment decisions. While the literature proposes a number of EA measurement solutions, the designs of the mathematical operations used to measure EA have not yet been independently analyzed. It is imperative that the EA community works towards developing robust, reliable, and widely accepted measurement solutions. Only then can senior management make informed decisions about the allocation of resources for EA initiatives and ensure that their investment yields optimal results. Methodology: In previous research, we identified, through a systematic literature review, the EA measurement solutions proposed in the literature and classified them by EA entity types. In a subsequent study, we evaluated their metrology coverage from both a theoretical and empirical perspective. The metrology coverage was designed using a combination of the evaluation theory, best practices from the software measurement literature including the measurement context model, and representational theory of measurement to evaluate whether EA measurement solutions satisfy the metrology criteria. The research study reported here presents a more in-depth analysis of the mathematical operations within the proposed EA measurement solutions, and for each EA entity type, each mathematical operation used to measure EA was examined in terms of the scale types and measurement units of the inputs, their transformations through mathematical operations, the impact in terms of scale types, and measurement units of the proposed outputs. Contribution: This study adds to the body of knowledge on EA measurement by offering a metrology-based approach to analyze and design better EA measurement solutions that satisfy the validity of scale type transformations in mathematical operations and the use of explicit measurement units to allow measurement consistency for their usage in decision-making models. Findings: The findings from this study reveal that some important metrology and quantification issues have been overlooked in the design of EA measurement solutions proposed in the literature: a number of proposed EA mathematical operations produce numbers with unknown units and scale types, often the result of an aggregation of undetermined assumptions rather than explicit quantitative knowledge. The significance of such aggregation is uncertain, leading to numbers that have suffered information loss and lack clear meaning. It is also unclear if it is appropriate to add or multiply these numbers together. Such EA numbers are deemed to have low metrological quality and could potentially lead to incorrect decisions with serious and costly consequences. Recommendations for Practitioners: The results of the study provide valuable insights for professionals in the field of EA. Identifying the metrology limitations and weaknesses of existing EA measurement solutions may indicate, for instance, that practitioners should wait before using them until their design has been strengthened. In addition, practitioners can make informed choices and select solutions with a more robust metrology design. This, in turn, will benefit enterprise architects, software engineers, and other EA professionals in decision making, by enabling them to take into consideration factors more adequately such as cost, quality, risk, and value when assessing EA features. The study’s findings thus contribute to the development of more reliable and effective EA measurement solutions. Recommendation for Researchers: Researchers can use with greater confidence the EA measurement solutions with admissible mathematical operations and measurement units to develop new decision-making models. Other researchers can carry on research to address the weaknesses identified in this study and propose improved ones. Impact on Society: Developers, architects, and managers may be making inappropriate decisions based on seriously flawed EA measurement solutions proposed in the literature and providing undue confidence and a waste of resources when based on bad measurement design. Better quantitative tools will ultimately lead to better decision making in the EA domain, as in domains with a long history of rigor in the design of the measurement tools. Such advancements will benefit enterprise architects, software engineers, and other practitioners, by providing them with more meaningful measurements for informed decision making. Future Research: While the analysis described in this study has been explicitly applied to evaluating EA measurement solutions, researchers and practitioners in other domains can also examine measurement solutions proposed in their respective domains and design new ones.

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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.774
Threshold uncertainty score0.327

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.002
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.001
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.016
GPT teacher head0.236
Teacher spread0.220 · 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