← Latest papers
⚡ electrical engineering

IDDMBSE: Integrating Data-Driven and Model-Based Systems Engineering for Trusted Autonomous Cyber-Physical Systems

This paper introduces IDDMBSE, an integrated Systems Engineering methodology that bridges Model-Based Systems Engineering (MBSE) and data-driven ML/AI through a unified V-process and open-source tool chain (PERFECT, TRADES-X, and VERITAS) to enable the trusted development and verification of autonomous cyber-physical systems.

Original authors: John S. Baras, Sai Sandeep Damera, Ryan Matheu, Clinton Enwerem, Praveen M. S. Kumar

Published 2026-06-08
📖 5 min read🧠 Deep dive

Original authors: John S. Baras, Sai Sandeep Damera, Ryan Matheu, Clinton Enwerem, Praveen M. S. Kumar

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are building a highly advanced, self-driving robot. You have two ways to design it:

  1. The Architect's Blueprint (Model-Based): You draw perfect, mathematical blueprints. You know exactly how the wheels turn and how the sensors should work based on physics. This is precise, but it assumes the world is a clean, predictable classroom.
  2. The Street-Smart Learner (Data-Driven): You let the robot learn by doing, feeding it millions of photos and experiences so it can recognize a cat or a pothole. This is great for the messy real world, but it's a "black box"—you can't always explain why it made a decision, and it might fail in weird ways you didn't predict.

The Problem: Currently, engineers treat these two methods as separate. They build the robot using the blueprints, then awkwardly glue the "street-smart" AI onto it later. This makes the system fragile, hard to certify as safe, and slow to design.

The Solution: IDDMBSE
The paper introduces IDDMBSE (Integrated Data-Driven and Model-Based Systems Engineering). Think of this as a Master Conductor that unites the Architect and the Street-Smart Learner into a single, harmonious orchestra.

Instead of treating the AI as a mystery box, IDDMBSE treats it as a standard part of the blueprint. It creates a loop where the math and the data constantly check each other.

The Three Specialized Tools

To make this work, the authors built a "toolchain" (a set of three specialized software tools) that talk to each other through a central "Modeling Hub" (like a shared digital notebook).

  1. PERFECT (The Simulator):

    • The Analogy: Imagine a video game engine that can instantly turn your paper blueprint into a working robot in a virtual world.
    • What it does: It takes the abstract design (SysML) and automatically turns it into a real, running robot code (ROS). It then runs thousands of simulations in a virtual "Isaac Sim" test range (a digital dirt track with rocks and slopes) to see how the robot actually performs. It feeds the results back into the blueprint.
  2. TRADES-X (The Smart Selector):

    • The Analogy: Imagine you are shopping for a car. You have 8,000 possible combinations of engines, tires, and sensors. Testing them all would take forever. TRADES-X is the smart shopper who says, "Let's use math to rule out 99% of the bad options first, then we'll only test the top 10 in the real world."
    • What it does: It uses math to quickly eliminate impossible designs, then uses the simulator (PERFECT) to deeply test only the best remaining candidates. This saves massive amounts of time and computing power.
  3. VERITAS (The Safety Inspector):

    • The Analogy: A triple-layer security guard.
      • Layer 1 (Math): Checks the blueprint to prove the robot can't do something dangerous.
      • Layer 2 (Data): Checks the simulation results to statistically prove the robot rarely fails.
      • Layer 3 (Real-time): Watches the robot while it's running and sounds an alarm if it starts to drift off course.
    • What it does: It combines these three checks to give a "guarantee" that the robot is safe. If a design fails any of the three, it gets rejected.

How It Works in Practice

The paper demonstrates this on a Trusted Autonomous Ground Robot (a self-driving vehicle for rough terrain). Here is how they used the tools:

  • Choosing Sensors: They had to pick the best mix of cameras and lasers. TRADES-X mathematically narrowed down 8,000 options to just 7, which PERFECT then tested in the virtual dirt track.
  • Planning Paths: They tested a new "risk-averse" path planner. PERFECT ran it in the simulation, showing it took slightly longer paths but avoided dangerous obstacles much better than older methods.
  • Seeing Clearly: They used a technique called "conformal prediction" to make the robot's vision safer. If the robot isn't 100% sure about an object, the system automatically draws a bigger "safety bubble" around it so the robot doesn't crash.
  • Robot Teams: They tested a group of robots working together. VERITAS checked the math to ensure they wouldn't crash into each other, and if one robot made a mistake, the system flagged it immediately.

The Big Picture

The paper claims that by using IDDMBSE, engineers can build robots that are not only smart but also trusted. They can prove the robot is safe because every decision, from the initial blueprint to the final code, is traced back to a single set of requirements.

Looking Ahead: The authors note that their current tools rely on older software standards (SysML v1), which can be clunky. They are currently rebuilding IDDMBSE on a new, modern foundation (SysML v2) that will make the connection between the math and the AI even tighter and easier to manage, potentially allowing AI agents to help write the blueprints themselves in the future.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →