Lost in Source Code: Physically Separating Features in Legacy Systems

Jacob Krüger

doi:10.1109/ICSE-C.2017.46

Lost in Source Code: Physically Separating Features in Legacy Systems

Jacob Krüger

Engineering of Software-Intensive Systems

Onderzoeksoutput: Hoofdstuk in Boek/Rapport/Congresprocedure › Conferentiebijdrage › Academic › peer review

7 Citaten (Scopus)

Samenvatting

Feature-oriented programming allows developers to physically separate and reuse features via composition. This promises several benefits compared to other reuse approaches, for instance, easier traceability and maintenance. However, due to their simplicity cloning and annotation-based product lines are established in practice. We aim to reduce risks and costs of migrating towards composition, lowering the adoption barrier. This includes i) processes, ii) migration approaches, and iii) assessing advantages and disadvantages. Overall, we will facilitate integrating physical separation into legacy applications.

Originele taal-2	Engels
Titel	International Conference on Software Engineering Companion (ICSE-C)
Uitgeverij	IEEE Press
Pagina's	461-462
Aantal pagina's	2
DOI's	https://doi.org/10.1109/ICSE-C.2017.46
Status	Gepubliceerd - 2017

Bibliografische nota

DBLP License: DBLP's bibliographic metadata records provided through http://dblp.org/ are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions.

Toegang tot document

10.1109/ICSE-C.2017.46

Citeer dit

@inproceedings{04af148ad8914e138d005ddb06c4a72a,

title = "Lost in Source Code: Physically Separating Features in Legacy Systems",

abstract = "Feature-oriented programming allows developers to physically separate and reuse features via composition. This promises several benefits compared to other reuse approaches, for instance, easier traceability and maintenance. However, due to their simplicity cloning and annotation-based product lines are established in practice. We aim to reduce risks and costs of migrating towards composition, lowering the adoption barrier. This includes i) processes, ii) migration approaches, and iii) assessing advantages and disadvantages. Overall, we will facilitate integrating physical separation into legacy applications.",

keywords = "Software Product Line, Extraction, Migration",

author = "Jacob Kr{\"u}ger",

note = "DBLP License: DBLP's bibliographic metadata records provided through http://dblp.org/ are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions.",

year = "2017",

doi = "10.1109/ICSE-C.2017.46",

language = "English",

pages = "461--462",

booktitle = "International Conference on Software Engineering Companion (ICSE-C)",

publisher = "IEEE Press",

}

TY - GEN

T1 - Lost in Source Code: Physically Separating Features in Legacy Systems

AU - Krüger, Jacob

N1 - DBLP License: DBLP's bibliographic metadata records provided through http://dblp.org/ are distributed under a Creative Commons CC0 1.0 Universal Public Domain Dedication. Although the bibliographic metadata records are provided consistent with CC0 1.0 Dedication, the content described by the metadata records is not. Content may be subject to copyright, rights of privacy, rights of publicity and other restrictions.

PY - 2017

Y1 - 2017

N2 - Feature-oriented programming allows developers to physically separate and reuse features via composition. This promises several benefits compared to other reuse approaches, for instance, easier traceability and maintenance. However, due to their simplicity cloning and annotation-based product lines are established in practice. We aim to reduce risks and costs of migrating towards composition, lowering the adoption barrier. This includes i) processes, ii) migration approaches, and iii) assessing advantages and disadvantages. Overall, we will facilitate integrating physical separation into legacy applications.

AB - Feature-oriented programming allows developers to physically separate and reuse features via composition. This promises several benefits compared to other reuse approaches, for instance, easier traceability and maintenance. However, due to their simplicity cloning and annotation-based product lines are established in practice. We aim to reduce risks and costs of migrating towards composition, lowering the adoption barrier. This includes i) processes, ii) migration approaches, and iii) assessing advantages and disadvantages. Overall, we will facilitate integrating physical separation into legacy applications.

KW - Software Product Line

KW - Extraction

KW - Migration

U2 - 10.1109/ICSE-C.2017.46

DO - 10.1109/ICSE-C.2017.46

M3 - Conference contribution

SP - 461

EP - 462

BT - International Conference on Software Engineering Companion (ICSE-C)

PB - IEEE Press

ER -

Lost in Source Code: Physically Separating Features in Legacy Systems

Samenvatting

Bibliografische nota

Toegang tot document

Vingerafdruk

Citeer dit