< Back to Electrical & Electronic Toolchain
- Introduction: The Shift to Centralized E/E Architectures
- Core Architecture and Modules of the M-Design Toolchain
- Key Technological Advantages Over Traditional Tools
- Real-World Automotive Engineering Applications
- Best Practices for Engineering Adaptation and Optimization
- Conclusion & Future Outlook
- FAQ Section: Top 5 Most Discussed FAQs (English) — Automotive E/E Toolchain: M‑Design E/E Development
Introduction: The Shift to Centralized E/E Architectures
As the automotive industry transforms with electrification, intelligence, connectivity, and shared mobility, the development of electronic and electrical (E/E) systems is becoming more complex. Traditional distributed E/E architectures are moving toward centralized and domain-based models, increasing the need for efficient, integrated development tools.
The M-Design E/E Development Toolchain addresses these challenges by providing a full-cycle solution for automotive E/E development. It uses Model-Based Systems Engineering (MBSE) principles to streamline the development process, from requirements gathering to verification and integration.
Core Architecture and Modules of the M-Design Toolchain
The M-Design Toolchain consists of several core modules that cover the full lifecycle of automotive E/E development, ensuring smoother processes and collaboration between different teams.
Requirements Engineering Module
This module is essential for managing the early stages of development. It imports multi-source requirements and organizes them using SysML-based models to ensure they are verifiable and traceable. With the help of collaborative review mechanisms, teams can effectively track and modify requirements, ensuring alignment across departments.
System Architecture Design Module
The system architecture design module is pivotal in laying out the overall structure of the system. It allows engineers to visualize how various components, such as domain controllers, ECUs, sensors, and actuators, will be interconnected. The module supports various architectural styles, including distributed, centralized, and zonal, and helps engineers design systems that meet modern AUTOSAR standards for interoperability. It also protects intellectual property through encrypted model encapsulation.
Simulation and Verification Module
Simulation is crucial for validating system behavior before physical implementation. M-Design’s simulation tools support Model-in-the-Loop (MIL) and Software-in-the-Loop (SIL) simulations, providing early-stage testing of system functions, timing, and fault tolerance. The tool automatically checks the impact of design changes, preventing downstream issues, and helps maintain ISO 26262 compliance with built-in safety verification tools like FTA and FMEA.
Code Generation Module
The code generation module automates the creation of C/C++ code, ensuring compliance with AUTOSAR and enabling easy integration with various automotive ECUs and controllers. Code generated by the tool is traceable back to the model, which makes debugging and maintenance simpler. The tool also supports MISRA C/C++ compliance to meet safety and quality standards.
Integration Test Module
Testing is an integral part of the E/E development process. M-Design’s integration testing tools automatically generate test cases based on the design and requirements models, reducing manual work. The module supports both bench and real-vehicle testing, ensuring systems are validated under both simulated and real-world conditions. After testing, the tool generates detailed reports, including test results, defect analysis, and actionable insights.
Key Technological Advantages Over Traditional Tools
The M-Design Toolchain provides several key advantages over traditional, fragmented toolchains that require separate tools for each stage of development.
Full-Process Integration
By integrating all stages of the development lifecycle into a single toolchain, M-Design helps reduce development time by over 15%. This integration eliminates inefficiencies caused by using different tools for requirements, architecture, simulation, and testing.
Model-Driven and Forward Engineering
The toolchain is built around MBSE, a model-driven approach that facilitates more flexible and agile development. This method ensures that changes can be easily incorporated at any stage of the development process, which is particularly valuable as E/E systems evolve rapidly.
Safety Compliance and Autonomous Control
M-Design adheres to the ISO 26262 and AUTOSAR standards, ensuring that developed systems meet safety requirements. It also supports the integration of domestic chips and operating systems, which helps reduce reliance on foreign solutions and supports autonomous vehicle development.
Real-World Automotive Engineering Applications
M-Design has been successfully used in various automotive engineering projects, demonstrating its effectiveness in real-world scenarios.
Case Study 1: Autonomous Driving Domain Controller Development
M-Design was used to develop an L2.5 autonomous driving domain controller for a major automaker. The toolchain helped cover the full process from requirements to real-vehicle testing. The results were impressive: the development cycle was reduced by 20%, code defects decreased by 35%, and interface compatibility issues were reduced by 40%.
Case Study 2: Cross-Domain Integration and Verification
In this case, M-Design supported the integration of various vehicle domains such as powertrain, body, and ADAS (Advanced Driver Assistance Systems). By using M-Design for cross-domain simulation and real-vehicle validation, the project was able to reduce communication latency to under 10ms and address typical cross-domain integration issues, such as interface compatibility.
Best Practices for Engineering Adaptation and Optimization
To maximize the benefits of the M-Design Toolchain, companies should follow best practices for engineering adaptation and optimization.
Engineering Adaptation Strategies
Establishing a clear development mechanism across teams is crucial for ensuring that requirements, architecture, and testing teams are aligned throughout the process. Early hardware and software compatibility checks should be conducted to avoid issues during later stages.
Optimization Recommendations
Companies can benefit from building enterprise-level model libraries, integrating CI/CD tools for automated workflows, and investing in MBSE training for engineers. These strategies ensure that M-Design’s full capabilities are leveraged and that the development process is optimized.
Conclusion & Future Outlook
The M-Design E/E Development Toolchain offers a comprehensive solution to the challenges faced by automotive engineers in developing complex E/E systems. It provides end-to-end support from requirements engineering to testing, ensuring that all stages of development are seamlessly integrated. As the automotive industry moves toward centralized computing architectures and autonomous driving technologies, M-Design will continue to evolve to meet these needs, driving innovation in the field of automotive E/E development.
FAQ Section: Top 5 Most Discussed FAQs (English) — Automotive E/E Toolchain: M‑Design E/E Development
1. What is M‑Design E/E Development and what problems does it solve?
M‑Design E/E Development is a model‑based systems engineering (MBSE) toolchain designed to optimize automotive electrical/electronic (E/E) architecture development. It addresses issues such as fragmented tools, disconnected requirements, and low cross-team collaboration by providing unified SysML-based modeling and full lifecycle traceability.
2. What core functionalities does the M‑Design toolchain provide?
M‑Design integrates several key functions, including SysML-based requirements and architecture modeling, behavior and parameter simulation, traceability analysis, cross-team collaborative modeling, and verification. These functions support managing the full development lifecycle from concept to verification.
3. How can I start using M‑Design (installation, trial, activation)?
Users can download a trial version from the official website and activate it using a license. The trial version includes user manuals and tutorials to help get started.
4. Does M‑Design support the latest modeling standards and how?
Yes. M‑Design supports SysML v2 for comprehensive systems modeling, including full model construction, simulation, and standardized API integration with external tools.
5. What are common challenges or limitations users encounter?Common issues include a steep learning curve for MBSE, integration challenges with legacy tools, performance limitations on large models, and differences in tool capabilities across versions.
