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"
(→Qompass Designer for Papyrus) |
(→Qompass Designer for Papyrus) |
||
| Line 1: | Line 1: | ||
= Qompass Designer for Papyrus = | = Qompass Designer for Papyrus = | ||
| + | |||
| + | == What is Qompass == | ||
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 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 | ||
| Line 14: | Line 16: | ||
Qompass is integrated into the open source UML editor [http://www.eclipse.org/papyrus Papyrus], | Qompass is integrated into the open source UML editor [http://www.eclipse.org/papyrus Papyrus], | ||
| − | The UML profile [http://www.omgmarte.org | + | 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]. | 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 | + | == 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 Qompass | ||
* [[Papyrus_Qompass_getting_started]] Getting started and installation instructions | * [[Papyrus_Qompass_getting_started]] Getting started and installation instructions | ||
| Line 23: | Line 31: | ||
* [[Papyrus_Qompass_connector-container]] Using dedicated interaction components and realizing cross-cutting concerns via the container | * [[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 | * [[Papyrus_Qompass_code-generation]] The code generation from models | ||
| − | + | * [[Papyrus_Qompass_example-walkthrough]] Discussion of a set of examples | |
| − | + | * [[Papyrus_Qompass_reconfiguration]] Use of Qompass for reconfiguration (ongoing work) | |
Revision as of 04:12, 5 June 2014
Contents
Qompass Designer for Papyrus
What is Qompass
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.
Tool Chain overview
Qompass 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 Qompass
- Papyrus_Qompass_getting_started Getting started and installation instructions
- 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
- Papyrus_Qompass_example-walkthrough Discussion of a set of examples
- Papyrus_Qompass_reconfiguration Use of Qompass for reconfiguration (ongoing work)