MétaCan
Menu
Back to cohort
Record W1983158177 · doi:10.1115/detc2009-86514

Automatic Generation of UML Diagrams From Product Requirements Described by Natural Language

2009· article· en· W1983158177 on OpenAlexafffund
Lei Chen, Yong Zeng

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsConcordia University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsSystems Modeling LanguageClass diagramComputer scienceUML toolApplications of UMLProgramming languageUnified Modeling LanguageObject Constraint LanguageCommunication diagramSemantics (computer science)Software engineeringSoftware

Abstract

fetched live from OpenAlex

In this paper, a novel approach is proposed to transform a requirement text described by natural language into two UML diagrams — use case and class diagrams. The transformation consists of two steps: from natural language to an intermediate graphic language called recursive object model (ROM) and from ROM to UML. The ROM diagram corresponding to a text includes the main semantic information implied in the text by modeling the relations between words in a text. Based on the semantics in the ROM diagram, a set of generation rules are proposed to generate UML diagrams from a ROM diagram. A software prototype R2U is presented as a proof of concept for this approach. A case study shows that the proposed approach is feasible. The proposed approach can be applied to requirements modeling in various engineering fields such as software engineering, automotive engineering, and aerospace engineering. The future work is pointed out at the end of this paper.

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.003
metaresearch head score (Gemma)0.013
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: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.003
Threshold uncertainty score0.016

Distilled classifier scores by category (both heads)

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

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.021
GPT teacher head0.256
Teacher spread0.235 · 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

Citations12
Published2009
Admission routes2
Has abstractyes

Explore more

Same topicModel-Driven Software Engineering TechniquesFrench-language works237,207