Business Process Points: a proposal to measure BPM projects
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.
Bibliographic record
Abstract
Organizations need more standardization and efficiency in business process execution, which is leading them to show an increasing interest in the business process management (BPM) approach. Stakeholders and workers from different departments are collaborating to obtain better products/services as a result of the BPM projects, but do not always achieve satisfactory outcomes. BPM projects must be well managed and measured for successful implementation. Software Engineering (SE) projects often use a Functional Size Measurement (FSM) technique to estimate the size of the project. This paper proposes an FSM technique for BPM, based on the Function Points metric from SE. We chose the Function Point Analysis, (an FSM technique), as the basis for the proposed Business Process Point Analysis (BPPA) technique. BPPA is a Process Size Measurement technique, developed for business processes modeled through the Business Process Management Model and Notation. BPPA will enable project managers to measure Business Process Points of BPM projects by allowing them to estimate important variables for better managing projects, such as required resources, human effort, cost and time. This paper provides an overview of the proposed BPPA technique and the results of an empirical analysis based on observations from a BPM specialist and an FPA specialist.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.003 | 0.006 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.018 |
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 it