|
|
| (13 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | = Papyrus Designer = | + | = Page has been moved to [https://gitlab.eclipse.org/eclipse/papyrus/org.eclipse.papyrus-designer/-/wikis/home SW Designer wiki on gitlab] = |
| − | | + | |
| − | == What is Papyrus Designer? ==
| + | |
| − | | + | |
| − | Papyrus Designer is a component based modeling approach that supports the code generation for embedded systems. Theses systems are characterized by timing and resource constraints - sometimes also denoted as non-functional properties. Since these systems get more and more complex, it is important that the non-functional properties are not just specified in the documentation and respected by the implemented system, but that these are explicitly modeled and suitable code is derived from the model. Papyrus Designer is part of the Papyrus tool-suite integrated into Papyrus. The separation of concerns between the two tools is that
| + | |
| − | | + | |
| − | * Papyrus Architect analyzes a system, in particular with respect to schedulability analysis. It enables the validation of several variants to allocate software components to execution resources and thus provides an architectural exploration
| + | |
| − | * Papyrus Designer supports the code generation for a specified architecture.
| + | |
| − | | + | |
| − | Papyrus Designer code 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 and a final code generation step as shown in the figure below.
| + | |
| − | | + | |
| − | <center>
| + | |
| − | [[Image:PapyrusQompass-methodology.png|800px]]<br/> | + | |
| − | Tool Chain overview
| + | |
| − | </center>
| + | |
| − | | + | |
| − | <p>
| + | |
| − | | + | |
| − | Papyrus Designer is integrated into the open source UML editor [http://www.eclipse.org/papyrus Papyrus],
| + | |
| − | The UML profile [http://www.omgmarte.org MARTE] is used for non-functional properties.
| + | |
| − | Parts of the component model were developed in the context of the French national project [http://www.flex-eware.org 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
| + | |
| − | | + | |
| − | * [[Papyrus/Qompass/designer/getting-started|Getting started and installation instructions]]
| + | |
| − | * [[Papyrus/Qompass/designer/input-models|Input models for code generation]]
| + | |
| − | * [[Papyrus/Qompass/designer/connector-container|Using dedicated interaction components and realizing cross-cutting concerns via the container]]
| + | |
| − | * [[Papyrus/Qompass/designer/code-generation|Code generation from models]]
| + | |
| − | * [[Papyrus/Qompass/designer/example-walkthrough|Discussion of a set of examples]]
| + | |
| − | * [[Papyrus/Qompass/designer/reconfiguration|Use of Papyrus Designer for reconfiguration (ongoing work)]]
| + | |
