MétaCan
Menu
Back to cohort

UML-Driven Software Performance Engineering

2013· book-chapter· en· W2483497932 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

VenueAdvances in systems analysis, software engineering, and high performance computing book series · 2013
Typebook-chapter
Languageen
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsComputer scienceUnified Modeling LanguageApplications of UMLSoftware engineeringCategorizationSoftwareData scienceArtificial intelligenceProgramming language

Abstract

fetched live from OpenAlex

Performance is critical to the success of every software system. As a sub-area of software engineering, Software Performance Engineering (SPE) is a systematic and quantitative discipline to construct software systems that meet performance objectives. A family of SPE approaches that has become popular in the last decade is SPE based on models developed using the Unified Modeling Language (UML), referred to as UML-Driven Software Performance Engineering (UML-SPE). This particular research area has emerged and grown since late 1990s when the UML was proposed. More than 100 papers have been published so far in this area. As this research area matures and the number of related papers increases, it is important to systematically summarize and categorize the current state-of-the-art and to provide an overview of the trends in this specialized field. The authors systematically map the body of knowledge related to UML-SPE through a Systematic Mapping (SM) study. As part of this study, they pose two sets of research questions, define selection and exclusion criteria, and systematically develop and refine a systematic map (classification schema). In addition, the authors conduct bibliometric, demographic, and trend analysis of the included papers. The study pool includes a set of 90 papers (from 114 identified papers) published in the area of UML-SPE between 1998 and 2011. The authors derive the trends in terms of types of papers, types of SPE activities, and types of evaluations. They also report the demographics and bibliometrics trends in this domain and discuss the emerging trends in UML-SPE and the implications for researchers and practitioners in this area.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesMeta-epidemiology (narrow)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.690
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0020.001
Science and technology studies0.0000.000
Scholarly communication0.0010.005
Open science0.0020.001
Research integrity0.0010.001
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.004
GPT teacher head0.189
Teacher spread0.185 · 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