Difference between revisions of "Application Development and Deployment"
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
The Concept Car has a modular architecture that allows the development and deployment of applications as driver assistance systems through the Controlboard. | The Concept Car has a modular architecture that allows the development and deployment of applications as driver assistance systems through the Controlboard. | ||
| Line 11: | Line 7: | ||
The whole process in order to develop and deploy an application is described in the following: | The whole process in order to develop and deploy an application is described in the following: | ||
| − | *[[Platform Independent Application Development| | + | *[[Platform Independent Application Development|Platform Independent Application Development]] |
| − | *[[Platform Specific Code Generation| | + | *[[Platform Specific Code Generation|Platform Specific Code Generation]] |
| − | *[[Application Deployment| | + | *[[Application Deployment|Application Deployment]] |
Latest revision as of 14:44, 20 October 2009
The Concept Car has a modular architecture that allows the development and deployment of applications as driver assistance systems through the Controlboard.
As Simulink Models are the primary use of the board, the process of developing and deploying those models will be presented in more details. However, it is possible to implement also other applications.
Basically, the process consists of generating code from a Simulink Model and deploying this code to execute on the Concept Car platform. The execution of the application is coordinated by the Controlboard, that means, this board, based on the functionality described by the Simulink model, receives messages from the Sensors Boards, process these information, make decisions and send those decisions through messages to the Actor Board.
The whole process in order to develop and deploy an application is described in the following:
