FeatureGroup : public class
Created: |
2006-06-28 17:55:18 |
Modified: |
2010-04-29 13:26:53 |
|
Project: |
|
Author: |
Mark-Oliver Reiser |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Advanced: |
|
UUID: |
{776D6E42-62B5-49ee-8729-4C147A50EFD0} |
Appears In: |
FeatureModeling |
<p>FeatureGroup is a specialization of the FeatureTreeNode, enabling grouping of several Features. It specifies with its cardinality how these grouped features can be combined. For example, a FeatureGroup owning the two Features A and B, and with a cardinality of [1], means that A and B are alternatives.<br/></p><p><br/></p><p><br/></p><p>Semantics:<br/></p><p>FeatureGroup is a grouping entity for sibling Features to reflect variability for a set of Features.<br/></p><p><br/></p><p><br/></p><p>Extension:<br/></p><p>Class<br/></p>
- Attributes
- Associations From
- Other Links
Attribute |
Details |
public String cardinality |
Notes:
|
The cardinality of the FeatureGroup. It states how many of its child features can be selected in a valid configuration. Mandatory features among the child features count as 1 and for cloned features all instances created in the configuration count.
|
|
Element |
Source Role |
Target Role |
Details |
«atpStructureElement» Feature
Class
|
Name: childFeature
FeatureGroups may only have Features as their children and must always have at least two children.
It is perfectly legal to have child features in a feature group that are mandatory or cloned. However, except for special use cases, this is discouraged and therefore all child features of a FeatureGroup should usually be optional, i.e. have cardinality [0..1].
|
Name:
|
|