MétaCan
Menu
Back to cohort
Record W190494807

Refactoring use case models

2007· dissertation· en· W190494807 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

VenueSpectrum Research Repository (Concordia University) · 2007
Typedissertation
Languageen
FieldComputer Science
TopicService-Oriented Architecture and Web Services
Canadian institutionsConcordia University
Fundersnot available
KeywordsCode refactoringMetamodelingComputer scienceSemantics (computer science)Programming languageContext (archaeology)Software engineeringModel transformationProcess (computing)Unified Modeling LanguageSoftwareArtificial intelligence
DOInot available

Abstract

fetched live from OpenAlex

Use cases are promising vehicles for specifying requirements. However, obtaining well-organized use case models is difficult during software evolution. The thesis proposes to address the issue by refactoring use case models. Refactoring is a program transformation approach for iterative software development. Its concept is introduced to use case models in Cascaded Refactoring. The thesis introduces major research involved in refactoring use case models. It defines a use case metamodel to formalize use cases. The three-level metamodel covers the environment or context of a use case model, the structure of use cases in terms of episodes, and the event or message passing details of a scenario. The thesis presents a process algebra semantics for the use case model. The episode semantics is provided from the literature. The semantics of a single use case is defined in terms of the episode model. The semantics of the use case model is defined in terms of the individual use cases and their relationships. The thesis identifies a list of properties that need to be preserved during refactoring. It defines fifty-three use case refactorings, which are described using a template covering the refactoring description, arguments, preconditions, postconditions and verification of behavior preservation. The thesis also introduces a tool for use case modeling and refactoring. The tool helps validate the use case metamodel and refactorings on two case studies, which demonstrate that refactoring use case models is feasible and practical. Based on these case studies, the thesis discusses the nature of use case evolution and provides some guidelines for the refactoring process.

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), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Case report · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.498
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.003
Science and technology studies0.0010.000
Scholarly communication0.0010.002
Open science0.0030.001
Research integrity0.0010.002
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.045
GPT teacher head0.300
Teacher spread0.255 · 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