The use of features as an abstraction makes the FUSION framework independent of a particular implementation platform or application domain. For example, in a rule-based system a feature may correspond to a set of rules, in a service-oriented system it may correspond to a set of services in a workflow, and so on. For clarity, in this paper we assume a particular realization of a feature: a feature represents an extension of the architecture at well-defined variation points. A feature maps to a subset of the system’s software architecture. For example, Figure 1b shows the mapping of Evidence Generation feature to a subset of the TRS.