Incorporation of relational modeling method into object-oriented analysis
Bibliographic record
Abstract
It is a generally accepted concept that multiple views are needed in object-oriented analysis or domain analysis techniques. Three commonly adopted models for requirements analysis include object model, functional model and dynamic model. This paper introduces and incorporates the concept of relational modeling into the analysis techniques. Relational modeling mainly deals with two tasks: classification of semantic relations and identification of higher-order system causal relations. Classification of semantic relations supports comparison and evaluation of various relations, which in turn can be used to select suitable methods to process the relations. A higher-order relation depicts the relations between different relations as opposed to the relations between objects often discussed in object modeling. A network of higher-order relations reveals the cause-effect dependency relationships and can facilitate understanding and reasoning of application systems. Furthermore, incorporation of relational modeling techniques can support software reuse in an application domain or across domains.
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.009 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.004 | 0.004 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.006 | 0.009 |
| Open science | 0.003 | 0.003 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.005 | 0.003 |
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".