Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus Software Designer"
m (Francois.le-fevre.cea.fr moved page Papyrus Qompass to Papyrus Designer: product name changed) |
|||
| Line 3: | Line 3: | ||
== What is Papyrus Designer? == | == What is Papyrus Designer? == | ||
| − | Papyrus | + | Papyrus designer supports the code generation from models including embedded and real-time systems as potential targets. In does this at two different levels of abstraction. |
| − | * | + | * Direct code generation for a specific programming language. Currently, C++ and Java are supported, C will be supported soon. |
| − | + | ||
| − | + | * Support for component-based models. In this case, the generation starts from a model that includes the definition of software components, hardware nodes and deployment information. The latter consists of a definition of the instances of components and nodes and an <em>allocation</em> between these. Code generation is done by a sequence of transformations steps. The model transformation takes care of some platform specific aspects (e.g. communication mechanisms or thread allocation), based on non-functional properties. This is complementary with the upcoming Papyrus architect that can create an allocation based on modeled analysis data such as period length or worst case execution times. | |
| + | |||
| + | Papyrus Designer code generation | ||
<center> | <center> | ||
Revision as of 08:06, 11 April 2016
Contents
Papyrus Designer
What is Papyrus Designer?
Papyrus designer supports the code generation from models including embedded and real-time systems as potential targets. In does this at two different levels of abstraction.
- Direct code generation for a specific programming language. Currently, C++ and Java are supported, C will be supported soon.
- Support for component-based models. In this case, the generation starts from a model that includes the definition of software components, hardware nodes and deployment information. The latter consists of a definition of the instances of components and nodes and an allocation between these. Code generation is done by a sequence of transformations steps. The model transformation takes care of some platform specific aspects (e.g. communication mechanisms or thread allocation), based on non-functional properties. This is complementary with the upcoming Papyrus architect that can create an allocation based on modeled analysis data such as period length or worst case execution times.
Papyrus Designer code generation
Tool Chain overview
Papyrus Designer is integrated into the open source UML editor Papyrus, The UML profile MARTE is used for non-functional properties. Parts of the component model were developed in the context of the French national project Flex-eWare.
Target audience
The following information assume that the reader already knows UML and the basics about component oriented design.
Content of this document
In the sequel, you find information about the Papyrus Designer