Bibliographic record
Abstract
In this article, we discuss the concept of shoehorning system requirements into (possibly) poor solutions. Some examples are provided that demonstrate that shoehorning may result in inadequate or even catastrophic system solutions. The design of a new system, a significant upgrade of an existing system, or the procurement of an external system begins (in most cases) with the establishment of what the system is supposed to accomplish, that is, requirements. These requirements spell out how the system is expected to perform if and when it is implemented. Because of the importance of en-suring that the system will perform the required tasks, a new discipline called requirements engineering has been established, which includes the developments of require-ments for systems and the oversight that requirements are implemented to perform the tasks envisioned for the system. In this discussion, the term system can mean a physical product, a software product, an organizational new structure, and so on.
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.010 | 0.032 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.005 | 0.013 |
| Scholarly communication | 0.007 | 0.013 |
| Open science | 0.004 | 0.012 |
| Research integrity | 0.004 | 0.004 |
| Insufficient payload (model declined to judge) | 0.021 | 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".