Use Case Refactoring: A Tool and a Case Study
Bibliographic record
Abstract
Use case models are widely used for requirements engineering to capture functional and nonfunctional requirements, guide scenario-based design and validation, and to manage projects. Our tool for use case development and evolution supports reorganization (refactoring) of use case models as well as the extension of use case models to include new functional and nonfunctional requirements. The tool is based on a three-level metamodel covering the environment or context of a use case model, the structure of use cases, and the event or message-passing details of a scenario. In this paper we describe the tool that we have developed, and demonstrate its application to a case study for bank teller machines (ATMs). We show that the concept of refactoring can be applied to use case models as an aid to their development and evolution. We are now working on a firm semantic foundation for use cases in order to verify the behaviour-preserving property of individual refactorings.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.014 | 0.024 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.005 | 0.005 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.004 | 0.005 |
| Open science | 0.004 | 0.004 |
| Research integrity | 0.005 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".