MARTE11 — Feature group

The whole AADL features group concepts can't be represented in MARTE

Precise the mapping perimeter and semantics of "inverse of"

Feature Group is a new aadl v2 concept.
An AADL feature is part of a component type definition that specifies how that
component interfaces with other components of the system. Features represent
ports, subprogram and subprogram group accesses, parameters, and data and
bus accesses.
Feature group represents groups of component features, features group can
contain feature group, and can be use anywhere features can be used. Inside a
component, each feature can be connected individually, outside a component a
feature groups can be connected as a single unit.
A feature group type can be declared to be the inverse of another feature group
type, which specifies that the feature types will remain the same but that the
“direction” will be the opposite: so service provided/ required qualifier, flow
direction, the parameter passing mode will be automatically deduced.
In UML concept, the notion of port group, as group of ports, doesn’t exist. We
use a symmetrical solution, meaning the possibility to refine and compose
interfaces typing ports as alternative to physical connection point assembly.
The MARTE AADL mapping perimeter will be restricted to data access and
subprogram access.
In order to provide a homogeneous representation for designers, align with data
access and subprogram access, feature group will be represented as an UML
interface composed by at least two attributes (representing more than one data
access) or two subprogram access (representing more than one subprogram
access). By default, the interface is provided.
UML delegation/assembly connection represents AADL feature group access. In Threads and Processes subcomponents, constituting the system
subcomponents, internal ports will be typed by interfaces representing the
FeatureGroup subtypes, like unitary or composed data/subprogram access