Digital Transformation in Aircraft Design and Certification: Developing Requirements for Modeling Regulatory Documentation
Bibliographic record
Abstract
Aircraft design and development is complex and regulated by increasingly stringent regulatory documentation. While many disciplines manage design complexity with well-established digital tools, digital transformation of the certification process remains in the early stages of implementation. Models are often used to provide explicit structures to facilitate digital transformation. While several modeling approaches have been applied to regulatory documentation, a gap remains for an established list of requirements for developing effective models in the context of digital transformation. This paper proposes a list of requirements using a requirements elicitation framework adapted from the International Council on Systems Engineering (INCOSE) Needs and Requirements Manual. The adapted research methodology includes problem identification, needs assessment, and requirements development processes. The resulting requirements are validated against needs statements and verified against selected INCOSE requirement statement criteria. Four requirements are selected for a detailed feasibility assessment, which compares the efficacy of process mapping, Unified Modeling Language (UML), and ontological modeling methods to realize the requirements.
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.030 | 0.072 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.006 | 0.003 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.005 | 0.008 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.003 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".