Model-Driven Engineering of Infotainment Networks: Page 2 of 6

July 28, 2016 //By Yury Asheshov, K2L
Model-Driven Engineering of Infotainment Networks
A vehicle’s infotainment system is a distributed embedded system, which contains hardware and software components, interacting through networks. The networking supports the infotainment system’s extensibility and flexibility.
provided by the Object Management Group (OMG).

MDA specifies three default models of a system: Computation Independent Model (CIM), Platform Independent Model (PIM) and Platform Specific Model (PSM). A CIM is a business or domain model that defines exactly what the system is expected to do. A PIM is an abstract model used to create a Platform Specific Model (PSM), which in turn is a model of the concrete system that implements the PIM upon the specific technology.


Figure 1: Abstraction Levels of MDA models
For larger image click here

 

MDA has the capability to define transformations that map the models.  A transformation from CIM to PIM is technically possible, but the efficiency of such a transformation is questionable, because CIM contains no technical details and may include informal requirements. Nevertheless, the CIM requirements should be traceable through the PIM to the PSM constructs. The PIM, which abstracts out the technical aspects, may be effectively transformed into several platform-specific models.

The design of an infotainment network specifies, among other things, the physical deployment of software components on nodes, the inter-communication protocol (data exchange) between those components, and a configuration of bandwidth allocations to transfer data, audio and video contents between nodes (connection management). It is essential to note, that each node cannot be considered as an isolated device, but must be designed as part of an infotainment network. The UML deployment diagram depicts a physical deployment of the software components on nodes and can be used as specified in the UML standard. An UML model of a data exchange may be specified in several ways. The best known are the remote procedure call (RPC) and the message-oriented styles.

When the RPC style of the data exchange model is used, the methods and the attributes (properties) of the communication interfaces must be defined as interfaces of the programming language. These methods and attributes may have additional marks (annotations) that specify

Design category: 

Vous êtes certain ?

Si vous désactivez les cookies, vous ne pouvez plus naviguer sur le site.

Vous allez être rediriger vers Google.