Model Transformation: Simulink

From UcgnWiki

Jump to: navigation, search
(Overview)
Line 3: Line 3:
= Overview =
= Overview =
-
The Simulink model transformation layer and the UCGN core code-generator were designed because of the dissatisfaction with some of the available COTS code-generators at the time (2005/2006), i.e. MATLAB Realtime Workshop<ref>Especially The Mathworks have done their homework since then with respect to Safety-critical applications and DO-178B</ref>, dSpace TargetLink, IBM Rational Rhapsody etc. It was perceived that all of the COTS generators resulted in source code that would pose some significant problems when attempting certification of the generated source code to the aerospace software standard [http://en.wikipedia.org/wiki/DO-178B DO-178B]. All existing COTS code generators lacked the ability to be fully configured to produce the desired source code.
+
The Simulink model transformation layer and the UCGN core code-generator were initially conceived several years back because of the dissatisfaction with some of the available COTS code-generators at the time (2005/2006), i.e. MATLAB Realtime Workshop<ref>Especially The Mathworks have done their homework since then with respect to Safety-critical applications and DO-178B</ref>, dSpace TargetLink, IBM Rational Rhapsody etc. It was perceived that all of the COTS generators resulted in source code that would pose some significant problems when attempting certification of the generated source code to the aerospace software standard [http://en.wikipedia.org/wiki/DO-178B DO-178B]. All existing COTS code generators lacked the ability to be fully configured to produce the desired source code.
Also, the project at the time required that different model-based development approaches would be used together (i.e. UML modeling and control design using Simulink) and that the resulting auto-code be integrated. This was non-trivial because of the very different "flavors" of source code resulting from the different modeling tools.   
Also, the project at the time required that different model-based development approaches would be used together (i.e. UML modeling and control design using Simulink) and that the resulting auto-code be integrated. This was non-trivial because of the very different "flavors" of source code resulting from the different modeling tools.   

Revision as of 18:38, 25 June 2010

Personal tools