Skip to main content

Mastering MBSE for EV Development with MathWorks: A Seamless Workflow

· 4 min read
Blagoje Mrkic
Blagoje Mrkic
Model based Systems Architect

Welcome to MBSE Explained, where we demystify Model-Based Systems Engineering for the automotive and EV industry. With nearly five years as a Model-Based Embedded Software Developer and Architect, and 1.5 years as a Model-Based Systems Architect in automotive projects, I've seen firsthand how crucial integrated tools are for successful system development. Today, we're diving into the powerful ecosystem of MathWorks tools for MBSE, specifically how they enable a streamlined workflow from concept to validation, focusing on System Composer, Requirements Toolbox, and their connection to system test and software Model-Based Design (MBD).

The Integrated MathWorks MBSE Ecosystem​

Developing complex automotive and EV systems demands a robust approach to managing requirements, architecture, and design. MathWorks provides a comprehensive suite of tools that supports the entire MBSE lifecycle, ensuring traceability and consistency across domains.

At the heart of this workflow is System Composer™. This powerful tool allows you to define, analyze, and specify system and software architectures using industry standards. You can model everything from high-level system components like an EV powertrain management unit to detailed sensor-actuator interfaces. System Composer acts as the central hub, enabling early-stage analysis and architectural exploration, which is critical for identifying potential issues before costly hardware is built.

Complementing System Composer is the Requirements Toolbox™. This tool allows engineers to capture, manage, and link requirements directly to system models, design components, and test cases. This direct traceability is invaluable for demonstrating compliance with standards like ISO 26262 and ensuring that every system function, from regenerative braking to battery thermal management, can be traced back to a specific stakeholder need. This integration ensures a robust "digital thread" throughout your development process.

Bridging MBSE to System Test and Software MBD​

One of the greatest strengths of the MathWorks ecosystem is its seamless integration with downstream activities, accelerating both system verification and software development.

Connecting to System Test​

The architectural models created in System Composer, combined with detailed requirements managed in Requirements Toolbox, form a solid foundation for system testing. Test engineers can leverage these models to:

  • Derive Test Cases: Automatically generate test cases that directly validate specific requirements and architectural behaviors.
  • Validate System Behavior: Use simulation models (often built in Simulink® and Simscape™ from the System Composer architecture) to execute tests and verify the system's performance under various operating conditions – think charging cycles for an EV battery or torque vectoring for traction control.
  • Traceability for Compliance: Maintain a clear link from test results back to specific requirements, essential for regulatory compliance and audit trails in the automotive sector.

Seamless Software Model-Based Design (MBD)​

For software MBD, the transition from system architecture to detailed software design is remarkably smooth.

  • Refined Design: Components defined in System Composer can be further elaborated into detailed Simulink and Stateflow® models for embedded software. This ensures a consistent design methodology from the system level down to individual software components.
  • Code Generation: With tools like Embedded Coder®, engineers can automatically generate production-ready code directly from these detailed models, significantly reducing manual coding errors and development time.
  • Verification and Validation: Integrated tools like Polyspace® support static code analysis and formal verification, ensuring the generated code meets quality and safety standards, which is paramount in safety-critical automotive applications.

This integrated workflow empowers teams to develop safer, more reliable, and innovative EV systems faster, by fostering collaboration and maintaining a consistent digital representation of the system throughout its lifecycle.

Conclusion​

Leveraging MathWorks tools for MBSE provides an unparalleled advantage in the complex world of automotive and EV development. From defining robust system architectures with System Composer to linking requirements with Requirements Toolbox, and then seamlessly transitioning to system testing and software MBD, the entire process is streamlined and traceable. This holistic approach empowers engineering teams to tackle the intricate challenges of modern vehicle design with confidence and efficiency.

What are your experiences with MathWorks tools in your MBSE journey? Share your thoughts below! At MBSE Explained, we're committed to simplifying systems for smarter EVs.