Our Workflow

This workflow defines a structured approach to developing robust automotive electronics, integrating Model-Based Design (MBD), diagnostics (UDS), communication protocols (LIN, SPI, CAN, J1939), Bootloader, ASPICE processes, and testing strategies. Functional Safety (ISO 26262) and Cybersecurity (ISO/SAE 21434) are ongoing focuses.

Concept Stage

Concept Stage

Define product vision, assess feasibility, analyze stakeholders, research the market, and evaluate FuSa and cybersecurity risks.

System Requirements

System Requirements

Specify system functionality, communication protocols (LIN, SPI, I2C, J1939, CAN), Bootloader updates, and align with ASPICE and ISO standards.

System Architecture

System Architecture

Create modular designs for diagnostics, Bootloader, and communication protocols using MBD tools.

Software and Hardware Requirements

Software and Hardware Requirements

Develop diagnostic services, Bootloader routines, and hardware components compatible with ASPICE and ISO 26262.

Software Architecture

Software Architecture

Design layered software for diagnostics and communication with API integration and early error detection using Simulink.

Hardware Architecture

Hardware Architecture

Design and validate hardware schematics and PCBs for communication protocols and diagnostics.

Development Stage

Development Stage

Build software libraries, validate hardware modules, and integrate diagnostics and communication protocols.

Testing and Validation

Testing and Validation

Conduct unit, system, and hardware testing to ensure compliance with ASPICE and ISO 26262 standards.Ensure functionality, reliability, and compliance.

ASPICE Workflow

ASPICE Workflow

Use ASPICE-aligned processes to capture, simulate, and validate requirements with MBD tools and maintain traceability.