Model Based Design of Automotive Software

Ans. Our Model Based Software Development team follow the industry accepted V-cycle SDLC Model. Over the last 12+ years, we have achieved ensured complete compliance and alignment of this V-model with enterprise level QA modules such as CMMI Level-3 and ASPICE.

The quality of the artifacts and documents generated throughout the development process are in compliant with CMMI Level-3 and/or ASPICE.

We have also worked on projects where we delivered the artifacts compliant to both CMMI Level 3 and ASPICE, as per the requirements of the customer.

Ans. For one of our Model Based Development projects, we developed an automation tool that could convert libraries of floating point to fixed point model. This conversion was the step prior to generating the code and integrating it with the low-level drivers.

The Master Completion of this conversion manually would have taken more than a week for a developer. Also, it would be error prone, as a lot of data type changes and I/O port name changes would have been required.

The Master However, with the help our Automation Tool, we could convert 16 such libraries to fixed point in 1-2 days.

The Master The benefits for the customer were

• More accurate conversion, better quality of the code and very less turn-around time.

Ans. Yes, post-integration support is part of the Service Level Agreement (SLA). Any kind of bug fixes and change requests, during or post the integration in production environment are part of our model based design support and maintenance services.

If required, our Model Based Design experts can also travel to the customers’ location for an Onsite Support.

Ans.Yes, Embitel has all the necessary skill-sets to help you setup Model Based Software Development process. Our MBD experts will help you with the following processes:

• Support for Documentation related to each and every phase of V based SDLC model.
• ISO 26262 compliance
• AUTOSAR based model development
• Test plan, test cases creation
• I/O documentation for every phase of V-cycle as an evidence for CMMI or other QA audits

Ans.We have expertise in designing both Non-AUTOSAR as well as AUTOSAR based MBD models.

Our MBD experts have worked on projects where standard AUTOSAR guidelines have been followed for model creation, data type nomenclature, I/O names, vehicle diagnostics and more.

Ans. When you partner with Embitel for Model Based projects, you can expect to collaborate with an expert core team of Model Based Development Consultants, Project Managers and Automotive Engineers.

Here is the team hierarchy that is most commonly followed in the Model based software development project.

• Veteran Model Based Development Managers, who ensure end to end V cycle based MBD project execution. Compliance to the organizational process execution model is also ensured by them to the highest level possible.
• Senior MBD Consultants with 14+years of experience, to partner with you for critical automotive projects for product (ECU)/application development and consulting support.
• Senior MATLAB programming experts proficient in developing automotive ECUs/applications as per the latest industry standards including MAAB, AUTOSAR, and ISO 26262.

Ans. We can help you with a phased adoption of Model Based Development paradigm after in-depth review of the architecture of your existing product line.

Here is a brief overview of how a MBD adoption/migration approach may turn out be:

• Getting ready for the migration: Includes assessment of current state of the development process and learning the core MBD tools.
• Feature selection as per project scope: Understanding and fin-tuning of scope and requirements at every phase of development, selection of features, modeling and simulation and code generation.
• Component selection and physical modelling: Activities include Expand modelling, simulation at component level and introduction of plant modelling.
• Standardization: Performing Simulation at system level and full model based verification and validation. Best practices like introduction of tool automation and creation of reusable libraries also come into picture.
• Optimization: The final phase is to align the MBD approach with enterprise vision and goals. Objective is to make the processes fully automated and optimized.

Ans. Model-Based Design (MBD) in the automotive software landscape facilitates the design, simulation, and testing of automotive software before physical prototypes are built.

It streamlines development, enhances accuracy, and reduces costs.

For example, MBD is used in designing advanced driver-assistance systems (ADAS), where simulations predict system responses to various scenarios, enabling early detection and correction of issues, ultimately speeding up the ADAS development cycle and improving safety features.

If we compare it with a non-MBD approach, developing a new adaptive cruise control feature would involve manually writing and integrating code based on the system’s specifications, with physical tests conducted on prototypes to validate functionality. This could lead to significant delays if errors are found late in the development process.

Conversely, with an MBD approach, the same adaptive cruise control system is designed using models that precisely define its behavior. Simulations based on these models can quickly test various scenarios (e.g., different traffic conditions), identifying issues early. Automatic code generation from validated models further speeds up development and reduces errors, making the overall process more efficient.