|
|
| (20 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | = Qompass Designer for Papyrus = | + | = Page has been moved to [https://gitlab.eclipse.org/eclipse/papyrus/org.eclipse.papyrus-designer/-/wikis/home SW Designer wiki on gitlab] = |
| − | | + | |
| − | Qompass Designer is a component based modeling approach that supports the code generation from 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. Qompass Designer is part of the Qompass tool-suite integrated into Papyrus. The separation of concerns between the two tools is that
| + | |
| − | | + | |
| − | * Qompass analyzer 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
| + | |
| − | * Qompass designer supports the code generation for a specified architecture. It enables this code generation by means of 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>
| + | |
| − | | + | |
| − | Qompass 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].
| + | |
| − | | + | |
| − | In the sequel, you find information about the
| + | |
| − | | + | |
| − | * [[Papyrus_Qompass_input_models]] Input models for code generation"
| + | |
| − | * [[Papyrus_Qompass_connector-container]] Using dedicated interaction components and realizing cross-cutting concerns via the container
| + | |
| − | * [[Papyrus_Qompass_code-generation]] The code generation from models
| + | |
| − | | + | |
| − | We also recommend the examples section in the documentation index as a starting point for using Qompass.
| + | |
