MétaCan
Menu
Back to cohort

ISO/IEC 29110 Deployment Packages and Case Study for Systems Engineering: The “Not‐So‐Secret” Ingredients That Power the Standard

2016· article· en· W2519193008 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueINCOSE International Symposium · 2016
Typearticle
Languageen
FieldEngineering
TopicSystems Engineering Methodologies and Applications
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsSoftware deploymentSystems engineeringFlexibility (engineering)EngineeringProduct lifecycleEngineering managementSoftware engineeringComputer scienceNew product developmentBusiness

Abstract

fetched live from OpenAlex

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. 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. The ISO/IEC 29110 systems engineering management and engineering guides were developed mainly from ISO/IEC/IEEE 15288 to address this new reality, to exploit the lean and efficient nature of VSEs and to adapt to their typical budget and resource constraints. By design, the management and engineering guide is supported by Deployment Packages (DP), the development of which was taken on by the INCOSE VSE Working Group. A DP is a set of artefacts designed to facilitate the implementation of the management and engineering guides of ISO/IEC 29110 by VSEs. In tune with the need for low cost and flexibility, Open Source software tools are emerging to support VSEs and provide a bridge with “Big League” development life‐cycle toolsets. Finally, to make the deployment of ISO/IEC 29110 possible in VSEs, training packages, supported by relevant pilot projects help VSE personnel learn how to apply all of the above. This paper describes the Systems Engineering DP for Requirements Engineering (RE DP) and shows how it can be applied using the Autonomous Rover Case Study developed under the Eclipse Foundation Polarsys project.

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 imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.764
Threshold uncertainty score0.477

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.030
GPT teacher head0.276
Teacher spread0.246 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it