| A2L (ASAP2) | A file that describes the measurement and calibration objects of an ECU. DEP imports A2L files in Measurement and Calibration. |
| Activity | A view selector in a workspace toolbar, for example CAN / CAN FD or EVSE console. |
| ARINC 429 / ARINC 825 | Avionics data buses. DEP simulates them virtually only. |
| Campaign | A saved selection of scenarios that runs as one batch. |
| Canonical signal | DEP's single name for a value that crosses a component boundary. It is mapped to buses in Signal Mappings. |
| Check | Validation of the saved System for the active profile before a run. It does not certify hardware. |
| Component | A block in the System: a model, ECU, vECU, LRU, vLRU, PLC, gateway, sensor, actuator, network, subsystem or DUT. |
| Connection | A link from a component output port to another component's input port, either a direct signal or over a network. |
| DBC | A CAN database file that describes messages and signals. |
| DUT | Device under test. |
| ECU / vECU | Electronic control unit. A vECU is its software running virtually on the PC (SIL). |
| EVCC / EVSE | Electric vehicle communication controller (vehicle side) and electric vehicle supply equipment (charger side). |
| Evidence | DEP's record of what actually ran: revision, hashes, samples, frames and verdicts. |
| Execution owner | The single part of DEP that currently controls execution: a System run, restbus acquisition, campaign or HIL deployment. |
| Faceplate | A reusable group of HMI widgets, for example a pump or a charger panel. |
| FMI / FMU | Functional Mock-up Interface, a standard for exchanging models. An FMU is a model packaged to that standard. DEP imports and exports FMI 2 and FMI 3 FMUs. |
| Co-simulation / model exchange | FMU kinds. A co-simulation FMU brings its own solver. A model-exchange FMU is solved by DEP (Euler, implicit Euler, RK4 or RK45). |
| HIL | Hardware in the loop: execution on a real-time HIL bench with real I/O. The bench runs on NI VeriStand; DEP discovers it, deploys reviewed systems and observes channels. |
| HMI | Human–machine interface: the operator screens built in HMI Designer. |
| Implementation | The executable behind a component: native model, FMU, physical model, state machine or software. |
| LDF | LIN description file. |
| Logical time | Simulated time that advances in ticks, independent of the wall clock. |
| LRU / vLRU | Line-replaceable unit (avionics) and its virtual counterpart. |
| MIL | Model in the loop: every component runs as a model. |
| Native model | A block-diagram model built in DEP's Model Designer. |
| Physical outputs locked | DEP does not drive real hardware outputs. |
| Prepare for System | Building a new executable version of a model so that the System can use it. |
| Profile | The execution mode of the System: MIL, SIL or HIL. A project can name its profiles. |
| Project | One .rbsproj file that holds everything. |
| Restbus | Simulation of the bus traffic of ECUs that are not physically present. |
| Revision | A saved state of the System. Evidence refers to the revision that ran. |
| Scenario | A saved test case: set inputs, run, check outputs. |
| Session | An execution of the System that persists between batches until it is stopped or released. |
| SIL | Software in the loop: components run compiled software. |
| SIL Kit | An open-source co-simulation framework. DEP can exchange data with SIL Kit participants. |
| Smoke test | A short run (100 ticks) that checks a project executes. It is not a full validation. |
| SoftwareUnit | A process that runs imported customer software. |
| SSP | System Structure and Parameterization, a standard for describing connected FMUs. DEP supports SSP 2.0.1. |
| Starter | A recommended example project in the project library. |
| System | The test setup in a project: components and connections. |
| Tick | One logical-time step of the System, for example 10 ms. |
| XCP | A measurement and calibration protocol for ECUs. DEP does not connect to ECUs over XCP. |
