Bibliographic record
Abstract
A use case represents a unit of the functionality specification of a system. Industrial object-oriented projects have applied use cases to capture user requirements. Use cases can be used throughout the whole process of object-oriented software development [14]. But, the problem of how to write use cases is still puzzling even software experts [6]. It reflects the lack of a systematic approach to capturing use cases. The set of use cases in a use case model is unstructured regarding the structure of the problem addressed by an application. This paper presents a notion of a use case pattern and proposes using a use case pattern to guide use case capturing. A use case pattern encodes reusable knowledge on the structure and function of a specific class of applications. It guides the work of use case gathering. We illustrate the approach to use case modeling with several use case patterns.
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.048 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.009 | 0.009 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.006 | 0.008 |
| Open science | 0.004 | 0.005 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.012 | 0.005 |
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".