Open Source Systems Engineering Guides, Deployment Packages and Support Tools for Very Small Enterprises ‐‐ A Case Study
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
Abstract Very small entities (VSEs) play an increasingly important role in the global economy. The products they develop are often integrated into products made by larger enterprises. The “Big League” clients, furthermore, demand of the VSEs that they assume a much broader role, spanning the entire development life‐cycle of the product instead of being limited to a “build‐to‐print” approach. To address this new reality, to exploit the lean and efficient nature of VSEs and to adapt to their typical budget and resource constraints, the ISO/IEC 29110 systems engineering standards, management and engineering guides were developed from ISO/IEC/IEEE 15288. In addition, and by design, the standard is supported by Deployment Packages, software tools and training kits. The INCOSE VSE working group developed the deployment packages. A deployment package is a set of artefacts designed to facilitate the implementation of a standard or a set of practices in a VSE. In tune with the need for low cost and flexibility, Open Source software tools are emerging to complete “Big League” development life‐cycle toolsets, which are often out‐of‐reach to VSEs. Finally, to make the deployment of the standard possible in the VSE, training packages, supported by relevant pilot projects help VSE personnel learn how to apply all of the above.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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