10.3.1 The Development of Systems Engineering International Standards and Support Tools for Very Small Enterprises
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 Industry recognizes that there are very small organizations that develop parts which contain software components. These organizations, those with up to 25 people, are very important to the world‐wide economy, and the parts they develop are often integrated into products made by larger enterprises. Failure to deliver a quality product on time and within budget threatens the competitiveness of both organizations. One way to mitigate these risks is for all the suppliers in a product chain put in place proven engineering practices. Many international standards have been developed to capture such proven engineering practices. However, these standards were not written for very small development organizations and are consequently difficult to apply in such settings. An ISO Working Group has been established to address these difficulties. The working group developed standards and technical reports, ISO/IEC 29110, which were published in 2011 for organizations developing software. In 2009 an INCOSE working group was established to evaluate the possibility of developing a standard, using the ISO/IEC 29110 standard as a baseline and the ISO/IEC 15288 as the framework, for organizations developing systems. At the 2011 INCOSE International Workshop, a group of systems engineers reviewed the ISO/IEC 29110 software standard and proposed modifications to meet their needs. One constraint was to develop a document which will allow an organization developing systems with software components to be able to use the actual set of ISO/IEC 29110 standards as well as the proposed systems engineering standards. The future systems engineering standard is targeted at VSEs which do not have experience or expertise in tailoring ISO/IEC 15288. A draft document has been developed and reviewed. Recently, an ISO working group has been mandated to develop the ISO standard for very small organizations developing systems. The INCOSE Systems Engineering Handbook is used as the main reference for the development of a set of systems engineering deployment packages. A deployment package is a set of artefacts developed to facilitate the implementation of a set of practices of a standard in a very small organization.
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.000 | 0.001 |
| Open science | 0.001 | 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