A technique for specifying interface modules for real-time systems
Bibliographic record
Abstract
Documentation plays a key role as a component of design process, and a preview of a task before it comes to be executed. It is particularly useful for aviation and military applications in which reliability and maintainability are very important aspects for judging the success of a project. Interface modules (IM) encapsulate input or output device hardware and the related software, so that the application software can be written without specific knowledge of the particular devices used. An IM specification must therefore use a combination of notations and formalisms. In this paper, we present a technique for IM specification that is an extension of a system requirements documentation technique. It is based on the software cost reduction (SCR) method. An IM is specified as a "subsystem" that interacts with both the external environment and other software modules in the larger system. The interface quantities are modeled as functions of time and the behaviour is described in terms of conditions, events and mode classes. This technique facilitates concise and formal description of the module behaviour, including tolerances and delays.
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 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.001 |
| 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.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 itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, 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".