top of page



 Architectural Trends and Design Patterns 


In the current market the complexity of the E/E system grows exponentially. More functions and more advanced functionality, higher bandwidth networks, cloud computing, AI etc. 
Together with this there is a higher demand for new models being provided by the OEMs more frequently to stay relevant, i.e. shorter time-to-market is needed. 


Traditional architecture usually have tight coupling between SW components, HW and network signaling. As a result it fails to solve modern day issues where the demand for fast development cycles is critical to achieve faster time-to-market.

Some key questions the software and system architects should ask before developing an new architecture:

  • Can the architecture handle the key Quality Attributes?

  • What are the main Architectural Drivers to meet future demands?

  • Does the architecture Scale?

  • How adaptable is the architecture to changes?

  • How to design for the unknowns?

Some of the current architecture design patterns used:

  • Service Oriented Architecture

  • Event Driven Architectures

  • Layered Architecture

  • Microkernel Architecture

Nebula Connecting the Dots with its future-ready Architectural Solution.

To  keep up with ever increasing demands for next generation secure solutions OEMs must make a gear shift from a traditional  architecture to new methods of developing software. Nebula is the game changer that can help the OEMs making that transition:

  • Helping OEMs define their next generation architectural platform and making the transition both architecture wise and organization wise

  • Way of handling legacy parts of the traditional systems in the new architecture.

  • Support isolating the underlying hardware dependencies

  • Provides solutions that shorten development cycles with scalable and reusable output without compromising on safety and performance.

​Nebula also provides a state-of-the art service-oriented platform and design studio that can help making the transition even smoother and cost-efficient.



E/E Architecture Roadmap


We have developed a Model Based E/E Architectural Design process that is an end-to-end solution from start to finish of the entire development process.

  • Project definition

  • Variant Management

  • Requirement Management

  • Function Definition using user stories and use cases

  • Function Design

  • Layered System Architecture

  • Module Definition

  • Module / Service Design

  • Implementation

  • Testing

  • Deployment

  • Network Management

  • Role definitions

  • We find that using MBSE is a key enabler to be able to cope with the increasing complexity of the E/E architecture and to handle System Safety in an efficient way.​

  • ASPICE compliant and utilizing ISO/IEC/IEEE 42010 Systems and Software Engineering — Architecture Description



Model Based System Engineering (MBSE) in E/E Architectural Design process 

State of Art Technology Portfolio

Nebula Delivers  Next generation architectural solutions using Key Performance Driving factors 

Electronic Circuit Board

High Performance  Computing

  • Domain Specific Controllers

  • Zonal Controllers 

  • Secured Connected Gateways

Electric Car Charger

Supported vehicle domains

  • HMI/Telematics & Connectivity

  • Control and Comfort 

  • ADAS 

  • Core platform Management 

Data Management 

  • Safety-Middleware Concepts 

  • Partitioning

  • Testing and validation

  • Cloud Services 

bottom of page