Use processes — modeling requirements based on elements of BPMN and UML Use Case Diagrams
Bibliographic record
Abstract
This paper presents a new approach to gather requirements called Use Processes. The approach includes a Use Process Diagram which is based on notation elements of the OMG Business Process Modeling Notation and Use Case Diagrams of UML v1.5. We also propose a set of templates to describe the elements of the Use Process Diagram. We believe that a business process-oriented approach to gather requirements will lead in the customer and user satisfaction because it allows their participation in the requirements definition. This is very important because the main customers of the software applications are business people who are usually very comfortable in working with visualization of business processes. To prove the validity of our approach, we implemented it to develop three small object-oriented software projects in two organizations, one in a department of a bureau of the Mexican Government and two in a private enterprise that develops software.
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.017 | 0.030 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.007 | 0.004 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.006 | 0.012 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.003 | 0.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.
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".