3.4.0 Integrating MBSE into a Multi‐Disciplinary Engineering Environment
Bibliographic record
Abstract
Abstract Model‐based systems engineering (MBSE) formalizes the practice of systems engineering through the use of models. This panel is intended to address considerations for incorporating MBSE into a broader multi‐disciplinary engineering environment. Engineering disciplines use multiple languages and tools whose results are not always easily integrated. The lack of integration is a source of design discrepancies and errors. The potential for MBSE is that it provides a means to integrate multi‐disciplinary engineering including systems, hardware, software, analysis, and test throughout the development life cycle. This panel will include representatives from other engineering disciplines to address questions such as: 1) What should other engineering disciplines expect from MBSE, and what should systems engineering expect from other disciplines to enable MBSE? 2) What can MBSE learn from model‐based approaches used in other engineering disciplines? 3) How should the practices and tools be integrated/coupled across disciplines? 4) How are the system, hardware, and software models managed to ensure an integrated technical baseline? 5) How should a program be organized to achieve more effective utilization and application of model‐based engineering? These are some of the questions that must be answered to more fully reap the benefits of MBSE.
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.024 | 0.022 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.006 | 0.007 |
| Open science | 0.002 | 0.007 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.009 | 0.003 |
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".