MétaCan
Menu
Back to cohort

A Model-driven and Template-based Approach for Requirements Specification

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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsComputer scienceTemplateNon-functional requirementSoftware requirements specificationFormal specificationRequirements analysisSoftware engineeringDomain (mathematical analysis)AmbiguityNatural languageCertificationRequirements engineeringProgramming languageSoftwareSoftware systemSoftware developmentSoftware designArtificial intelligenceSoftware construction

Abstract

fetched live from OpenAlex

Requirements specification and verification play an important role in the certification of safety-critical software (SCS). These activities are costly and error-prone because SCS exhibit a high number of requirements and most SCS manufacturers are still using natural language to specify these requirements. On one hand, natural language can introduce ambiguity and inconsistency. On the other hand, formal languages add an overhead to the requirements specification because of their complexity. Controlled Natural Languages (CNLs) fill these gaps by offering a middle-ground solution, although not yet well adopted by the industry. In this paper, we introduce an approach that combines CNLs and model-driven engineering (MDE) for requirements specification. The approach was proposed to support an industrial partner in the certification process of a SCS. Our approach uses templates and relies on two types of models: models that specify the templates, and a model of the domain of the system at hand. Using models of the templates enables to automate some requirements analysis tasks. Using a domain model allows the auto-completion and verification of requirements specified using the templates. We implemented the approach and validated it using three case studies and more than a thousand requirements. We observed that our approach and underlying templates are applicable across domains and that the templates yield requirements with better quality in terms of necessity, ambiguity, completeness, singularity, and verifiability.

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.000
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.045
Threshold uncertainty score0.256

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.000
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.239
GPT teacher head0.352
Teacher spread0.112 · 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