2012
DOI: 10.1007/bf03323457
|View full text |Cite
|
Sign up to set email alerts
|

Model-Driven Product Consolidation into Software Product Lines

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2012
2012
2015
2015

Publication Types

Select...
2
1

Relationship

2
1

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 5 publications
0
4
0
Order By: Relevance
“…Klatt and K. Krogmann [2] proposed model-driven product consolidation into software product lines. Whether an existing SPL should be extended with an ad-hoc customized product (reactive approach) or a new SPL should be created by consolidating multiple products (extractive approach) -implementation level models of the existing products should be extracted in both cases.…”
Section: Related Workmentioning
confidence: 99%
“…Klatt and K. Krogmann [2] proposed model-driven product consolidation into software product lines. Whether an existing SPL should be extended with an ad-hoc customized product (reactive approach) or a new SPL should be created by consolidating multiple products (extractive approach) -implementation level models of the existing products should be extracted in both cases.…”
Section: Related Workmentioning
confidence: 99%
“…Similar to Bosch et al [2], [21], we propose a clear differentiation between features, which are on a capability-level and related to requirements management, and variability of software in terms of variation points, which are on the level of software design and architecture. The following subsections explain this differentiation in more detail and introduce how we propose to partition them into different models [15].…”
Section: Features and Variabilitymentioning
confidence: 99%
“…abstract syntax trees as included in the OMG Knowledge Discovery Model [19], [18]). Due to this, we propose to use a specific variation point model, capable to link those mature models and include the design decision about the variation point realisation as described in [15] and illustrated in Figure 1.…”
Section: Model Structurementioning
confidence: 99%
“…In [3] we explain how to identify and recommend related variation points in the software. The product line engineer has to make design decisions on i) which variation points to merge, and ii) how to realise their variability.…”
Section: Product Copy Migration Examplementioning
confidence: 99%