Migration to Service-Oriented Architecture Using Model-Based Design

This example shows the step-wise migration from a signal-based model to a service-oriented architecture (SOA). SOA is a modern software architecture paradigm for building applications as a collection of modular units of software called services. This approach enables you to build complex and distributed applications in which you can update individual components, in contrast to building a large model with a signal-based design. A typical SOA software stack consists of application software with services, platform services, and middleware. In SOA, services act as clients, or servers, and each is implemented as a software component. The connection points between these components are called client-server ports, forming service-oriented interfaces.

Some advantages to using service components in design include:

• Services can be reused and shared with many applications or components.

• Potential for relocating functions within the software architecture.

• Increased testability of individual modules.

This example shows the migration of an electric vehicle powertrain control software application from a signal-based model to a service-oriented architecture. The application generates brake and torque commands based on vehicle inputs.

Service-Oriented Architecture Workflow Steps

Follow these steps to migrate the electric vehicle powertrain control software application to a service-oriented architecture.

1. Generate Baseline Tests

2. Partition Software Application

3. Create Architecture Model and Service Interface

4. Create Simulink Behavior Model

5. Validate Migrated Model

6. Generate Embedded Code

Service-Oriented Architecture Project

To load the project to your working folder, click the Copy Command button. The project contains folders that correspond to the example steps, with the files referenced throughout the example.