MétaCan
Menu
Back to cohort

Development and evaluation of a generalized ontology framework for software requirement specification

2025· article· W4416046743 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

VenueIndonesian Journal of Electrical Engineering and Computer Science · 2025
Typearticle
Language
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsYork University
Fundersnot available
KeywordsOntologySemantic reasonerProcess ontologyUpper ontologyOntology engineeringOntology-based data integrationProcess (computing)ReuseSoftware development

Abstract

fetched live from OpenAlex

This paper presents an ontology developed to address challenges such as com munication gaps, risks of errors, and inconsistencies during the manual process of creating software requirement specifications (SRS). The proposed ontology offers a systematic and formal depiction of the requirements, enhancing consis tency and communication among stakeholders. The ontology has been devel oped from the software requirements documents to facilitate the development process. This paper discusses the process of creating the ontology and demon strates using Pellet Reasoner for inference and Prot´eg´e for ontology construction to save and reuse information. The ontology seems to be efficient in manag ing complex software projects, enabling accurate requirement retrieval through SPARQL queries. This study emphasizes how incorporating ontologies into re quirement engineering can significantly enhance the quality and reliability of SRS.

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.004
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.962
Threshold uncertainty score0.859

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.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.037
GPT teacher head0.312
Teacher spread0.275 · 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