Application framework support for process-oriented software development
Bibliographic record
Abstract
As organisations move their business processes online, it is becoming important for software development to be process-oriented. In particular, managed process applications are a class of business software that helps to improve operational efficiency in organisations by monitoring processes and reporting on performance. General purpose application development tools and model-driven architecture do not support run-time configurability of a managed process nor do they provide specific systematic support for integrated data collection, monitoring and reporting within a managed process. To facilitate such configurability and integrated data management, a model-based application framework is needed to address process-oriented software development. In this paper, we describe a prototype of such a framework, illustrating and evaluating the benefits, with a case study of a system developed for and used by a palliative care support team in Ottawa, Canada. In the case study, we illustrate how a managed process can be modelled using the prototype framework (including its’ workflow, roles, entities, events, alerts and performance indicators).
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.008 | 0.011 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.005 | 0.004 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.011 | 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".