On The Importance of Being Able to Hold a Stake
Bibliographic record
Abstract
Abstract The consideration of stakeholders as an input to a Systems Engineering approach is well‐known and well‐documented. What is not considered or discussed as much are the times a Systems Engineer developing a solution must become a stakeholder, defining and distributing needs derived from the system solution to its sub‐element systems and other realization systems. This paper describes the importance of a Systems Engineer being able to act as a stakeholder, and how important the partnership and cooperation between a system developer (Systems Engineer) and the stakeholders is. Both interacting with and being a stakeholder are important skills for a Systems Engineer to have – this paper gives an introduction to both why and how to do this.
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.037 | 0.075 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.010 | 0.029 |
| Scholarly communication | 0.014 | 0.019 |
| Open science | 0.001 | 0.014 |
| Research integrity | 0.009 | 0.010 |
| Insufficient payload (model declined to judge) | 0.018 | 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".