Skip to content

Architecture editor

Jump to bottom
Luca Gherardi edited this page Dec 10, 2013 · 6 revisions

The Architecture Editor allows the design of Architectural Models. In particular it can be used for designing the architecture of a product line (aka the Template System Model).

In order to create a new Architectural Model:

  1. Select File -> New -> Other...
  2. Select the item ROS Component Model Diagram under the category HyperFlex

The wizard will open the Architecture Diagram editor. In this page we exemplify the design or a ROS architectural model, however the concepts holds also for other Software Frameworks. The picture below depicts a diagram designed with the ROS editor.

Architectural Model editor

ROS Architectural Model Design

TO BE MODIFIED

The palette on the right provides the tools for inserting new architectural element and composing them:

  • Node: a Node is a component in the ROS terminology. It has the following properties:
    • Name: it is the name the component will have at runtime
    • Package Name: it is the name of the ROS package containing the executable
    • Type: it is the name of the executable
    • This attribute are used in the Node tag of the ROS launch file in the following way:
      • <node pkg="Package Name" type="Type" name="Name">
  • Publisher: a publisher is a component interface used for writing typed messages on a specific topic. It has the following properties:
    • Name: it is the name of the interface
    • Topic Name: it is the name of the topic on which the publisher writes data. It is defined in the declaration of the publisher in the Node implementation.
  • Subscriber: a publisher is a component interface used for reading typed messages from a specific topic. It has the following properties:
    • Name: it is the name of the interface
    • Topic Name: it is the name of the topic from which the subscriber read data. It is defined in the declaration of the subscriber in the Node implementation.
  • Topic: is the register on which publishers write data and from which subscribers read data. It has the following properties:
    • Name: it is the name of the topic. When this name is different with respect to the name of the topic defined in a connected publisher (or subscriber), this topic name is used for deriving the remap tag: <remap from="publisher.topicName" to="topic.name"/>
  • Service Server: ...
    • ...
  • Service Client: ...
    • ...
  • Parameter: ...
    • ...
  • Composite: ...
    • ...
  • Import Composite: ...
    • ...
  • Connection: ...
    • ...
  • Promote Connection: ...
    • ...
Clone this wiki locally