|
|
| (9 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | = Qompass Designer Examples = | + | = Page has moved to [https://gitlab.eclipse.org/eclipse/papyrus/org.eclipse.papyrus-designer/-/wikis/example-walkthrough gitlab] = |
| − | | + | |
| − | Qompass designer for Papyrus comes with a set of examples. All of these can be accessed via File->New->Example and the category Papyrus examples. A hosting project must already exist.
| + | |
| − | | + | |
| − | All examples contain embedded comments. In the sequel, we go through some of the examples, starting with a simple HelloWorld program based on Qompass.
| + | |
| − | | + | |
| − | | + | |
| − | == Hello World ==
| + | |
| − | | + | |
| − | The Hello World example consists of two software components, System and HelloWorld. The former is a component that all Qompass applications use. It represents the software architecture. The HelloWorld components is a ''part'' within the system, i.e. the system ''has'' or contains a Hello World component. On the UML level, the part is attribute with composite aggregation typed with the HelloWorld component. It is important to separate the composition on the instance level from the definition of components: the component HelloWorld is not defined within the system, its instances can also appear in other composites.
| + | |
| − | | + | |
| − | The hardware model has a quite similar structure compared to the software components: A component representing the hardware architecture contains a single node (called MonoNode) on which we want to deploy our Hello World component.
| + | |
| − | In case of the Hello World component, the main instance is the instance of the system, containing a hello-world component as a sub-instance.
| + | |
| − | | + | |
| − | | + | |
| − | == Producer Consumer == | + | |
| − | | + | |
| − | The producer consumer example consists of two interacting components that are part of the obligatory system component. These components communicate in a data flow style in two different variants. In the first, the (data) consumer is invoked from the environment to push new data. In the second, the consumer component asks for new data. Therefore, the two different variants are denotes as Push and PullConsumer respectively.
| + | |
| − | via a channel, repres
| + | |
