2004
DOI: 10.1049/ip-sen:20040922
|View full text |Cite
|
Sign up to set email alerts
|

First class feature abstractions for product derivation

Abstract: Abstract:The authors have observed that large software systems are increasingly defined in terms of the features they implement. Consequently, there is a need to express the commonalities and variability between products of a product family in terms of features. Unfortunately, technology support for the early aspect of a feature is currently limited to the requirements level. There is a need to extend this support to the design and implementation level as well. Existing separation of concerns technologies, suc… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2006
2006
2020
2020

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 15 publications
(8 citation statements)
references
References 21 publications
0
8
0
Order By: Relevance
“…Some of these approaches use role models to represent the interfaces and interactions needed to cover certain functionality independently (a feature or a set of features). The most representative are [6,21], but similar approaches have appeared in the OO field, for example [5,20]. We build on this correlation using agent-based role models at the acquaintance organization to represent features independently.…”
Section: Software Product Linesmentioning
confidence: 99%
“…Some of these approaches use role models to represent the interfaces and interactions needed to cover certain functionality independently (a feature or a set of features). The most representative are [6,21], but similar approaches have appeared in the OO field, for example [5,20]. We build on this correlation using agent-based role models at the acquaintance organization to represent features independently.…”
Section: Software Product Linesmentioning
confidence: 99%
“…A central task of this paradigm is thus to model the SPL variability, i.e., what is common, what varies between the different software systems, and how it varies. Variability representations are used, among others, for knowledge representation [15], to define the scope of the product line [16], manage its evolution and maintenance [7], to perform design operations [17,18] or for product derivation [19].…”
Section: Software Product Lines Engineeringmentioning
confidence: 99%
“…The concept of role here is similar to the responsibility in [12] and the role in [9]. Compared with features, roles reserve the knowledge of features as well as endow features with the implementation aspects, so it can support the mapping from features to program artefacts in a more natural way [19].…”
Section: Fig 2 Meta-model Of the Role Modelmentioning
confidence: 99%