MétaCan
Menu
Back to cohort
Record W2077210358 · doi:10.4018/jdm.2009010101

Use Case Diagrams in Support of Use Case Modeling

2009· article· en· W2077210358 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

VenueJournal of Database Management · 2009
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsSimon Fraser University
Fundersnot available
KeywordsUse Case DiagramComputer scienceUnified Modeling LanguageDiagramCommunication diagramInfluence diagramSet (abstract data type)ComprehensionActivity diagramClass diagramRepresentation (politics)Human–computer interactionNatural language processingInformation retrievalArtificial intelligenceProgramming languageSoftwareDecision tree

Abstract

fetched live from OpenAlex

Use case modeling in the Unified Modeling Language (UML) is a popular text-based tool for systems analysis and design. Use cases can be used with or without supporting use case diagrams. This paper uses an experiment to explore the effectiveness of including a use case diagram with a set of use cases. The Cognitive Theory of Multimedia Learning is used to hypothesize that the use case diagram improves the effectiveness of use cases for novice users by providing visual cues aiding model viewers in selecting and integrating relevant information. The level of understanding developed by participants viewing either uses cases or use cases with a supporting use case diagram was measured using comprehension, retention, and problem solving tasks. Results showed that participants viewing the use cases with the supporting diagram developed a significantly higher level of understanding, as measured by performance on the problem solving task, than participants provided with use cases alone. This analysis suggests practitioners should consider combining a visual representation, such as a use case diagram, with text-based use cases to achieve higher levels of understanding in persons viewing these descriptions.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Case report · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.743
Threshold uncertainty score0.418

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.003
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.067
GPT teacher head0.301
Teacher spread0.234 · 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