tree 579f88644f7ecce952748c46dea97a67ce198055
parent 913fe70aeb80c550dec19eebac1ed8b004ce65a7
author Ansgar Radermacher <ansgar.radermacher@cea.fr> 1615994834 +0100
committer Ansgar Radermacher <ansgar.radermacher@cea.fr> 1616093060 +0100

Bug 572058 - [Robotics] It should be possible to use a (sub-) systems for the definition of a larger system

- Profile changes:
   - add abstract stereotype <<ComponentOrSystem>> to the robotics profile. <<ComponentDefinition>> as well
     as <<System>> inherit from this new superclass
   - Move a part of the derived methods to the abstract superclass
   - <<ComponentInstance>>: remove "activities" attribute, as this does not exist for systems.
     More important, a user examining a component instance has an out-side/blackbox view of a component (or
     system), i.e. is not interested in activities.
   - <<ComponentInstance>>: change name and type of derived attribute "compDef:ComponentDefinition" to
     "compDefOrSys:ComponentOrSystem"

- Enable the addition of ports to a system

- Type selection dialog shows component definitions and system => Filter with new abstract stereotype,
	ScanUtils support multiple extensions via "|"

- Use robotics dialog for attributes (enable to choose types from ROS messages - a bit out of context of
  this bug

- Adapations in assertion code which uses getCompDef operation of an instance.

Change-Id: I4285460bfdf176480619ced1dbe33f0f2b102d16
Signed-off-by: Ansgar Radermacher <ansgar.radermacher@cea.fr>