MétaCan
Menu
Back to cohort
Record W2045775041 · doi:10.1109/sera.2006.51

Models Derived from Automatically Analyzed Textual User Requirements

2006· article· en· W2045775041 on OpenAlexaff
Magda Ilieva, Olga Ormandjieva

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicService-Oriented Architecture and Web Services
Canadian institutionsConcordia University
Fundersnot available
KeywordsComputer scienceUnified Modeling LanguageFormalism (music)Activity diagramRelation (database)Software engineeringNatural languageProgramming languageSoftwareData miningNatural language processing

Abstract

fetched live from OpenAlex

Requirements engineering is an important area of software engineering concerned with the extraction and presentation of knowledge from user requirements. There is a considerable gap between the various types of presentation of the same kinds of knowledge - those of the user written in natural language (NL) and those of requirements engineering (RE) depicted using diagrams (de facto standard UML diagrams, for example). Our research is aimed at filling that gap. In this paper, we introduce a universal formalism based on the basic building unit of NL, which is the relation triad. Through the definition of these basic relations in NL, we create three RE models: the use case path model, the hybrid activity diagram model and the domain model. These models are abstractions of the knowledge contained in the text, and serve as the basis for deriving UML diagrams

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.001
metaresearch head score (Gemma)0.009
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.007
Threshold uncertainty score0.022

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.009
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0020.001
Science and technology studies0.0000.001
Scholarly communication0.0020.002
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0070.003

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.014
GPT teacher head0.233
Teacher spread0.219 · 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 designSimulation or modeling
Domainnot available
GenreMethods

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

Citations35
Published2006
Admission routes1
Has abstractyes

Explore more

Same topicService-Oriented Architecture and Web ServicesFrench-language works237,207