Table 1 Some of the F3 patterns
From: F3T: a tool to support the F3 approach on the development and reuse of frameworks
Pattern | Purpose |
|---|---|
Domain Feature | Indicates structures that should be created for a feature. |
Mandatory Decomposition | Indicates code units that should be created when there is a mandatory decomposition linking two features. |
Optional Decomposition | Indicates code units that should be created when there is an optional decomposition linking two features. |
Simple Decomposition | Indicates code units that should be created when there is a simpledecomposition linking two features. |
Multiple Decomposition | Indicates code units that should be created when there is a multipledecomposition linking two features. |
Variant Decomposition | Indicates code units that should be created when there is a variantdecomposition linking two features. |
Variant Feature | Defines a class hierarchy for features with variants. |
Modular Hierarchy | Defines a class hierarchy for features with common attributes andoperations. |
Requiring Dependency | Indicates code units that should be created when a feature requires another one. |
Excluding Dependency | Indicates code units that should be created when a feature excludes another one. |